You set a proxy in Chrome, load a page, and instead of the site you get a flat gray error: ERR_PROXY_CONNECTION_FAILED. Not a slow load, not a half-broken page, nothing. Every tab fails the same way, and normal browsing worked fine a minute ago. On Firefox or Tor Browser the identical failure reads as the proxy server is refusing connections, but in Chrome you get this. The message looks vague, but it is actually one of Chrome's more specific errors, and that specificity is exactly what makes it quick to fix once you know what it points at.
The short version: Chrome tried to reach the proxy you configured and could not open a connection to it at all. That single fact tells you where to look and, just as usefully, where not to. Here are the six fixes, in the order that clears this error fastest.
What does ERR_PROXY_CONNECTION_FAILED mean?
Chrome shows ERR_PROXY_CONNECTION_FAILED (rendered in full as net::ERR_PROXY_CONNECTION_FAILED) when it cannot open a connection to the proxy server you told it to use. The break is between Chrome and the proxy, not between the proxy and the website you wanted. In plain terms, Chrome dialed the proxy and got no answer, so it stopped before it ever reached the target site.
Because the failure is on the Chrome-to-proxy leg, you can ignore anything to do with the destination website. The site is not blocking you; Chrome never got that far. That narrows the whole problem down to five things: a wrong address, a protocol mismatch, a dead proxy, a browser-side conflict, or something local blocking the connection. Here is each cause, how to spot it, and the fix.
| Cause | How to spot it | Fix |
|---|---|---|
| Wrong IP or port | Every site fails instantly | Re-check the address, verify it is alive |
| Protocol mismatch | Fails on a proxy you know is good | Match HTTP vs SOCKS |
| Dead proxy | Worked earlier, fails now | Swap in a fresh one |
| Conflicting extension | Started after installing or updating an extension | Keep one proxy extension only |
| System vs extension clash | Chrome says "controlled by an extension" | Use one layer, not both |
| Firewall, AV or VPN | Fails only on this machine or network | Disable the blocker or change port |
How to fix ERR_PROXY_CONNECTION_FAILED
1. Check the IP and port, then confirm the proxy is alive
Start with the boring cause, because it is the most common. One wrong digit in the IP or a transposed port number, and Chrome is dialing an address where nothing is listening. It fails in exactly the way a dead proxy does.
Re-read the proxy address against your source, character by character. A proxy is written as host:port, for example 203.0.113.7:8080, so make sure the port on the right matches what your provider gave you and nothing got truncated when you pasted it.
Then confirm the proxy is actually alive, outside Chrome, so you are testing the proxy and not your browser setup. Paste the IP and port into our proxy checker; it reports in one pass whether the proxy answers, where it exits, and how fast it is. If the checker calls it dead, Chrome was right to fail and no amount of browser tweaking will help. If the checker says it is alive but Chrome still fails, your problem is one of the next five. Our full walkthrough on how to check if a proxy is working covers the manual version if you prefer the command line.
2. Match the protocol: HTTP against SOCKS
Chrome has to speak the same protocol the proxy expects. Point an HTTP proxy setting at a SOCKS-only proxy, or the reverse, and the handshake never completes. Chrome reports that as ERR_PROXY_CONNECTION_FAILED because, from its side, the connection genuinely failed.
The port is your best clue. A proxy on 1080 is almost always SOCKS. Ports 8080, 3128 and 80 are usually HTTP. If your provider listed the proxy as SOCKS5, set the type to SOCKS5 in your extension or system dialog, not HTTP.
Fix it wherever you configured the proxy: in a proxy extension, change the profile's type field; in system settings, tick the correct proxy row. If you are not sure how your setup routes Chrome in the first place, our guide on how to set up a proxy in Chrome lays out each method and shows where the protocol setting lives in each one.
3. The proxy is dead, so switch to a fresh one
If the address is right and the protocol matches, the proxy itself may simply be down. This is the default explanation with free proxies, which have lifetimes measured in minutes, not days. A proxy you tested and configured correctly this morning can be gone this afternoon, and the moment it drops, every Chrome tab through it returns ERR_PROXY_CONNECTION_FAILED.
There is nothing to fix on your end here; the proxy died. Swap in a different one. Our free proxy list shows a last-checked timestamp and an uptime figure for every entry, so you can pick one that was confirmed alive minutes ago instead of gambling on a stale dump. Grab a fresh IP and port, update it in Chrome, and reload. If the error clears, the old proxy was the whole problem.
4. A broken or duplicate proxy extension is conflicting
Proxy-manager extensions are the usual way people route Chrome, and they are also a common source of this error. Two failure modes show up here. The first is having more than one proxy extension enabled at once, say FoxyProxy and SwitchyOmega both installed; they both try to control Chrome's proxy config, and whichever wins may be pointing at nothing. The second is a single extension left half-configured, with a saved profile that has an empty or wrong host.
Open chrome://extensions and look at which proxy tools are enabled. Keep exactly one proxy extension active and disable the rest. Then open the survivor's options and check that the profile you are actually using has a real host and port, not a blank field left over from setup. If the error started right after you installed or updated a proxy extension, that is almost certainly your cause.
5. System and extension proxy settings are fighting
Chrome does not have its own proxy engine on desktop; it either follows your operating system's proxy settings or hands control to an extension. When both are set, they can contradict each other. A classic case: you switched your extension to Off expecting direct browsing, but a proxy is still set at the Windows or macOS system level, pointing somewhere dead, so Chrome keeps failing.
Chrome will usually tell you who is in charge. Open Chrome's settings and look for a line saying the proxy is controlled by an extension, or open your system proxy panel and see whether a manual proxy is switched on. Pick one layer and clear the other. If you are using an extension, make sure the system proxy is off. If you are using system settings, make sure no extension is also trying to steer. Running both is how you end up chasing an error that neither layer alone would produce.
6. A firewall, antivirus, or VPN is blocking the connection
If the proxy checks out as alive from another machine but Chrome on this one still fails, something local is sitting between Chrome and the proxy. Corporate firewalls frequently block outbound connections to non-standard proxy ports. Antivirus suites with a web-shield or "secure connection" feature can intercept the same traffic. And an active VPN reroutes your entire connection, which can leave Chrome unable to reach a proxy that expects to be contacted from your normal IP.
Work through the local blockers one at a time. Turn off any VPN and reload; if the error clears, the VPN and proxy were colliding, and you need to pick one or chain them on purpose rather than by accident. Add Chrome or the proxy port to your antivirus and firewall exceptions. If you are on a locked-down network that blocks odd ports, a proxy listening on a common port like 8080 or 443 has a far better chance of getting through than one on an unusual high port.
Isolate it in under a minute
When the error hits, you do not have to guess which of the six it is. Two checks split the field:
- Paste the proxy into the checker. Dead? It was fix 3, and you just need a fresh proxy. Alive? The proxy is fine and your problem is browser-side or local, which means fixes 1, 2, 4, 5 or 6.
- Try the same proxy in a different app, or in a fresh Chrome profile with no extensions. Works there but not your main Chrome? An extension or a settings clash is the culprit (fixes 4 and 5). Fails everywhere on this machine while the checker says alive? Look local: firewall, antivirus or VPN (fix 6).
Two checks, and you have gone from a blank gray error page to a single known cause. ERR_PROXY_CONNECTION_FAILED looks blunt, but it is honest: Chrome is telling you it could not reach the proxy, and one of these six reasons is why. Fix the reason and the tab loads.
Frequently asked questions
What does ERR_PROXY_CONNECTION_FAILED mean in Chrome?
It means Chrome could not open a connection to the proxy server you configured. The failure is on the Chrome-to-proxy leg, not between the proxy and the website. In practice the proxy address is wrong, the proxy is dead, the protocol is mismatched, or a local firewall, antivirus or VPN is blocking the connection.
How do I fix ERR_PROXY_CONNECTION_FAILED?
Work through it in order: double-check the proxy IP and port, confirm the proxy is alive in a checker, match the protocol (HTTP vs SOCKS), swap in a fresh proxy if the old one died, keep only one proxy extension enabled, make sure system and extension settings are not fighting, and disable any VPN or firewall blocking the proxy port.
Why does ERR_PROXY_CONNECTION_FAILED keep coming back?
Usually because you are using free proxies, which die within minutes. A proxy that was alive when you set it up drops offline, and every Chrome tab through it fails until you replace it. The fix is to pull a fresh, recently-verified proxy each time instead of reusing an old one.
Is ERR_PROXY_CONNECTION_FAILED a problem with my proxy or with Chrome?
Either. Test the proxy outside Chrome first by pasting it into a proxy checker. If the checker says it is dead, the proxy is the problem and you need a new one. If the checker says it is alive but Chrome still fails, the issue is browser-side: a wrong protocol, a conflicting extension, or a local firewall or VPN.
What is the difference between ERR_PROXY_CONNECTION_FAILED and ERR_TUNNEL_CONNECTION_FAILED?
ERR_PROXY_CONNECTION_FAILED means Chrome could not connect to the proxy at all. ERR_TUNNEL_CONNECTION_FAILED means Chrome did reach the proxy, but the proxy could not open a tunnel to the HTTPS site you asked for. The first points at the proxy being unreachable or misconfigured; the second points at the proxy struggling to reach the target.