#26264 closed defect (not a bug)

I can't connect anymore to tor

Reported by: xfederico Owned by: tbb-team
Priority: Medium Milestone: Tor: unspecified
Component: Applications/Tor Browser Version: Tor: unspecified
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

5/31/2018 5:03:10 AM.600 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
5/31/2018 5:03:15 AM.900 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
5/31/2018 5:03:15 AM.900 [NOTICE] Switching to guard context "default" (was using "bridges")
5/31/2018 5:03:15 AM.900 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
5/31/2018 5:03:15 AM.900 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
5/31/2018 5:03:15 AM.900 [NOTICE] Opening Socks listener on 127.0.0.1:9150
5/31/2018 5:03:15 AM.900 [NOTICE] Bootstrapped 5%: Connecting to directory server
5/31/2018 5:03:16 AM.000 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server
5/31/2018 5:03:16 AM.400 [NOTICE] Bootstrapped 15%: Establishing an encrypted directory connection
5/31/2018 5:03:16 AM.600 [NOTICE] Bootstrapped 20%: Asking for networkstatus consensus
5/31/2018 5:03:16 AM.700 [NOTICE] Bootstrapped 25%: Loading networkstatus consensus
5/31/2018 5:03:22 AM.100 [WARN] Received NETINFO cell with skewed time (OR:199.58.81.140:443): It seems that our clock is behind by 2 days, 0 hours, 0 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time, timezone, and date settings.
5/31/2018 5:03:22 AM.100 [WARN] Problem bootstrapping. Stuck at 25%: Loading networkstatus consensus. (Clock skew -172813 in NETINFO cell from OR; CLOCK_SKEW; count 2; recommendation warn; host 74A910646BCEEFBCD2E874FC1DC997430F968145 at 199.58.81.140:443)
5/31/2018 5:03:22 AM.100 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
5/31/2018 5:03:22 AM.100 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
5/31/2018 5:03:22 AM.100 [NOTICE] Closing old Socks listener on 127.0.0.1:9150
5/31/2018 5:03:22 AM.800 [NOTICE] Delaying directory fetches: DisableNetwork is set.

Child Tickets

Change History (3)

comment:1 Changed 17 months ago by teor

5/31/2018 5:03:22 AM.100 [WARN] Received NETINFO cell with skewed time (OR:199.58.81.140:443): It seems that our clock is behind by 2 days, 0 hours, 0 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time, timezone, and date settings.

Please set your computer's clock to the correct date.

comment:2 Changed 17 months ago by Dbryrtfbcbhgf

Priority: ImmediateMedium
Severity: BlockerNormal

comment:3 Changed 17 months ago by gk

Resolution: not a bug
Status: newclosed

What teor said. I'd say that's a configuration error and not a Tor Browser bug.

Note: See TracTickets for help on using tickets.