The sections below summarize the most common problems when connecting to Tor.

The computer clock is set to an incorrect time zone

The clock of the computer needs to be correct to connect to Tor.

If you choose to hide that you are connecting to Tor, you might have to fix the clock manually if Tails fails to connect to Tor.

Choose Fix Clock in the error screen of the Tor Connection assistant to set the clock and time zone of your computer.

If you have problems fixing the clock, you can instead try to restart Tails and choose to connect to Tor automatically. When connecting to Tails automatically, Tails fixes the clock automatically by connecting to the captive portal detection service of Fedora before connecting to Tor.

You need to sign in to the network

A captive portal is a web page that is often displayed before you can access the Internet on public networks in airports, hotels, libraries, and other places.

Train station Wi-Fi. Click here for 60 minutes of free Wi-Fi

Tails cannot connect to the Tor network when the Internet connection is initially blocked by a captive portal.

To sign in to a network using a captive portal:

  1. Restart Tails.

  2. When the Welcome Screen appears, click on the Add Additional Setting button.

  3. Choose Unsafe Browser in the Additional Settings dialog.

  4. Select the Enable the Unsafe Browser option.

  5. Click Start Tails.

  6. Try connecting to the Tor network again using the Tor Connection assistant.

  7. In the error screen of the Tor Connection assistant, choose Try Signing in to the Network.

  8. In the warning, choose Launch to start the Unsafe Browser.

  9. Follow the instructions on the homepage of the Unsafe Browser.

The progress bar gets stuck around 50%

When using a custom Tor obfs4 bridge, the progress bar of Tor Connection sometimes gets stuck halfway through and becomes extremelly slow.

To fix this, you can either:

  • Close and reopen Tor Connection to speed up the initial connection.

  • Try a different obfs4 bridge.

This issue only affects outdated obfs4 bridges and does not happen with obfs4 bridges that run version 0.0.12 or later. (#19173)

The bridge is no longer operational

It is possible that the bridge that you entered is no longer working.

Try entering another bridge or requesting other bridges.

You did not enter the bridge correctly

Only obfs4 bridges can be used in Tails currently.

An obfs4 bridge looks like:

obfs4 1.2.3.4:1234 B0E566C9031657EA7ED3FC9D248E8AC4F37635A4 cert=OYWq67L7MDApdJCctUAF7rX8LHvMxvIBPHOoAp0+YXzlQdsxhw6EapaMNwbbGICkpY8CPQ iat-mode=0

You need to enter the entire line, not just the IP address and port combination.