21:11:45 PM.300 Failed to find node for hop 0 of our path. 21:11:44 PM.500 Bootstrapped 85%: Finishing handshake with first hop 21:11:44 PM.300 Failed to find node for hop 0 of our path. 21:11:44 PM.300 Bootstrapped 80%: Connecting to the Tor network Common log error #2: Can’t reach guard relays 21:11:43 PM.500 Opening Socks listener on 127.0.0.1:9150 If a SOCKS proxy is not required, or you’re not sure, please try connecting to the Tor network without a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly. If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. 09:24:08.900 Proxy Client: unable to connect to xx.:xxxxx ('general SOCKS server failure') 09:23:47.900 Bootstrapped 10%: Finishing handshake with directory server 09:23:47.900 Bootstrapped 5%: Connecting to directory server You should see one of these common log errors (look for the following lines in your Tor log): Common log error #1: Proxy connection failure 09:23:40.800 Opening Socks listener on 127.0.0.1:9150 Or to save the logs to a file (default: tor-browser.log) If you don't see this option and you have Tor Browser open, you can navigate to the hamburger menu ('≡'), then click on 'Settings', and finally on 'Connection' in the side bar.Īt the bottom of the page, next to the 'View the Tor logs' text, click the button 'View Logs.'.Īlternatively, on GNU/Linux, to view the logs right in the terminal, navigate to the Tor Browser directory and launch the Tor Browser from the command line by running: Then paste the Tor log into a text file or other document.

If you’re having trouble connecting, an error message may appear and you can select the option to 'copy Tor log to clipboard'.

Tor browser not connecting