Connexió al Tor

If you’re having trouble connecting, an error message may appear and you can select the option to "copy Tor log to clipboard". A continuació, enganxeu el registre de Tor en un fitxer de text o en un altre document.

If you don't see this option and you have Tor Browser open, you can navigate to the hamburger menu ("≡"), then click on "Preferences", and finally on "Tor" in the side bar. At the bottom of the page, next to the "View the Tor logs" text, click the button "View Logs...".

Alternatively, 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:

‪./start-tor-browser.desktop --verbose

or to save the logs to a file (default: tor-browser.log)

‪./start-tor-browser.desktop --log [file]

Heu de veure un d'aquests errors de registre comuns (busqueu les següents línies al vostre registre de Tor):

Common log error #1: Proxy connection failure

2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150
2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server
2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server
2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx ("general SOCKS server failure")

Si veieu línies com aquestes al vostre registre de Tor, significa que no esteu connectant a un proxy SOCKS. Si es requereix un proxy SOCKS per a la configuració de la xarxa, assegureu-vos que heu introduït correctament els vostres detalls del proxy. Si no es requereix un proxy SOCKS, o no esteu segur, intenteu connectar-vos a la xarxa Tor sense un proxy SOCKS.

Common log error #2: Can’t reach guard relays

11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150
11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network
11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop
11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.

Si veieu línies com aquestes en el vostre registre Tor, significa que Tor no s'ha pogut connectar al primer node del circuit Tor. Això podria significar que estàs en una xarxa censurada.

Intenteu connectar-vos amb ponts i això hauria de solucionar el problema.

Common log error #3: Failed to complete TLS handshake

13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server 
13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) 
13-11-17 19:53:49.300 [WARN] 10 connections have failed: 
13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE 
13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)

Si veieu línies com aquesta al registre Tor, significa que Tor no ha pogut completar una encaixada de mans de TLS amb les autoritats del directori. Usar ponts probablement solucionarà això.

Common log error #4: Clock skew

19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 
19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server 
19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server 
19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time, timezone, and date settings.

Si veieu línies com aquesta en el vostre registre Tor, significa que el vostre rellotge del sistema no és correcte. Assegureu-vos que el rellotge s'estableixi amb precisió, inclosa la zona horària correcta. Torneu a iniciar Tor.

Un dels problemes més comuns que causa errors de connexió al navegador Tor és un rellotge del sistema incorrecte. Assegureu-vos que el rellotge del sistema i el fus horari estiguin configurats amb precisió. If this doesn't fix the problem, see the Troubleshooting page on the Tor Browser manual.

If you cannot reach the onion service you desire, make sure that you have entered the 16-character or, the newest format, 56-character onion address correctly; even a small mistake will stop Tor Browser from being able to reach the site. Si encara no podeu connectar-vos al servei de onion, torneu-ho a provar més tard. És possible que hi hagi un problema de connexió temporal o que els operadors del lloc hagin permès que es desconnectés sense previ avís.

You can also ensure that you're able to access other onion services by connecting to DuckDuckGo's onion service.

Proxy server errors can occur for a variety of reasons. You may try one or more of the following activities in case you encounter this error:

  • If you have an antivirus, it may be interfering with the Tor service. Disable the antivirus and restart the browser.
  • You should not have moved the Tor Browser folder from its original location to a different location. If you did this, revert the change.
  • You should also check the port that you are connecting with. Try a different port from the one currently in use, such as 9050 or 9150.
  • When all else fails, reinstall the browser. This time, make sure to install Tor Browser in a new directory, not over a previously installed browser.

If the error persists, please get in touch with us.