If you are having trouble connecting, an error message may appear and you can select the “copy or log to clipboard” option. then paste the tor login into a text file or other document.
If you don’t see this option and you have a browser open, you can navigate to the hamburger menu (“≡”), then click “settings” and finally “connection” in the sidebar. at the bottom of the page, next to the “view tor logs” text, click the “view logs…” button.
Reading: How to connect to tor browser
Alternatively, on gnu/linux, to view the logs directly in the terminal, navigate to the tor browser directory and start the tor browser from the command line by running:
o to save the logs to a file (default: tor-browser.log)
./start-tor-browser.desktop -log [file]
You should see one of these common log errors (look for the following lines in your tor log):
Common Log Error #1: Proxy Connection Error
If you see lines like these in your tor log, it means you can’t connect to a socks proxy. If a socks proxy is required for your network setup, make sure you have entered your proxy details correctly. if a socks proxy is not required, or you are unsure, try connecting to the tor network without a socks proxy.
Common Log Error #2: Unable to reach protection relays
If you see lines like these in your tor log, it means your tor was unable to connect to the first node in the tor circuit. this could mean you are on a censored network.
try connecting with bridges, and that should fix the problem.
Common Log Error #3: Failed to complete tls handshake
If you see lines like this in your tor log, it means that tor was unable to complete a tls handshake with the directory authorities. using bridges will probably fix this.
Common Log Error #4: Clock Skew
If you see lines like this in your tor log, it means your system clock is wrong. Make sure your watch is set accurately, including the correct time zone. then restart tor.