Opened 2 years ago

Closed 2 years ago

Last modified 2 years ago

#22941 closed defect (duplicate)

Bootstrapped frozen at 85% : Failed to find node for hop 0 of our path.

Reported by: JohnMilos Owned by:
Priority: Medium Milestone:
Component: Core Tor/Tor Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Hi all,
since a tor update, i can't no longer connect to tor.
Look at the log :

15/07/2017 17:09:12.700 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
15/07/2017 17:09:12.700 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
15/07/2017 17:09:12.700 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
15/07/2017 17:09:12.700 [NOTICE] Opening Socks listener on 127.0.0.1:9150
15/07/2017 17:09:13.700 [NOTICE] Bootstrapped 80%: Connecting to the Tor network
15/07/2017 17:09:13.700 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
15/07/2017 17:09:14.000 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop
15/07/2017 17:09:14.700 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
15/07/2017 17:09:15.700 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
15/07/2017 17:09:16.700 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
15/07/2017 17:09:17.700 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
15/07/2017 17:09:18.700 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
15/07/2017 17:09:19.700 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
15/07/2017 17:09:20.700 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
15/07/2017 17:09:21.700 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
15/07/2017 17:09:22.700 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
15/07/2017 17:09:23.700 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
15/07/2017 17:09:24.700 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
15/07/2017 17:09:24.900 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
15/07/2017 17:09:24.900 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
15/07/2017 17:09:24.900 [NOTICE] Closing old Socks listener on 127.0.0.1:9150
15/07/2017 17:09:25.700 [NOTICE] Delaying directory fetches: DisableNetwork is set.

I'm on Windows.
Thanks for the help !

Child Tickets

Change History (8)

comment:1 Changed 2 years ago by cypherpunks

Component: - Select a componentCore Tor/Tor
Status: newneeds_information

Which version of Windows? Which version of Tor? Can you add any more details? Thanks!

comment:2 Changed 2 years ago by JohnMilos

Windows 7 ; appVersion="7.0.2".
It always worked. Recently, after maybe 2 months, i decided to launch Tor : i have visited some pages, then it had to restart to install a new update. It restarted and never worked again.
Regards,

Last edited 2 years ago by JohnMilos (previous) (diff)

comment:3 Changed 2 years ago by cypherpunks

Last edited 2 years ago by cypherpunks (previous) (diff)

comment:4 Changed 2 years ago by JohnMilos

Hi,
i checked time, time zone and date => all is ok.
Also downloaded another fresh tor browser package => launched it and same issue.
I'm a bit lost i must admit !

comment:5 Changed 2 years ago by cypherpunks

Last edited 2 years ago by cypherpunks (previous) (diff)

comment:6 Changed 2 years ago by JohnMilos

What do you mean by "triggered by old cached stuff and some recent fix maybe" ?
I tried Tor Browser from 2 distinct directories : from a key usb and another fresh downloaded version on the desktop. Only common thing is the computer.
Time is ok, date also.
I've tried with and without VPN => same issue.
By the way, i don't think it's possible to perfectly synchronize time on a PC ? 2 sec ahead or not ? It makes a difference ?

comment:7 Changed 2 years ago by JohnMilos

Ok, sorry my mistake !
All was ok but not the timezone : settled initially on UTC-08:00 strangely !
I selected UTC+01:00 and all looks ok now.
Thanks to all.
Thread to close.

comment:8 Changed 2 years ago by cypherpunks

Resolution: duplicate
Status: needs_informationclosed
Last edited 2 years ago by cypherpunks (previous) (diff)
Note: See TracTickets for help on using tickets.