Troubleshooting
Tor Browser Not Connecting? How to Fix It
If the Tor Browser opens but gets stuck on “Connecting…” and never loads a website, you're not alone. It's the most common problem people run into, and it's usually fixable. In most cases the problem isn't Tor itself: your network is quietly blocking the connection. This guide covers the fixes that actually work, starting with the one that solves it most often.
Quick answer
The fix that works most often: use a bridge
If Tor fails to connect, click “Try a Bridge” when Tor Browser offers it. That's Connection Assist, which picks a bridge that works in your country. If there's no such button, go to Settings → Connection, click “Select a built-in bridge…”, choose obfs4 (or Snowflake), and connect. In Russia, Iran, or China, a WebTunnel bridge often works when nothing else does. (In Russia? Telegram is blocked there, so see the Russia steps below.)
What your error message means
Tor Browser usually tells you why it can't connect. Find your message below to jump straight to the right fix.
| You see… | It usually means | What to do |
|---|---|---|
| “Tor Browser could not connect to Tor” or “Tor network: Potentially blocked” | Your network blocks Tor | Click “Try a Bridge”, or turn on a bridge |
| “Tor failed to establish a Tor network connection” | Tor couldn't reach the network: blocked, wrong clock, or blocked by security software | Try a bridge, then check your clock and antivirus |
| “Tor Browser couldn't reach the Internet” or “Internet: Offline” | No internet connection, or a firewall or proxy is in the way | Check that a normal browser works, then check your firewall and proxy settings |
| “Tor Browser couldn't locate you” | Connection Assist doesn't know your country | Choose your country under “Unblock the Internet in”, then “Try a Bridge” |
| “Tor Browser still cannot connect” or “None of the configurations we tried worked” | Even the automatic bridges are blocked | Get a WebTunnel bridge or fresh bridges, or ask Tor support |
| “Tor exited during startup” or “Tor unexpectedly exited” | Something stopped Tor from running, often an antivirus | Allow Tor in your antivirus, or reinstall into a fresh folder |
On Android the wording is friendlier, for example “We can't connect to Tor directly,” but the fixes are the same.
Fix #1: let Connection Assist find a bridge
When a normal connection fails, Tor Browser can pick a bridge for you based on your location. This feature is called Connection Assist. It's the fastest fix for most people in censored countries, and it can even hand out the newer WebTunnel bridges automatically.
-
Wait for the error screen
After a failed attempt, Tor Browser shows a message such as “Tor Browser could not connect to Tor.”
-
Choose your location
Under “Unblock the Internet in”, keep Automatic or pick your country.
-
Click “Try a Bridge”
Give it a minute; it may try more than once. If it connects, you're done.
Fix #2: turn on a bridge yourself
A bridge is a hidden, disguised entry point into the Tor network that gets around blocks. Tor Browser includes three. These steps match Tor Browser 15 on desktop:
-
Open the connection settings
On the “Connect to Tor” screen, click Configure Connection…. Otherwise, go to ☰ menu → Settings → Connection, or type
about:preferences#connectionin the address bar. -
Click “Select a built-in bridge…”
It's in the Bridges section.
-
Choose obfs4 (or Snowflake)
obfs4 works on most networks. If it's blocked where you are, choose Snowflake. Keep meek as a last resort, because it's slow.
-
Confirm and connect
Make sure “Use bridges” is on, then connect. A working bridge shows as Connected.
On Android
Go to Settings (⚙) → Config Bridge, switch on “Use a Bridge”, and choose obfs4, Snowflake, or meek.
Which bridge to try: obfs4, Snowflake, WebTunnel, meek
-
obfs4 (built in)
Makes your Tor traffic look like random data. The best first choice on most networks.
-
Snowflake (built in)
Routes through volunteer proxies so your connection looks like a video call. A strong alternative when obfs4 is blocked.
-
WebTunnel (request one)
Makes Tor look like a normal visit to an HTTPS website. It often works in heavy censorship, such as Russia's mobile networks, Iran, and China. It isn't built in: send
/webtunnelto @GetBridgesBot on Telegram, or, in Russia, where Telegram is blocked, ask Tor support. (Step-by-step WebTunnel setup) -
meek (built in)
Goes through a big content delivery network. It can get through tough blocks but is usually very slow, so treat it as a last resort.
Full guide: how to set up Tor bridges, including where to get fresh ones.
In Russia? What works in 2026
Russia has blocked direct connections to Tor since December 2021, so you'll almost always need a bridge. It still works for most people: Tor Metrics estimates that around 90,000 people in Russia connect through bridges every day (compare other countries in our Tor censorship tracker). A few things are different there, though.
-
Start with “Try a Bridge”
For Russia, Connection Assist tries Snowflake first, then WebTunnel, then obfs4. Choose Russia under “Unblock the Internet in” and give it a few minutes.
-
On mobile data, use WebTunnel
Most Russian mobile carriers block obfs4. If Tor works on home Wi-Fi but not on mobile data, that's why. Use a WebTunnel bridge instead.
-
Telegram is blocked, so the bots may not open
Since March 2026, many Russian providers block Telegram, which also cuts off @GetBridgesBot and @TorProjectSupportBot, and bridges.torproject.org is blocked too. Other official sources: Request bridges… inside Tor Browser, or an email to bridges@torproject.org from a Gmail or Riseup address. Both give obfs4 bridges.
-
Ask for a private WebTunnel bridge
The Tor Project's support team hands out private bridges. Email frontdesk@torproject.org or message the team on Signal (+1 778 743 1312) or WhatsApp (+44 7421 000612), and include “private bridge ru” in your message. They reply Monday to Thursday.
-
Snowflake comes and goes
Since spring 2026, Russian censors have been filtering Snowflake, so it may connect one day and fail the next. If it stops working, switch to WebTunnel rather than retrying.
-
Mobile internet “whitelists”: nothing gets through
During mobile internet shutdowns, when only approved Russian sites and apps work, Tor can't connect with any bridge. The Tor Project says so itself. It isn't your settings: use home internet, or wait until the restriction ends.
Other common reasons Tor won't connect
If a bridge doesn't solve it, one of these is usually the cause:
-
Wrong system clock
Tor needs your computer's date, time, and time zone to be correct. If they're off, the connection fails. In the Tor log this shows up as “skewed time.” Set your clock to update automatically.
-
Antivirus or firewall blocking Tor
Some security software silently blocks Tor. Kaspersky is a known example. Add Tor Browser to your antivirus's exceptions. On Windows, that means
firefox.exe,tor.exe, andlyrebird.exeinside the Tor Browser folder; on macOS,TorBrowser,tor.real, andlyrebird. -
No internet at all, or a proxy in the way
Open a normal browser first. If nothing loads there either, the problem is your internet connection, not Tor. If you see “Proxy server is refusing connection,” check your antivirus, make sure you haven't moved the Tor Browser folder, and if needed reinstall into a fresh folder. Only set a proxy under Settings → Connection → Advanced if your network requires one.
-
Tor is already running, or your computer just woke up
A second copy of Tor Browser, or waking from sleep or hibernation, can confuse the connection. Close every Tor window, or restart your computer, and try again.
-
An outdated or damaged install
Update Tor Browser. If it still fails, delete it and install a fresh copy into a new, empty folder from the official download page, rather than installing over the old one.
-
A leftover bridge you don't need
If you turned a bridge on earlier and your network doesn't actually block Tor, it can make things slow or flaky. Turn it off. (Tor connects but crawls? See why Tor is slow and how to speed it up.)
When not to use a bridge
Bridges are only needed when Tor is blocked on your network. If Tor connects fine without one, don't turn bridges on, because a direct connection is faster. Leaving a bridge on unnecessarily can make Tor feel slow or unreliable, and some people mistake that for Tor being “broken.”
Still not connecting? What to try next
-
Switch bridge type, not just bridges
If obfs4 fails, another obfs4 bridge usually fails too. Move to Snowflake or WebTunnel, which disguise Tor in a completely different way.
-
Get fresh bridges from official sources
Censors block bridges constantly. Get new ones from the Telegram bot @GetBridgesBot (
/obfs4or/webtunnel) or bridges.torproject.org, then paste them in Settings → Connection → Add new bridges… Both are blocked in Russia: here's what to use there. -
Try another network
Some mobile carriers block bridge types that work on home Wi-Fi, or the other way round. If you can, test on a different connection.
-
Ask the Tor Project for help
The official support team can send private bridges that aren't handed out publicly. Message @TorProjectSupportBot on Telegram (English, Russian, and Farsi), write on Signal or WhatsApp, or email frontdesk@torproject.org. The team replies Monday to Thursday. See all official support channels. Ignore anyone else offering “working bridges” or “fixed” Tor downloads.
-
Reinstall, but only from the official site
Never download a “fixed” Tor Browser from a random site, ad, or chat. Those can be tampered with. Use torproject.org/download only.
Is it legal to get around a block?
That depends on where you live. Some countries block Tor without making it illegal to use. See Tor laws by country, and if you're just getting started, our installation guide.
The bottom line
A stuck “Connecting…” almost always means your network blocks Tor. Click “Try a Bridge” first, then try the built-in obfs4 or Snowflake. In heavy censorship, a WebTunnel bridge (from @GetBridgesBot or Tor support) is often what gets you through. If that doesn't help, check your clock and antivirus, and only ever reinstall from the official site.
Frequently asked questions
Why is my Tor Browser stuck on connecting?
Almost always because your network is blocking the Tor network. That's common with some internet providers, schools, and workplaces, and in censored countries. A wrong system clock or an antivirus or firewall can also cause it. The most reliable fix is a bridge: click “Try a Bridge” or choose a built-in bridge under Settings → Connection.
What does “Tor Browser could not connect to Tor” mean?
It means Tor Browser reached the internet but couldn't get onto the Tor network, which usually means your network blocks Tor. Choose your location and click “Try a Bridge”, or turn on a built-in bridge such as obfs4 or Snowflake in Settings → Connection.
Which bridge should I use first?
On most networks, try obfs4 first, then Snowflake. In heavily censored countries like Russia, Iran, or China, let Connection Assist choose, or get a WebTunnel bridge from @GetBridgesBot or the Tor Project's support team. On Russian mobile data, obfs4 is usually blocked, so go straight to WebTunnel. Use meek only as a last resort, because it's usually slow.
Does Tor still work in Russia?
Yes, for most people, as long as you use a bridge. Tor Metrics estimates that around 90,000 people in Russia connect through bridges every day. On mobile data obfs4 is usually blocked, so use WebTunnel. During mobile internet “whitelist” shutdowns, Tor can't connect at all. Telegram is blocked too, so get bridges by email or from the Tor Project's support team (see In Russia? above).
Does a VPN help Tor connect?
Sometimes. If your network blocks Tor, connecting to a reputable VPN first can let Tor reach the network. But bridges are designed for exactly this problem, they're free, and they don't ask you to trust a VPN company, so try a bridge first. (Weighing it up? See do you need a VPN with Tor?)
Is it safe to use bridges?
Yes. Bridges are an official Tor feature built into the Tor Browser. They only change how you reach the Tor network; your traffic is still protected by Tor's normal layered encryption. Only get bridges from official sources, and only use them if your network blocks Tor.
Sources
We base this guide on official Tor Project documentation and independent sources. Links checked October 11, 2026.
- Troubleshooting Tor Browser — Tor Project Support
- Antivirus blocking Tor Browser — Tor Project Support
- “Proxy server is refusing connection” error — Tor Project Support
- Reading Tor log errors — Tor Project Support
- Unblocking Tor (bridge types) — Tor Project Support
- Tor user support channels — Tor Project Support
- Connecting to Tor from censored regions (Russia) — Tor Project Support
- Russia blocked Telegram (2026) — OONI Explorer
- Tor Project User Support report, December 2025 — Tor Project Forum
- Bridge users from Russia — Tor Metrics
- Anti-censorship team meeting notes, Oct 8, 2026 (Snowflake filtering in Russia) — Tor Project Forum