en	[[!meta title="Troubleshooting connecting to Tor"]]

en	The sections below summarize the most common problems when [[connecting to Tor|tor]].

en	[[!toc startlevel=2]]

en	The computer clock is set to an incorrect time zone

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

en	If you choose to [[hide that you are connecting to Tor|tor#hiding]], you might have to fix the clock manually if Tails fails to connect to Tor.

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

en	If you have problems fixing the clock, you can instead try to restart Tails and choose to [[connect to Tor automatically|tor#automatic]]. When connecting to Tor automatically, Tails fixes the clock automatically by connecting to the captive portal detection service of [Fedora](http://fedoraproject.org/static/hotspot.txt) before connecting to Tor.

en	You need to sign in to the network

en	[[!inline pages="doc/anonymous_internet/unsafe_browser/captive_portal.inline" raw="yes" sort="age"]]
id	[[!inline pages="doc/anonymous_internet/unsafe_browser/captive_portal.inline.id" raw="yes" sort="age"]]

en	To sign in to a network using a captive portal:

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

en	Wait until the *Unsafe Browser* starts.

en	Follow the instructions on the home page of the *Unsafe Browser*.

en	You need to configure a Tor bridge

en	[[!inline pages="doc/anonymous_internet/tor/bridge.inline" raw="yes" sort="age"]]
id	[[!inline pages="doc/anonymous_internet/tor/bridge.inline.id" raw="yes" sort="age"]]

en	The progress bar gets stuck around 50%

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

en	[[!img stuck.png link="no" alt=""]]

en	To fix this, you can either:

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

en	Try with [[another bridge|troubleshoot#bridge]].

en	<div class="bug">

en	<!--

en	On 2025-09-04, the Anticensorship Team believed that there were still many bridges with an obfs4 version earlier than 0.0.12.

en	Their "transport-info" info in cached-extrainfo is too new to give us reliable information.

en	-->

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

en	</div>

en	The bridge is no longer operational

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

en	You did not enter the bridge correctly

en	You can use *obfs4* and *WebTunnel* bridges in Tails right now.

en	An *obfs4* bridge looks like:

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

en	A *WebTunnel* bridge looks like:

en	webtunnel [1234:567:890a:bcde:f123:4567:890a:bcde]:443 5F55B60FF2AEA996B5109BC338FC5F2BCA696F52 url=https://example.com/webtunnel ver=0.0.1

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