How to Fix ERR_TUNNEL_CONNECTION_FAILED in Chrome

By ErrorFix · Updated October 25, 2026 · 7 min read

What ERR_TUNNEL_CONNECTION_FAILED means

ERR_TUNNEL_CONNECTION_FAILED means Chrome tried to reach a website through a middleman — a proxy server or a VPN — and the tunnel through that middleman could not be built. Normally, when you use a proxy, Chrome asks the proxy to open a tunnel to the website, and the website's traffic flows back through that tunnel. When the proxy is down, misconfigured, overloaded, or refusing the request, the tunnel never forms, and Chrome gives up with this error instead of loading the page.

This error is different from a plain connection failure because Chrome is not saying the website is unreachable — it is saying the route to the website is broken. That is why it shows up most often in places where a proxy sits in the middle by design: office and school networks that filter web traffic, computers with a VPN running, and devices with parental-control or security software that routes browsing through its own proxy. At home, with no proxy and no VPN, you will rarely see it — and when you do, it usually means a leftover proxy setting or a VPN extension is still forcing traffic through a tunnel that no longer exists.

Common causes

• A stale or broken proxy setting: a proxy address left over from an old office, school, or VPN setup points Chrome at a server that no longer answers.
• A failing VPN connection: the VPN server is down, overloaded, or blocked, so the tunnel it builds collapses before any website can load.
• A VPN or proxy browser extension: an extension can force traffic through its own tunnel even when the desktop VPN app is switched off.
• Network filtering or parental controls: school, office, or family-safety filters route traffic through their own proxy, and if that service is down, tunneled connections fail.
• Firewall or antivirus interference: a firewall rule or web shield can block the tunneled connection, especially on networks it does not trust.

How to fix ERR_TUNNEL_CONNECTION_FAILED — step by step

Work through these fixes in order. Most cases are fixed by step 1 or 2.

1. Turn off your proxy settings. This error is almost always about a proxy, so start there. On Windows, open Settings, go to Network and internet, then Proxy, and turn off Use a proxy server under Manual proxy setup; also turn off Automatically detect settings if the problem persists. On a Mac, open System Settings, go to Network, select your Wi-Fi or Ethernet connection, click Details, then Proxies, and uncheck every protocol. If you are on a Chromebook, open Settings, go to Network, select your connection, and set Proxy to Direct Internet connection. Close Chrome completely and reopen it before testing, because a running Chrome can hold on to the old proxy configuration.
2. Disconnect your VPN and remove VPN extensions. A VPN builds its own tunnel, and when that tunnel breaks, Chrome reports exactly this error. Disconnect your VPN completely and quit the VPN app rather than just closing its window, then reload the page. Also check Chrome itself: type chrome://extensions in the address bar and disable or remove any VPN or proxy extension, since an extension can force traffic through a dead tunnel even when the desktop VPN app is off. If the page loads with everything disconnected, reconnect the VPN and try a different server location — the server you were on may be down or blocked.
3. Test in incognito and in another browser. Open an Incognito window with Ctrl + Shift + N on Windows (Cmd + Shift + N on a Mac) and load the same site. Incognito runs without extensions and with a fresh cache, so if the site works there, an extension or cached setting in your normal profile is forcing the broken tunnel. Also try the site in a different browser such as Edge or Firefox. If it works in Firefox but not Chrome, the problem lives in Chrome's profile or settings; if it fails everywhere, the problem is your system proxy, VPN, or network, not the browser.
4. Flush DNS and reset the network stack. Stale DNS records and a corrupted network stack can stop a tunnel from forming. On Windows, open Command Prompt as Administrator and run ipconfig /flushdns, then netsh winsock reset, then netsh int ip reset, and restart your computer. On a Mac, open Terminal and run sudo dscacheutil -flushcache followed by sudo killall -HUP mDNSResponder. As a deeper Chrome reset, go to Settings, then Reset settings, then Restore settings to their original defaults. This clears extension configurations and custom settings without deleting your bookmarks or saved passwords.
5. Check your firewall, antivirus, and filtering software. Security and filtering software can block the tunnel outright. On Windows, open Windows Security, then Firewall and network protection, then Allow an app through firewall, and confirm Google Chrome is checked for both Private and Public networks. Try pausing your antivirus web shield briefly as a test and re-enable it immediately afterward. Also look for parental-control or content-filtering apps on the device — school and family-safety filters route traffic through their own proxy, and if that service is down or misconfigured, every tunneled connection fails with this error.
6. Switch networks or contact your network admin. If nothing above works, change the network to isolate the cause. Turn on your phone's mobile hotspot and connect your computer to it — if sites load fine on the hotspot, your home, office, or school network is the problem, usually a proxy or filter on that network. On a work or school network, you usually cannot fix this yourself: ask the IT admin whether a proxy is required and get the correct proxy address and port. If only one website fails on every network while everything else works, that site's server or firewall is refusing the connection — contact the site owner or wait and retry later.

Did this fix it? Quick checklist

• Pages load without the tunnel error
• The site works with the proxy turned off
• The site loads with the VPN fully disconnected
• The error is gone in an incognito window

If the error is gone in incognito but still appears in a normal window, an extension is still forcing the broken tunnel — keep extensions disabled and re-enable them one at a time to find the culprit. If the error disappears on a phone hotspot but returns on your usual Wi-Fi, the problem is your network's proxy or filter, not your computer — check the router's settings for a proxy or filtering service, or ask your network admin. And if one specific site keeps failing on every network while everything else loads, that site's server is refusing the connection; there is nothing left to fix on your side, so contact the site owner or try again later.