Tor Browser 11.0.9 and Windows 10 - intermittent connection. LTP after not being able to get on for last 1 week

I am using:

  • Windows 10 on laptop
  • Tor Browser 11.0.9 (recent update)
  • Security level safest
  • my internet connection is Australian national broadband network
  • it used to work before about a month ago (version 10.5.6) and I haven’t used it in a month
  • it doesn’t work well not since auto-update
  • when I open a browser 70% of the time it doesn’t connect, 30% of the time it connect and goes to the homepage and then rarely it connects to a page like dark fail or dread forum and it doesn’t load any further
  • i have tried every trouble shooting like
    • tried sync clock
    • my ISP is not blocking it (called and checked)
    • deleted and re-installed at least 10 times - LTP doing this
    • tried installing TOR on a different partition
    • delete parent.lock file

I have tried getting bridges which is what I have done in the past and that has what allowed me to have the successful intermittent connection on this occasion but it doesn’t work consistently as I mentioned.

Often it comes up with a proxy error: ```
[WARN] Proxy Client: unable to connect to xx…xxx…xxx.xx:xxxxx (“general SOCKS server failure”)

This is mentioned in the Tor manual but my connection doesn’t require a SOCKS proxy and I am not sure what the solution to this problem is.

Can someone please help me with this because I have spent 1 week on this?


4/2/22, 00:32:23.518 [NOTICE] New control connection opened from 127.0.0.1.
4/2/22, 00:32:23.518 [NOTICE] New control connection opened from 127.0.0.1.
4/2/22, 00:35:40.744 [NOTICE] New control connection opened from 127.0.0.1.
4/2/22, 00:35:41.150 [NOTICE] New control connection opened from 127.0.0.1.
4/2/22, 01:31:17.271 [NOTICE] New control connection opened from 127.0.0.1.
4/2/22, 01:31:17.540 [NOTICE] New control connection opened from 127.0.0.1.
4/2/22, 01:31:30.171 [NOTICE] New control connection opened from 127.0.0.1.
4/2/22, 01:31:30.421 [NOTICE] New control connection opened from 127.0.0.1.
4/2/22, 01:33:35.599 [NOTICE] New control connection opened from 127.0.0.1.
4/2/22, 01:33:36.500 [NOTICE] New control connection opened from 127.0.0.1.
4/2/22, 01:33:37.473 [NOTICE] Opening Socks listener on 127.0.0.1:9150
4/2/22, 01:33:37.473 [NOTICE] Opened Socks listener connection (ready) on 127.0.0.1:9150
4/2/22, 01:33:37.480 [NOTICE] Renaming old configuration file to “C:\Users\ashwa\Desktop\Tor Browser\Browser\TorBrowser\Data\Tor\torrc.orig.1”
4/2/22, 01:33:38.125 [NOTICE] Bootstrapped 5% (conn): Connecting to a relay
4/2/22, 01:33:38.367 [NOTICE] Bootstrapped 10% (conn_done): Connected to a relay
4/2/22, 01:33:38.634 [NOTICE] Bootstrapped 14% (handshake): Handshaking with a relay
4/2/22, 01:33:39.183 [NOTICE] Bootstrapped 15% (handshake_done): Handshake with a relay done
4/2/22, 01:33:39.183 [NOTICE] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
4/2/22, 01:33:39.440 [NOTICE] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus
4/2/22, 01:33:39.695 [NOTICE] Bootstrapped 30% (loading_status): Loading networkstatus consensus
4/2/22, 01:33:41.680 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
4/2/22, 01:33:41.928 [NOTICE] Bootstrapped 40% (loading_keys): Loading authority key certs
4/2/22, 01:33:42.635 [NOTICE] The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services.
4/2/22, 01:33:42.635 [NOTICE] Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors
4/2/22, 01:33:42.635 [NOTICE] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/6944, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)
4/2/22, 01:33:44.134 [NOTICE] Bootstrapped 50% (loading_descriptors): Loading relay descriptors
4/2/22, 01:33:45.888 [NOTICE] The current consensus contains exit nodes. Tor can build exit and internal paths.
4/2/22, 01:33:46.729 [NOTICE] Bootstrapped 55% (loading_descriptors): Loading relay descriptors
4/2/22, 01:33:47.399 [NOTICE] Bootstrapped 61% (loading_descriptors): Loading relay descriptors
4/2/22, 01:33:47.527 [NOTICE] Bootstrapped 69% (loading_descriptors): Loading relay descriptors
4/2/22, 01:33:47.654 [NOTICE] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
4/2/22, 01:33:48.208 [NOTICE] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
4/2/22, 01:33:48.230 [NOTICE] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
4/2/22, 01:33:48.708 [NOTICE] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
4/2/22, 01:33:49.232 [NOTICE] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
4/2/22, 01:33:49.232 [NOTICE] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
4/2/22, 01:33:50.246 [NOTICE] Bootstrapped 100% (done): Done
4/2/22, 01:33:50.283 [NOTICE] New control connection opened from 127.0.0.1.
4/2/22, 02:45:52.490 [NOTICE] Switching to guard context “bridges” (was using “default”)
4/2/22, 02:45:53.146 [NOTICE] Delaying directory fetches: No running bridges
4/2/22, 02:45:53.147 [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”)
4/2/22, 02:45:53.453 [WARN] Pluggable Transport process terminated with status code 0
4/2/22, 02:45:53.963 [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”)
4/2/22, 02:45:54.472 [NOTICE] new bridge descriptor ‘hopperlab’ (fresh): $10A6CD36A537FCE513A322361547444B393989F0~hopperlab [xpuRzwsil54EG1HASFMlYoBCpMVFwYthoul2fMZPzQM] at 146.57.248.225
4/2/22, 02:45:54.472 [NOTICE] Our directory information is no longer up-to-date enough to build circuits: We’re missing descriptors for 1/2 of our primary entry guards (total microdescriptors: 6944/6944). That’s ok. We will try to fetch missing descriptors soon.
4/2/22, 02:45:54.525 [NOTICE] new bridge descriptor ‘GeorgetownPontem’ (fresh): $74FAD13168806246602538555B5521A0383A1875~GeorgetownPontem [ZWCs12Nk8NW7PEGQ2r5ZBF6PLXFnT+o5W3TS5QC/JGM] at 209.148.46.65
4/2/22, 02:45:54.570 [NOTICE] new bridge descriptor ‘Lisbeth’ (fresh): $CDF2E852BF539B82BD10E27E9115A31734E378C2~Lisbeth [DTpHLkU/hQso35JMGpJOY/6aWYjvfaup5LFU0+2WBII] at 192.95.36.142
4/2/22, 02:45:54.746 [NOTICE] new bridge descriptor ‘PraxedisGuerrero’ (fresh): $5EDAC3B810E12B01F6FD8050D2FD3E277B289A08~PraxedisGuerrero [qSueJICMYZBsv2+lFaemfzHkPZxDER2ZDeQdiLDMIDY] at 51.222.13.177
4/2/22, 02:45:54.777 [NOTICE] New control connection opened from 127.0.0.1.
4/2/22, 02:45:54.831 [NOTICE] new bridge descriptor ‘cymrubridge33’ (fresh): $0BAC39417268B96B9F514E7F63FA6FBA1A788955~cymrubridge33 [9sYkR4HW+Q/JanizcvQf1e412S2a1ExD6RHM+pL//HM] at 38.229.33.83
4/2/22, 02:45:55.163 [NOTICE] new bridge descriptor ‘griinchux’ (fresh): $011F2599C0E9B27EE74B353155E244813763C3E5~griinchux [Gf6Zetna0onvhOv8OLzeiUUfjv5zV6DFl82+x8wEt7A] at 85.31.186.98
4/2/22, 02:45:55.163 [NOTICE] new bridge descriptor ‘zipfelmuetze’ (fresh): $91A6354697E6B02A386312F68D82CF86824D3606~zipfelmuetze [7YRAoSWJ+wYD5j59olKF8/WmZ1yKaG6hoIZuOUFvsKk] at 85.31.186.26
4/2/22, 02:45:55.170 [NOTICE] New control connection opened from 127.0.0.1.
4/2/22, 02:45:55.270 [NOTICE] new bridge descriptor ‘dragon’ (fresh): $D9A82D2F9C2F65A18407B1D2B764F130847F8B5D~dragon [uOeNDAD+RKtd3LoscAdHmbtq6Y9j2sRh9isHkKussGM] at 37.218.245.14
4/2/22, 02:45:55.360 [NOTICE] new bridge descriptor ‘KauBridgeDot’ (fresh): $1AE2C08904527FEA90C4C4F8C1083EA59FBC6FAF~KauBridgeDot [r7OXmH6vfpl+GJqqfajI6Zap9dSNbxbdisopTdyS6QE] at 193.11.166.194
4/2/22, 02:45:55.360 [NOTICE] new bridge descriptor ‘KauBridgeBlue’ (fresh): $86AC7B8D430DAC4117E9F42C9EAED18133863AAF~KauBridgeBlue [WtmZ2uv4Y7guCnLU+hI0WbjGQlZMkREbsLZltXaXadQ] at 193.11.166.194
4/2/22, 02:45:55.423 [NOTICE] new bridge descriptor ‘KauBridgePale’ (fresh): $2D82C2E354D531A68469ADF7F878FA6060C6BACA~KauBridgePale [oggxcozpXaXS3PpTGVlr9kolycQ7wXQx0f67YECNprA] at 193.11.166.194
4/2/22, 02:45:55.591 [NOTICE] new bridge descriptor ‘cymrubridge31’ (fresh): $C8CBDB2464FC9804A69531437BCF2BE31FDD2EE4~cymrubridge31 [yJPSkZ6JZg2nzZzxRGXNSpE4Gw6BhTHZNodtyfCe0mU] at 38.229.1.78
4/2/22, 02:45:57.157 [WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with 144.217.20.138:80 ID= RSA_ID=FB70B257C162BF1038CA669D568D76F5B7F0BABB (“general SOCKS server failure”)
4/2/22, 02:45:57.157 [NOTICE] Bridge ‘dktoke’ has both an IPv4 and an IPv6 address. Will prefer using its IPv6 address ([2a0c:4d80:42:702::1]:27015) based on the configured Bridge address.
4/2/22, 02:45:57.157 [NOTICE] new bridge descriptor ‘dktoke’ (fresh): $C5B7CD6946FF10C5B3E89691A7D3F2C122D2117C~dktoke [jvQiwW4F56WErOOOEUDVkIOO65AYIAm8qy2z7oiSmD4] at 45.145.95.6 and [2a0c:4d80:42:702::1]
4/2/22, 02:46:03.891 [NOTICE] New control connection opened from 127.0.0.1.
4/2/22, 02:46:03.893 [NOTICE] Rate limiting NEWNYM request: delaying by 1 second(s)
4/2/22, 02:46:04.213 [NOTICE] New control connection opened from 127.0.0.1.
4/2/22, 02:46:04.290 [NOTICE] New control connection opened from 127.0.0.1.

Could it be related to this?

Welcome to the forums, BTW.

Thank you but I still don’t have a solution.

I have been using TOR on my android phone using my WIFI with no issues but would rather prefer to use it on my laptop windows 10.

I just can’t figure out what this issue is.