TB 8.5a1 fails to load reachable onion services

Sometimes i fail to load reachable onion services with TB 8.5a1.

I usually double check with another local tor service and reach the site with torsocks w3m $address.

Tested with Tor's onion services and my own v3 services.

Nothing special in the log. Copied Tor Log To Clipboard, last lines:

9/12/18, 10:53:52.230 [NOTICE] Heartbeat: Tor's uptime is 4 days 6:00 hours, with 9 circuits open. I've sent <scrubbed>
9/12/18, 10:53:52.240 [NOTICE] Average packaged cell fullness: 47.910%. TLS write overhead: 4% 

changed milestone to %Tor: unspecified

added component::core tor/tor milestone::Tor: unspecified owner::tbb-team priority::medium resolution::fixed severity::normal status::closed type::defect labels

Does the issue occur for particular onion services? Or random ones? Any hints on how to reproduce your issue?

Trac:
Status: new to needs_information

yesterday it happened with ea5faa5po25cf7fb.onion and jqs44zhtxl2uo6gk.onion (they are fine now) right now http://yslc6nb5fftewvbmxlkdm3h3b42feesug7qebc2a42xsgeesp4llkayd.onion/download/download.html is timing out in tb.

Trac:
test_onions.sh

can reach the service with system's tor service and tb's SOCKSPORT 9150, but not in new tabs/windows. this script compares reachability with two tor clients, might be useful for other things as well.

What happens in a new Tor Browser 8.5a1 installed at a different location? Do you see the same problems?

This is hard to reproduce without a guard known to have outdated descriptors.

I wonder if it's related to the version of tor bundled with 8.5a1. I know dgoulet and asn have been troubleshooting this off and on. Looks like tor-0.3.4.7-rc. What version is your local tor service (where you connect using torsocks)?

Trac:
Cc: N/A to dgoulet, asn

0.3.5.0-alpha-dev

Replying to traumschule:

0.3.5.0-alpha-dev

You could try copying that over the tor we ship in Tor Browser and check whether that solves your problem. If so, then waiting for the first 0.3.5 alpha and shipping that one seems to be the solution here.

Right, I think "difference between Tor 0.3.3.x and Tor 0.3.4.x" is a good direction to explore here.

i boldly claim that this issue is not caused by TB, but is inherent in tor's network architecture, because it regularly happens with tor nightly as well:

~/tor/webwml$ torsocks git pull
1536852541 ERROR torsocks[22353]: Connection timed out (in socks5_recv_connect_reply() at socks5.c:553)
fatal: unable to access 'http://dccbbv6cooddgcrq.onion/project/web/webwml.git/': Couldn't connect to server
~/tor/webwml$ torsocks git pull
1536858225 ERROR torsocks[22766]: Connection timed out (in socks5_recv_connect_reply() at socks5.c:553)                                                       
fatal: unable to access 'http://dccbbv6cooddgcrq.onion/project/web/webwml.git/': Couldn't connect to server
~/tor/webwml$ torsocks -P 9150 git pull
remote: Counting objects: 18, done.
remote: Compressing objects: 100% (18/18), done.
remote: Total 18 (delta 13), reused 0 (delta 0)
Unpacking objects: 100% (18/18), done.
From http://dccbbv6cooddgcrq.onion/project/web/webwml
   8c324824..daa74388  master     -> upstream/master
Updating 8c324824..daa74388
Fast-forward
~/tor/webwml$ torsocks git pull                                                                                                               
1536859186 ERROR torsocks[22841]: General SOCKS server failure (in socks5_recv_connect_reply() at socks5.c:533)                                               
fatal: unable to access 'http://dccbbv6cooddgcrq.onion/project/web/webwml.git/': Couldn't connect to server
~/tor/webwml$ torsocks git pull                                                                                                               
1536859186 ERROR torsocks[22841]: General SOCKS server failure (in socks5_recv_connect_reply() at socks5.c:533)                                               
fatal: unable to access 'http://dccbbv6cooddgcrq.onion/project/web/webwml.git/': Couldn't connect to server                                                   
~/tor/webwml$ torsocks -P 9150 git push origin master
Enumerating objects: 1, done.
Counting objects: 100% (1/1), done.
Writing objects: 100% (1/1), 223 bytes | 223.00 KiB/s, done.
Total 1 (delta 0), reused 0 (delta 0)
To github.com:traumschule/webwml.git
   8c324824..daa74388  master -> origin/master

(note the port changes between system tor and TB)

Trac:
Component: Applications/Tor Browser to Core Tor/Tor

We've been fixing couple things for HS and reachability: #27410 (moved) and #27774 (moved).

We are hunting down other issues. There is a big chance that it could be service side also since we still have open issues there.

Trac:
Milestone: N/A to Tor: unspecified
Cc: dgoulet, asn to asn

Trac:
cant_reach_ea5faa5po25cf7fb.onion.scrubbed.log.xz

Another time TB failed to find tpo's trac onion.

Wonder if this one is resolved now that Tor 0.3.4.x relays are mostly off the network, plus the other fixes. There are other known onion service reachability tickets open still too. I don't know that this one adds anything to them.

It does seem like a case of continuously trying to get an intro ack from an intro point that just won't send it as displayed in #27841 (moved).

I'm closing this for now, but let's reopen if it appears again.

Trac:
Status: needs_information to closed
Resolution: N/A to fixed

closed

moved to tpo/core/tor#27655 (closed)