Opened 7 years ago

Closed 3 years ago

#8564 closed defect (worksforme)

Newnym - HS is unavailable

Reported by: grarpamp Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor:
Severity: Normal Keywords: tor-hs
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


When hammering upon a HS at a continuous parrellism level (10 in this case), signal newym generates these immediately until the HS is available.
I think the handler would be better to hold these connections open until there's a circuit to the HS up, or its creation fails. Instead of dropping them while HS resolution/circuiting is in progress.

[notice] Closing stream for '[scrubbed].onion': hidden service is unavailable (try again later).

libtorsocks(17006): SOCKS V5 connect failed: 04:41:02 libtorsocks(17006): Host unreachable

app: connection to onion failed: No route to host

Child Tickets

Change History (8)

comment:1 Changed 7 years ago by nickm

Keywords: tor-hs added
Milestone: Tor: 0.2.4.x-finalTor: 0.2.5.x-final

I'm inclined to agree that this is worth fixing, but it doesn't seem like something critical to fix in 0.2.4. Is it hurting a not-testing use case in some bad way??

comment:2 Changed 7 years ago by nickm

(Tentatively reassigned to 0.2.5)

comment:3 Changed 7 years ago by grarpamp

I found it in logs and simply reran those tens of connections out of the thousands and have to hold off newnym till the run completes, which can be a couple days.
Though I suspect it applies to anyone who newnym's and then immediately tries connecting to a HS, ie: browsing. Which could yield an incorrect human interpretation of an hs status. A performance/reliability thing.

Was via socksport, but may also apply to transport, natdport.

comment:4 Changed 6 years ago by nickm

Milestone: Tor: 0.2.5.x-finalTor: 0.2.???

comment:5 Changed 4 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:6 Changed 4 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:7 Changed 3 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:8 Changed 3 years ago by nickm

Resolution: worksforme
Severity: Normal
Status: newclosed

We did a lot of work since 0.2.4 to improve HS reliability; whatever was causing this is probably fixed now. (Of course, if still might not be working, but if so, that's a new bug.)

Note: See TracTickets for help on using tickets.