How to fix ERR_PROXY_CONNECTION_FAILED in Chrome

Why Chrome reports ERR_PROXY_CONNECTION_FAILED

• A leftover proxy setting. You configured a proxy on Windows or macOS once, the order expired or you stopped using it, but the setting is still on. Chrome on Windows and macOS reads the operating-system proxy, so every site fails.
• Wrong port or IP. One wrong digit in the port sends Chrome to a port where nothing is listening.
• A proxy extension is active. SwitchyOmega, FoxyProxy or a VPN extension can override the system proxy and be easy to forget.
• Unwanted software set a proxy. Some adware and "network booster" tools write a proxy into system settings. If you have never set a proxy yourself, consider this.

The real output

We ran Chromium with --proxy-server=http://203.0.113.10:8080 (a documentation address) pointing at a port with no proxy behind it. The net-log records ERR_PROXY_CONNECTION_FAILED, with the underlying error ERR_CONNECTION_REFUSED: the host answered that the port accepts no connections.

For the same address the proxy checker returns connect failed, and curl prints curl: (7) Failed to connect to 203.0.113.10 port 8080 after 0 ms: Couldn't connect to server. All three say the same thing: nothing is listening on the ip:port you are using.

Fixes by device

• Windows 10/11: open Settings > Network & Internet > Proxy. If you do not want a proxy, switch off the manual setup; if you do, compare IP and port with the order in your dashboard. Step-by-step removal is in the turn off proxy guide.
• macOS: System Settings > Network > select Wi-Fi or Ethernet > Details > Proxies, then switch off Web Proxy (HTTP) and Secure Web Proxy (HTTPS) if unused.
• Android: open the connected Wi-Fi network, choose edit or advanced, and set Proxy to None. If the error happens on one Wi-Fi only, the proxy is almost certainly saved for that network.
• Chrome extensions: open the extensions page, disable proxy and VPN extensions one at a time and reload to find the culprit.
• Edge: also Chromium and also follows the Windows proxy, so fixing Windows fixes Edge.

If you want to keep using the proxy

Run the line through the checker. connect failed on an active order usually means a port mix-up: some orders list separate ports for HTTP and SOCKS5, so use the port that matches the protocol you picked in the dashboard. If the checker works and Chrome still fails, the setting on your device differs from the line you tested, so copy it again. Antidetect browsers show the same fault as a failed proxy check; see GoLogin proxy setup.

Step by step

1. 1

   Decide whether you need a proxy

   If not, go straight to switching it off. If yes, keep your dashboard proxy line open for comparison.

2. 2

   Open the operating-system proxy settings

   Windows: Settings > Network & Internet > Proxy. macOS: System Settings > Network > Details > Proxies.

3. 3

   Switch it off or correct IP and port

   Disable the manual proxy, or re-enter the exact IP and port from your order and save.

4. 4

   Disable proxy or VPN extensions

   Turn off each extension that controls proxy settings, reloading the page after each one.

5. 5

   Confirm with the checker

   Paste the line into the proxy checker; once it no longer says connect failed, you are done.

Frequently asked questions