Cannot connect to Tor Browser on Windows

Hello group :slight_smile: Sorry for opening another topic I just thought I posted in the wrong forum. l made a new topic in Tor Browser desktop maybe it should be moved, Frustrated and dealing with a small phone.

OS: Win10

Tor: version: 15.0.14

Security.: Standard

Everything was fine I put my laptop to sleep and upon awakening is when the problem started.

Yesterday this is what I was getting, references to A bug.

2026-05-27 04:12:45.235 \[NOTICE\] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2026-05-27 04:12:45.240 \[NOTICE\] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2026-05-27 04:12:45.246 \[NOTICE\] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2026-05-27 04:12:45.393 \[NOTICE\] Opening Socks listener on 127.0.0.1:9150 2026-05-27 04:12:45.393 \[NOTICE\] Opened Socks listener connection (ready) on 127.0.0.1:9150 2026-05-27 04:12:45.394 \[NOTICE\] Bootstrapped 5% (conn): Connecting to a relay 2026-05-27 04:13:50.828 \[WARN\] Problem bootstrapping. Stuck at 5% (conn): Connecting to a relay. (Connection timed out \[WSAETIMEDOUT \]; TIMEOUT; count 10; recommendation warn; host 0E66E082B67BE5D3894C4004CC189177D1A3B42D at 94.16.120.193:9001) 2026-05-27 04:13:50.829 \[WARN\] 9 connections have failed: 2026-05-27 04:13:50.829 \[WARN\] 9 connections died in state connect()ing with SSL state (No SSL object) 2026-05-27 04:13:50.831 \[WARN\] Problem bootstrapping. Stuck at 5% (conn): Connecting to a relay. (Connection timed out \[WSAETIMEDOUT \]; TIMEOUT; count 11; recommendation warn; host 9215A08C840208C79235D821C8B57BFB33245945 at 38.45.67.186:9001) 2026-05-27 04:13:50.832 \[WARN\] 10 connections have failed: 2026-05-27 04:13:50.832 \[WARN\] 10 connections died in state connect()ing with SSL state (No SSL object) 2026-05-27 04:13:50.983 \[NOTICE\] Closing no-longer-configured Socks listener on 127.0.0.1:9150 2026-05-27 04:13:50.983 \[NOTICE\] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2026-05-27 04:13:50.985 \[WARN\] connection_connect_sockaddr: Bug: Tried to open a socket with DisableNetwork set. (on Tor 0.4.9.8 e170cdcfebd45f6d) 2026-05-27 04:13:50.986 \[WARN\] tor_bug_occurred\_: Bug: connection.c:2200: connection_connect_sockaddr: This line should not have been reached. (Future instances of this warning will be silenced.) (on Tor 0.4.9.8 e170cdcfebd45f6d) 2026-05-27 04:13:50.986 \[WARN\] Bug: Tor 0.4.9.8 (git-e170cdcfebd45f6d): Line unexpectedly reached at connection_connect_sockaddr at connection.c:2200. (Stack trace not available) (on Tor 0.4.9.8 e170cdcfebd45f6d) 2026-05-27 04:13:51.337 \[NOTICE\] Delaying directory fetches: DisableNetwork is set. 2026-05-27 04:49:09.895 \[NOTICE\] Opening Socks listener on 127.0.0.1:9150 2026-05-27 04:49:09.895 \[NOTICE\] Opened Socks listener connection (ready) on 127.0.0.1:9150 2026-05-27 04:49:31.211 \[WARN\] Problem bootstrapping. Stuck at 5% (conn): Connecting to a relay. (Connection timed out \[WSAETIMEDOUT \]; TIMEOUT; count 12; recommendation warn; host 3DAF929D70A2B4D28E040EE5E3AC7F01FE67A9DF at 192.42.116.104:443) 2026-05-27 04:49:31.212 \[WARN\] 25 connections have failed: 2026-05-27 04:49:31.212 \[WARN\] 25 connections died in state connect()ing with SSL state (No SSL object) 2026-05-27 04:49:31.216 \[WARN\] Problem bootstrapping. Stuck at 5% (conn): Connecting to a relay. (Connection timed out \[WSAETIMEDOUT \]; TIMEOUT; count 13; recommendation warn; host B4DBFFC07EB79EEC4F68F1EC657A9A6D3420F54B at 194.164.173.152:21344) 2026-05-27 04:49:31.216 \[WARN\] 26 connections have failed: 2026-05-27 04:49:31.216 \[WARN\] 26 connections died in state connect()ing with SSL state (No SSL object) 2026-05-27 04:49:31.368 \[NOTICE\] Closing no-longer-configured Socks listener on 127.0.0.1:9150 2026-05-27 04:49:31.368 \[NOTICE\] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2026-05-27 04:49:31.369 \[WARN\] connection_connect_sockaddr: Bug: Tried to open a socket with DisableNetwork set. \[2 similar message(s) suppressed in last 2160 seconds\] (on Tor 0.4.9.8 e170cdcfebd45f6d) 2026-05-27 04:49:31.485 \[NOTICE\] Delaying directory fetches: DisableNetwork is set. 2026-05-27 05:07:18.940 \[NOTICE\] Opening Socks listener on 127.0.0.1:9150 2026-05-27 05:07:18.941 \[NOTICE\] Opened Socks listener connection (ready) on 127.0.0.1:9150 2026-05-27 05:07:18.941 \[NOTICE\] Our directory information is no longer up-to-date enough to build circuits: We have no recent usable consensus. 2026-05-27 05:07:40.132 \[WARN\] Problem bootstrapping. Stuck at 5% (conn): Connecting to a relay. (Connection timed out \[WSAETIMEDOUT \]; TIMEOUT; count 14; recommendation warn; host 3DAF929D70A2B4D28E040EE5E3AC7F01FE67A9DF at 192.42.116.104:443) 2026-05-27 05:07:40.133 \[WARN\] 29 connections have failed: 2026-05-27 05:07:40.133 \[WARN\] 29 connections died in state connect()ing with SSL state (No SSL object) 2026-05-27 05:07:40.151 \[NOTICE\] Closing no-longer-configured Socks listener on 127.0.0.1:9150 2026-05-27 05:07:40.152 \[NOTICE\] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2026-05-27 05:07:40.922 \[NOTICE\] Delaying directory fetches: DisableNetwork is set. 2026-05-27 05:10:26.633 \[NOTICE\] Opening Socks listener on 127.0.0.1:9150 2026-05-27 05:10:26.633 \[NOTICE\] Opened Socks listener connection (ready) on 127.0.0.1:9150 2026-05-27 05:10:48.399 \[WARN\] Problem bootstrapping. Stuck at 5% (conn): Connecting to a relay. (Connection timed out \[WSAETIMEDOUT \]; TIMEOUT; count 15; recommendation warn; host 643B4B2376FBA4E914A5490BBB26C8563873DC30 at 206.71.158.84:443) 2026-05-27 05:10:48.399 \[WARN\] 32 connections have failed: 2026-05-27 05:10:48.400 \[WARN\] 32 connections died in state connect()ing with SSL state (No SSL object) 2026-05-27 05:10:48.404 \[WARN\] Problem bootstrapping. Stuck at 5% (conn): Connecting to a relay. (Connection timed out \[WSAETIMEDOUT \]; TIMEOUT; count 16; recommendation warn; host 7BE683E65D48141321C5ED92F075C55364AC7123 at 193.23.244.244:443) 2026-05-27 05:10:48.404 \[WARN\] 33 connections have failed: 2026-05-27 05:10:48.404 \[WARN\] 33 connections died in state connect()ing with SSL state (No SSL object) 2026-05-27 05:10:48.418 \[NOTICE\] Closing no-longer-configured Socks listener on 127.0.0.1:9150 2026-05-27 05:10:48.418 \[NOTICE\] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2026-05-27 05:10:49.134 \[NOTICE\] Delaying directory fetches: DisableNetwork is set. ---------------------------------------------

No changes on my part I then got this today. Network card was firing up at first here.

2026-05-27 18:10:43.553 \[NOTICE\] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2026-05-27 18:10:43.560 \[NOTICE\] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2026-05-27 18:10:43.566 \[NOTICE\] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2026-05-27 18:10:46.361 \[NOTICE\] Opening Socks listener on 127.0.0.1:9150 2026-05-27 18:10:46.361 \[NOTICE\] Opened Socks listener connection (ready) on 127.0.0.1:9150 2026-05-27 18:10:46.541 \[NOTICE\] Bootstrapped 5% (conn): Connecting to a relay 2026-05-27 18:11:28.642 \[NOTICE\] Bootstrapped 10% (conn_done): Connected to a relay 2026-05-27 18:11:28.692 \[NOTICE\] Bootstrapped 14% (handshake): Handshaking with a relay 2026-05-27 18:11:28.801 \[WARN\] Received NETINFO cell with skewed time (OR:199.58.81.140:443): It seems that our clock is ahead by 2 hours, 59 minutes, or that theirs is behind. Tor requires an accurate clock to work: please check your time, timezone, and date settings. 2026-05-27 18:11:28.802 \[WARN\] Problem bootstrapping. Stuck at 14% (handshake): Handshaking with a relay. (Clock skew 10750 in NETINFO cell from OR; CLOCK_SKEW; count 4; recommendation warn; host 74A910646BCEEFBCD2E874FC1DC997430F968145 at 199.58.81.140:443) 2026-05-27 18:11:28.803 \[WARN\] 3 connections have failed: 2026-05-27 18:11:28.803 \[WARN\] 3 connections died in state connect()ing with SSL state (No SSL object) 2026-05-27 18:11:28.805 \[NOTICE\] Bootstrapped 15% (handshake_done): Handshake with a relay done 2026-05-27 18:11:28.808 \[NOTICE\] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection 2026-05-27 18:11:28.820 \[NOTICE\] Closing no-longer-configured Socks listener on 127.0.0.1:9150 2026-05-27 18:11:28.821 \[NOTICE\] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2026-05-27 18:11:29.585 \[NOTICE\] Delaying directory fetches: DisableNetwork is set 

Then this.

2026-05-27 18:22:36.541 \[NOTICE\] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2026-05-27 18:22:36.546 \[NOTICE\] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2026-05-27 18:22:36.552 \[NOTICE\] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2026-05-27 18:22:43.781 \[NOTICE\] Opening Socks listener on 127.0.0.1:9150 2026-05-27 18:22:43.781 \[NOTICE\] Opened Socks listener connection (ready) on 127.0.0.1:9150 2026-05-27 18:22:44.536 \[NOTICE\] Bootstrapped 5% (conn): Connecting to a relay 2026-05-27 18:23:05.687 \[NOTICE\] Bootstrapped 10% (conn_done): Connected to a relay 2026-05-27 18:23:05.772 \[NOTICE\] Bootstrapped 14% (handshake): Handshaking with a relay 2026-05-27 18:23:06.001 \[WARN\] Received NETINFO cell with skewed time (OR:204.13.164.118:443): It seems that our clock is ahead by 2 hours, 59 minutes, or that theirs is behind. Tor requires an accurate clock to work: please check your time, timezone, and date settings. 2026-05-27 18:23:06.002 \[WARN\] Problem bootstrapping. Stuck at 14% (handshake): Handshaking with a relay. (Clock skew 10750 in NETINFO cell from OR; CLOCK_SKEW; count 2; recommendation warn; host 24E2F139121D4394C54B5BCC368B3B411857C413 at 204.13.164.118:443) 2026-05-27 18:23:06.002 \[WARN\] 1 connections have failed: 2026-05-27 18:23:06.003 \[WARN\] 1 connections died in state connect()ing with SSL state (No SSL object) 2026-05-27 18:23:06.005 \[NOTICE\] Bootstrapped 15% (handshake_done): Handshake with a relay done 2026-05-27 18:23:06.007 \[NOTICE\] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection 2026-05-27 18:23:06.021 \[NOTICE\] Closing no-longer-configured Socks listener on 127.0.0.1:9150 2026-05-27 18:23:06.021 \[NOTICE\] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2026-05-27 18:23:06.559 \[NOTICE\] Delaying directory fetches: DisableNetwork is set. 2026-05-27 15:26:31.778 \[NOTICE\] Your system clock just jumped 10752 seconds backward; assuming established circuits no longer work. 2026-05-27 15:26:32.781 \[NOTICE\] Heartbeat: Tor's uptime is 0:03 hours, with 0 circuits open. I've sent 2 kB and received 3 kB. I've received 1 connections on IPv4 and 0 on IPv6. I've made 4 connections with IPv4 and 0 with IPv6. 2026-05-27 15:26:32.782 \[NOTICE\] Average packaged cell fullness: 100.000%. TLS write overhead: 162% 

I read in the previous log that [It seems that our clock is ahead by 2 hours, 59 minutes, or that theirs is behind] So I set the difference on my PC’s clock and got this. Bug is back.

2026-05-27 15:27:52.732 \[NOTICE\] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2026-05-27 15:27:52.737 \[NOTICE\] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2026-05-27 15:27:52.743 \[NOTICE\] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2026-05-27 15:28:10.125 \[NOTICE\] Opening Socks listener on 127.0.0.1:9150 2026-05-27 15:28:10.126 \[NOTICE\] Opened Socks listener connection (ready) on 127.0.0.1:9150 2026-05-27 15:28:10.724 \[NOTICE\] Bootstrapped 5% (conn): Connecting to a relay 2026-05-27 15:29:13.851 \[NOTICE\] Bootstrapped 10% (conn_done): Connected to a relay 2026-05-27 15:29:13.902 \[NOTICE\] Bootstrapped 14% (handshake): Handshaking with a relay 2026-05-27 15:29:14.011 \[NOTICE\] Bootstrapped 15% (handshake_done): Handshake with a relay done 2026-05-27 15:29:14.013 \[NOTICE\] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection 2026-05-27 15:29:14.062 \[NOTICE\] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus 2026-05-27 15:29:14.096 \[NOTICE\] Bootstrapped 30% (loading_status): Loading networkstatus consensus 2026-05-27 15:29:19.838 \[NOTICE\] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits 2026-05-27 15:29:20.431 \[NOTICE\] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits 2026-05-27 15:29:41.178 \[WARN\] Problem bootstrapping. Stuck at 80% (ap_conn): Connecting to a relay to build circuits. (Connection timed out \[WSAETIMEDOUT \]; TIMEOUT; count 10; recommendation warn; host 0E66E082B67BE5D3894C4004CC189177D1A3B42D at 94.16.120.193:9001) 2026-05-27 15:29:41.178 \[WARN\] 9 connections have failed: 2026-05-27 15:29:41.179 \[WARN\] 9 connections died in state connect()ing with SSL state (No SSL object) 2026-05-27 15:29:41.181 \[WARN\] Problem bootstrapping. Stuck at 80% (ap_conn): Connecting to a relay to build circuits. (Connection timed out \[WSAETIMEDOUT \]; TIMEOUT; count 11; recommendation warn; host 9215A08C840208C79235D821C8B57BFB33245945 at 38.45.67.186:9001) 2026-05-27 15:29:41.181 \[WARN\] 10 connections have failed: 2026-05-27 15:29:41.181 \[WARN\] 10 connections died in state connect()ing with SSL state (No SSL object) 2026-05-27 15:29:41.540 \[NOTICE\] Closing no-longer-configured Socks listener on 127.0.0.1:9150 2026-05-27 15:29:41.540 \[NOTICE\] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2026-05-27 15:29:41.543 \[WARN\] connection_connect_sockaddr: Bug: Tried to open a socket with DisableNetwork set. (on Tor 0.4.9.8 e170cdcfebd45f6d) 2026-05-27 15:29:41.543 \[WARN\] tor_bug_occurred\_: Bug: connection.c:2200: connection_connect_sockaddr: This line should not have been reached. (Future instances of this warning will be silenced.) (on Tor 0.4.9.8 e170cdcfebd45f6d) 2026-05-27 15:29:41.543 \[WARN\] Bug: Tor 0.4.9.8 (git-e170cdcfebd45f6d): Line unexpectedly reached at connection_connect_sockaddr at connection.c:2200. (Stack trace not available) (on Tor 0.4.9.8 e170cdcfebd45f6d) 2026-05-27 15:29:41.868 \[NOTICE\] Delaying directory fetches: DisableNetwork is set. 

Reset my PC clock to correct time and got this.

2026-05-27 18:35:37.444 \[NOTICE\] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2026-05-27 18:35:37.450 \[NOTICE\] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2026-05-27 18:35:37.456 \[NOTICE\] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2026-05-27 18:36:00.569 \[NOTICE\] Opening Socks listener on 127.0.0.1:9150 2026-05-27 18:36:00.569 \[NOTICE\] Opened Socks listener connection (ready) on 127.0.0.1:9150 2026-05-27 18:36:00.571 \[NOTICE\] Bootstrapped 5% (conn): Connecting to a relay 2026-05-27 18:37:06.315 \[WARN\] Problem bootstrapping. Stuck at 5% (conn): Connecting to a relay. (Connection timed out \[WSAETIMEDOUT \]; TIMEOUT; count 10; recommendation warn; host 9215A08C840208C79235D821C8B57BFB33245945 at 38.45.67.186:9001) 2026-05-27 18:37:06.315 \[WARN\] 9 connections have failed: 2026-05-27 18:37:06.315 \[WARN\] 9 connections died in state connect()ing with SSL state (No SSL object) 2026-05-27 18:37:06.317 \[WARN\] Problem bootstrapping. Stuck at 5% (conn): Connecting to a relay. (Connection timed out \[WSAETIMEDOUT \]; TIMEOUT; count 11; recommendation warn; host 102162A0695EF4539543491B11230573034DCC52 at 173.249.215.154:9001) 2026-05-27 18:37:06.317 \[WARN\] 10 connections have failed: 2026-05-27 18:37:06.318 \[WARN\] 10 connections died in state connect()ing with SSL state (No SSL object) 2026-05-27 18:37:06.320 \[WARN\] Problem bootstrapping. Stuck at 5% (conn): Connecting to a relay. (Connection timed out \[WSAETIMEDOUT \]; TIMEOUT; count 12; recommendation warn; host 87E79F4B6F9C321B5110F4C0C63DA1853CAF4732 at 94.23.170.63:9001) 2026-05-27 18:37:06.320 \[WARN\] 11 connections have failed: 2026-05-27 18:37:06.320 \[WARN\] 11 connections died in state connect()ing with SSL state (No SSL object) 2026-05-27 18:37:06.480 \[NOTICE\] Closing no-longer-configured Socks listener on 127.0.0.1:9150 2026-05-27 18:37:06.480 \[NOTICE\] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2026-05-27 18:37:06.482 \[WARN\] connection_connect_sockaddr: Bug: Tried to open a socket with DisableNetwork set. (on Tor 0.4.9.8 e170cdcfebd45f6d) 2026-05-27 18:37:06.482 \[WARN\] tor_bug_occurred\_: Bug: connection.c:2200: connection_connect_sockaddr: This line should not have been reached. (Future instances of this warning will be silenced.) (on Tor 0.4.9.8 e170cdcfebd45f6d) 2026-05-27 18:37:06.482 \[WARN\] Bug: Tor 0.4.9.8 (git-e170cdcfebd45f6d): Line unexpectedly reached at connection_connect_sockaddr at connection.c:2200. (Stack trace not available) (on Tor 0.4.9.8 e170cdcfebd45f6d) 2026-05-27 18:37:06.833 \[NOTICE\] Delaying directory fetches: DisableNetwork is set.

I installed Cloudflare warp to install Duckduckgo browser and Tor logged right on. Looks like my network /PC is blacklisted on Tor.

I use router iptables firewall which Warp defeats so this is not a solution for me.

The problem is not solved. My Internet is open but Tor is still showing a bug. Help!

WARN Bug: 0.4.9.8

Bootstrapped to 80% today bug warning is gone. I do believe this is a network issue.

Cloudflare Warp and many other programs using tun2socks often send TCP SYN+ACK before TCP connections are actually established, this behavior may confuse tor. You can verify it by using TCP ping programs or using curl with --trace - --trace-time

Thank you protium_serratum .

There is no problem connecting with WARP , going through the 1.1.1.1 Cloudflare network I get right on TOR but my DD-WRT firewall is defeated as all data passes through 1.1.1.1. .

If I just use TOR with ip’s opened in firewall to connect to TOR my firewall is still working. Always the beauty of TOR for for years, but after more than 10 years just stopped working.

Happy Happy!!! The TOR gods opened up the sky blue and low and behold I am posting this from TOR on my Windows 10 machine.

\[NOTICE\] Bootstrapped 100% (done): Done
2026-06-09 00:10:53.287
\[WARN\] Guard Esquie ($C26AF1347BCBB31E20089FBF9C338B0843FC171D) is failing an extremely large amount of circuits. This could indicate a route manipulation attack, extreme network overload, or a bug. Success counts are 5/151. Use counts are 2/2. 147 circuits completed, 0 were unusable, 142 collapsed, and 146 timed out. For reference, your timeout cutoff is 60 seconds.
2026-06-09 00:20:04.710
\[NOTICE\] Failed to find node for hop #1 of our path. Discarding this circuit.
2026-06-09 00:20:04.710
\[NOTICE\] Our circuit 0 (id: 164) died due to an invalid selected path, purpose General-purpose client. This may be a torrc configuration issue, or a bug.
2026-06-09 00:20:20.774
\[NOTICE\] No circuits are opened. Relaxed timeout for circuit 120 (a Measuring circuit timeout 3-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway.
2026-06-09 00:21:36.952
\[NOTICE\] Failed to find node for hop #1 of our path. Discarding this circuit.
2026-06-09 00:23:25.034
\[NOTICE\] Failed to find node for hop #1 of our path. Discarding this circuit.
2026-06-09 00:25:02.197
\[NOTICE\] Failed to find node for hop #1 of our path. Discarding this circuit.
2026-06-09 00:28:38.696
\[NOTICE\] Failed to find node for hop #1 of our path. Discarding this circuit.
2026-06-09 00:30:43.043
\[WARN\] Rejecting SOCKS request for anonymous connection to private address \[scrubbed\].

Got slow for a moment I think because of the

\[NOTICE\] Failed to find node for hop #1 of our path. Discarding this circuit.

and now it looks to be good to go.

Thank you everyone for all your efforts!!!