Tor Browser 11.0.3, Windows 10 OS, cannot use BRIDGE to connect

Support Tor Browser Desktop
1

When reporting a bug, please include as many of these as possible:

  • Operating System you are using
    Windows 10 Home version

  • Tor Browser version
    TOR Browser version 11.0.3

  • Tor Browser Security Level
    Standard

  • Step by step of how you got to the issue
    TOR settings/Bridges: Selected ‘Use a bridge’
    Selected ‘Request a bridge fron torproject.org’ and on Request a New Bridge…’
    NO CONNECTION to torproject.org to get new bridges, and never able to connect!
    Selected "Select a built-in-bridge’ ‘obfs4’ and TOR never connects and unable to use the browser.

NOTE: Only way to connect is WITHOUT the (necessary for us) option to ‘Use a bridge’ which then would require us to use a VPN to furhter insure more “privacy”

  • The Tor log
    12/24/21, 01:45:05.219 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
    12/24/21, 01:45:07.134 [NOTICE] Opening Socks listener on 127.0.0.1:9150
    12/24/21, 01:45:07.134 [NOTICE] Opened Socks listener connection (ready) on 127.0.0.1:9150
    12/24/21, 01:45:07.135 [WARN] CreateProcessA() failed: The system cannot find the file specified.
    12/24/21, 01:45:07.135 [WARN] Pluggable Transport process terminated with status code 0
    12/24/21, 01:45:07.135 [WARN] Failed to start process: (null)
    12/24/21, 01:45:07.135 [WARN] Managed proxy at ‘TorBrowser\Tor\PluggableTransports\obfs4proxy.exe’ failed at launch.
    12/24/21, 01:45:07.228 [WARN] Can’t use bridge at [scrubbed]: there is no configured transport called “obfs4”.
    12/24/21, 01:45:07.229 [WARN] Can’t use bridge at [scrubbed]: there is no configured transport called “obfs4”.
    12/24/21, 01:45:07.229 [WARN] Can’t use bridge at [scrubbed]: there is no configured transport called “obfs4”.
    12/24/21, 01:45:07.229 [WARN] Can’t use bridge at [scrubbed]: there is no configured transport called “obfs4”.
    12/24/21, 01:45:07.230 [WARN] Can’t use bridge at [scrubbed]: there is no configured transport called “obfs4”.
    12/24/21, 01:45:07.230 [WARN] Can’t use bridge at [scrubbed]: there is no configured transport called “obfs4”.
    12/24/21, 01:45:07.230 [WARN] Can’t use bridge at [scrubbed]: there is no configured transport called “obfs4”.
    12/24/21, 01:45:07.230 [WARN] Can’t use bridge at [scrubbed]: there is no configured transport called “obfs4”.
    12/24/21, 01:45:07.230 [WARN] Can’t use bridge at [scrubbed]: there is no configured transport called “obfs4”.
    12/24/21, 01:45:07.230 [WARN] Can’t use bridge at [scrubbed]: there is no configured transport called “obfs4”.
    12/24/21, 01:45:07.230 [WARN] Can’t use bridge at [scrubbed]: there is no configured transport called “obfs4”.
    12/24/21, 01:45:07.230 [WARN] Can’t use bridge at [scrubbed]: there is no configured transport called “obfs4”.
    12/24/21, 01:45:07.231 [WARN] Can’t use bridge at [scrubbed]: there is no configured transport called “obfs4”.
    12/24/21, 01:45:07.231 [WARN] Can’t use bridge at [scrubbed]: there is no configured transport called “obfs4”.
    12/24/21, 01:45:07.231 [WARN] Can’t use bridge at [scrubbed]: there is no configured transport called “obfs4”.
    12/24/21, 01:45:07.231 [WARN] Can’t use bridge at [scrubbed]: there is no configured transport called “obfs4”.
    12/24/21, 01:45:07.274 [NOTICE] Application request when we haven’t used client functionality lately. Optimistically trying known bridges again.
    12/24/21, 01:45:08.243 [WARN] Can’t use bridge at [scrubbed]: there is no configured transport called “obfs4”.
    12/24/21, 01:45:08.243 [WARN] Can’t use bridge at [scrubbed]: there is no configured transport called “obfs4”.
    12/24/21, 01:45:08.243 [WARN] Can’t use bridge at [scrubbed]: there is no configured transport called “obfs4”.
    12/24/21, 01:45:08.243 [WARN] Can’t use bridge at [scrubbed]: there is no configured transport called “obfs4”.
    12/24/21, 01:45:08.243 [WARN] Can’t use bridge at [scrubbed]: there is no configured transport called “obfs4”.
    12/24/21, 01:45:08.243 [WARN] Can’t use bridge at [scrubbed]: there is no configured transport called “obfs4”.
    12/24/21, 01:45:08.244 [WARN] Can’t use bridge at [scrubbed]: there is no configured transport called “obfs4”.
    12/24/21, 01:45:08.244 [WARN] Can’t use bridge at [scrubbed]: there is no configured transport called “obfs4”.
    12/24/21, 01:45:08.244 [WARN] Can’t use bridge at [scrubbed]: there is no configured transport called “obfs4”.
    12/24/21, 01:45:08.244 [WARN] Can’t use bridge at [scrubbed]: there is no configured transport called “obfs4”.
    12/24/21, 01:45:08.244 [WARN] Can’t use bridge at [scrubbed]: there is no configured transport called “obfs4”.
    12/24/21, 01:45:08.244 [WARN] Can’t use bridge at [scrubbed]: there is no configured transport called “obfs4”.
    12/24/21, 01:45:08.244 [WARN] Can’t use bridge at [scrubbed]: there is no configured transport called “obfs4”.
    12/24/21, 01:45:08.244 [WARN] Can’t use bridge at [scrubbed]: there is no configured transport called “obfs4”.
    12/24/21, 01:45:08.244 [WARN] Can’t use bridge at [scrubbed]: there is no configured transport called “obfs4”.
    12/24/21, 01:45:08.245 [WARN] Can’t use bridge at [scrubbed]: there is no configured transport called “obfs4”.
2

12/24/21, 01:45:07.135 [WARN] Failed to start process: (null)
12/24/21, 01:45:07.135 [WARN] Managed proxy at ‘TorBrowser\Tor\PluggableTransports\obfs4proxy.exe’ failed at launch.

there is no configured transport called “obfs4”.

Something is making obfs4proxy fail at launch, check that any anti-virus isn’t blocking or removing obfs4proxy

3

We have (1) diabled Malwarebytes, and the results are still the exact same situation; Same TOR log entries.

Also, again, once we connect TOR browser (without using bridges), then, we are unable to "Request A Bridge’ abd the Request Bridge pop-up displaying ‘Contacting BridgeDB. Please Wait.’ without ever connecting.

ADDITIONAL: Several users were continuing to use TOR (Version 10.5.8, the last version that ‘worked as needed’ for Windows 10 users), and now are reporting that they are also unable to Request Bridge; However, they are able to connect and use the TOR browser when they select “Bridges>Use a bridge>Select a built-in bridge>obfs4”

This is the TOR log for one of those users:
12/24/21, 03:25:11.455 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
12/24/21, 03:25:11.455 [NOTICE] Switching to guard context “bridges” (was using “default”)
12/24/21, 03:25:11.847 [NOTICE] New control connection opened from 127.0.0.1.
12/24/21, 03:25:11.881 [NOTICE] New control connection opened from 127.0.0.1.
12/24/21, 03:25:12.230 [NOTICE] New control connection opened from 127.0.0.1.
12/24/21, 03:25:14.955 [NOTICE] Opening Socks listener on 127.0.0.1:9150
12/24/21, 03:25:14.955 [NOTICE] Opened Socks listener connection (ready) on 127.0.0.1:9150
12/24/21, 03:25:15.113 [NOTICE] Application request when we haven’t used client functionality lately. Optimistically trying known bridges again.
12/24/21, 03:25:15.432 [NOTICE] Bootstrapped 1% (conn_pt): Connecting to pluggable transport
12/24/21, 03:25:15.440 [NOTICE] Bootstrapped 2% (conn_done_pt): Connected to pluggable transport
12/24/21, 03:25:15.448 [WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with [2a0c:4d80:42:702::1]:27015 ID= RSA_ID=C5B7CD6946FF10C5B3E89691A7D3F2C122D2117C (“general SOCKS server failure”)
12/24/21, 03:25:15.583 [NOTICE] Bootstrapped 10% (conn_done): Connected to a relay
12/24/21, 03:25:15.669 [NOTICE] Bootstrapped 14% (handshake): Handshaking with a relay
12/24/21, 03:25:15.742 [NOTICE] Bootstrapped 15% (handshake_done): Handshake with a relay done
12/24/21, 03:25:15.751 [NOTICE] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
12/24/21, 03:25:15.833 [NOTICE] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus
12/24/21, 03:25:16.100 [NOTICE] new bridge descriptor ‘GeorgetownPontem’ (fresh): $74FAD13168806246602538555B5521A0383A1875~GeorgetownPontem [ZWCs12Nk8NW7PEGQ2r5ZBF6PLXFnT+o5W3TS5QC/JGM] at 209.148.46.65
12/24/21, 03:25:16.182 [WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with [2a0c:4d80:42:702::1]:27015 ID= RSA_ID=C5B7CD6946FF10C5B3E89691A7D3F2C122D2117C (“general SOCKS server failure”)
12/24/21, 03:25:16.385 [NOTICE] new bridge descriptor ‘hopperlab’ (fresh): $10A6CD36A537FCE513A322361547444B393989F0~hopperlab [xpuRzwsil54EG1HASFMlYoBCpMVFwYthoul2fMZPzQM] at 146.57.248.225
12/24/21, 03:25:16.699 [NOTICE] new bridge descriptor ‘PraxedisGuerrero’ (fresh): $5EDAC3B810E12B01F6FD8050D2FD3E277B289A08~PraxedisGuerrero [qSueJICMYZBsv2+lFaemfzHkPZxDER2ZDeQdiLDMIDY] at 51.222.13.177
12/24/21, 03:25:16.939 [NOTICE] new bridge descriptor ‘KauBridgeBlue’ (fresh): $86AC7B8D430DAC4117E9F42C9EAED18133863AAF~KauBridgeBlue [WtmZ2uv4Y7guCnLU+hI0WbjGQlZMkREbsLZltXaXadQ] at 193.11.166.194
12/24/21, 03:25:17.490 [NOTICE] new bridge descriptor ‘KauBridgePale’ (fresh): $2D82C2E354D531A68469ADF7F878FA6060C6BACA~KauBridgePale [oggxcozpXaXS3PpTGVlr9kolycQ7wXQx0f67YECNprA] at 193.11.166.194
12/24/21, 03:25:17.490 [NOTICE] new bridge descriptor ‘KauBridgeDot’ (fresh): $1AE2C08904527FEA90C4C4F8C1083EA59FBC6FAF~KauBridgeDot [r7OXmH6vfpl+GJqqfajI6Zap9dSNbxbdisopTdyS6QE] at 193.11.166.194
12/24/21, 03:25:17.218 [NOTICE] new bridge descriptor ‘zipfelmuetze’ (fresh): $91A6354697E6B02A386312F68D82CF86824D3606~zipfelmuetze [7YRAoSWJ+wYD5j59olKF8/WmZ1yKaG6hoIZuOUFvsKk] at 85.31.186.26
12/24/21, 03:25:17.218 [NOTICE] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
12/24/21, 03:25:17.271 [NOTICE] new bridge descriptor ‘griinchux’ (fresh): $011F2599C0E9B27EE74B353155E244813763C3E5~griinchux [Gf6Zetna0onvhOv8OLzeiUUfjv5zV6DFl82+x8wEt7A] at 85.31.186.98
12/24/21, 03:25:17.564 [NOTICE] Bootstrapped 76% (ap_conn_pt): Connecting to pluggable transport to build circuits
12/24/21, 03:25:17.621 [NOTICE] Bootstrapped 77% (ap_conn_done_pt): Connected to pluggable transport to build circuits
12/24/21, 03:25:17.677 [NOTICE] new bridge descriptor ‘cymrubridge31’ (fresh): $C8CBDB2464FC9804A69531437BCF2BE31FDD2EE4~cymrubridge31 [yJPSkZ6JZg2nzZzxRGXNSpE4Gw6BhTHZNodtyfCe0mU] at 38.229.1.78
12/24/21, 03:25:17.679 [NOTICE] new bridge descriptor ‘cymrubridge33’ (fresh): $0BAC39417268B96B9F514E7F63FA6FBA1A788955~cymrubridge33 [9sYkR4HW+Q/JanizcvQf1e412S2a1ExD6RHM+pL//HM] at 38.229.33.83
12/24/21, 03:25:18.314 [WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with 192.95.36.142:443 ID= RSA_ID=CDF2E852BF539B82BD10E27E9115A31734E378C2 (“general SOCKS server failure”)
12/24/21, 03:25:18.314 [WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with 144.217.20.138:80 ID= RSA_ID=FB70B257C162BF1038CA669D568D76F5B7F0BABB (“general SOCKS server failure”)
12/24/21, 03:25:18.314 [NOTICE] new bridge descriptor ‘dragon’ (fresh): $D9A82D2F9C2F65A18407B1D2B764F130847F8B5D~dragon [uOeNDAD+RKtd3LoscAdHmbtq6Y9j2sRh9isHkKussGM] at 37.218.245.14
12/24/21, 03:25:20.693 [NOTICE] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
12/24/21, 03:25:20.867 [NOTICE] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
12/24/21, 03:25:21.284 [NOTICE] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
12/24/21, 03:25:21.291 [NOTICE] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
12/24/21, 03:25:21.875 [NOTICE] Bootstrapped 100% (done): Done
12/24/21, 03:25:22.144 [NOTICE] New control connection opened from 127.0.0.1.

4

Requesting a bridge from within Tor Browser is failing here too (Win 10 Pro, Tor Browser 11.0.3). The process gets stuck on the following screen.

reqbridge
reqbridge1495×879 60.5 KB

This occurs whether my antivirus software is enabled or not. The log contents are: 12/24/21, 03:21:32.179 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.

1 Like
5

Right, I can reproduce it on a completely new install, I think we’ve found some bug. I’ll go open an issue for it.

4 Likes
6

UPDATE: this appears to be far more insidious than simply “a bug” within TOR version 11.0.3. There appears to be either a BUG or some “system issues” within the TOR network that have conspired to BLOCK the use of BRIDGES with TOR network, completely and affecting ALL of our Windows 10 users/TOR 11.0.3 AND TOR 10.8.5

BOTH versions now do NOT work when BRIDGES are attempted to be used with connection to the TOR network!

Again, the only way to use TOR, is by NOT using BRIDGES, and therefore we MUST use a VPN!

7

Thanks for the bug report @MrYnLA! Given that it’s occurring on all versions of Tor Browser that I’ve tested (including 10.5.x) I don’t think this is an issue with Tor Browser itself – however I’ll follow-up with the developers to see what’s going on.

In the meantime both built-in bridges (i.e. obfs4, snowflake and meek-azure) and bridges from bridges.torproject.org don’t seem to be affected. Would you like to try those options instead?

Also, I’m happy to report that the previous Windows issues should be fixed as of version 11.0.3, and I’d encourage any Windows users using older versions of Tor Browser to update now :slight_smile:

2 Likes
8

Update: Arma has traced the issue back to Moat – the service that Tor Browser (and other Tor-powered apps) uses to fetch bridges from BridgeDB – and has managed to get it working again (thanks @arma!).

However this may just be a temporary fix, as the underlying issue likely remains. I’ll keep an eye on it in Tor Browser over the holiday period just in case it falls over again.

2 Likes
9

Yep! You can follow the “moat mysteriously disappeared” gitlab ticket here:

Hopefully that was the end of this particular problem, and our next step once people are back from break is to figure out why the process disappeared. Presumably some bug somewhere that made it exit. But we’ll see. :slight_smile:

4 Likes