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

  1. The computer clock is set to an incorrect time zone
  2. You need to sign in to the network
  3. The progress bar gets stuck around 50%
  4. The bridge is no longer operational
  5. Learning about another bridge
  6. You did not enter the bridge correctly

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 Tor 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. In the error screen of the Tor Connection assistant, choose Try Signing in to the Network.

  2. Wait until the Unsafe Browser starts.

  3. 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 extremely slow.

To fix this, you can either:

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

  • Try with another bridge.

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

The bridge is no longer operational

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

Try with another bridge.

Learning about another bridge

To learn about other Tor bridges, you have several options listed below.

None of these options is easy to do from Tails, so we recommend that you learn about several bridges from your regular computer before starting Tails and store the bridge lines in a text document on separate USB stick.

After you restarted on Tails, you can copy one of these bridge lines from this other USB stick into Tor Connection.

Even someone who knows your bridge cannot know what you are doing online from Tails.

  • CAPTCHA

    You can solve a CAPTCHA on https://bridges.torproject.org/.

    We recommend doing so from a different local network if you want to hide that you are connecting to Tor.

  • Email

    You can send an empty email to bridges@torproject.org from a Gmail or Riseup email address.

    Sending the email reveals to Gmail or Riseup that you are trying to connect to Tor but not to someone who monitors your Internet connection.

  • Telegram

    You can send the message /bridges to @GetBridgesBot on Telegram.

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.