Troubleshooting 4 min read

How to Fix ERR_PROXY_CONNECTION_FAILED in Chrome (2026)

Chrome can't even reach the proxy. Usually it's a leftover system setting or a wrong port. Here's how to find it in a few minutes.

ERR_PROXY_CONNECTION_FAILED means Chrome was told to use a proxy server and couldn't open a connection to it. No request reached any website; the failure happened on the very first hop. That narrows the cause to a short list: the proxy address or port is wrong, the proxy is unreachable from your network, or a proxy setting you forgot about is still active. Chrome shows the message as "There is something wrong with the proxy server, or the address is incorrect."

ERR_PROXY_CONNECTION_FAILED vs. Similar Errors

  • ERR_PROXY_CONNECTION_FAILED: Chrome couldn't connect to the proxy at all.
  • ERR_TUNNEL_CONNECTION_FAILED: Chrome connected to the proxy, but the proxy refused or failed to open the tunnel to the site. See ERR_TUNNEL_CONNECTION_FAILED.
  • A browser login prompt for the proxy: the connection worked and the proxy wants credentials (a 407 behind the scenes). See how to fix proxy error 407.

Step 1: Find Out Which Proxy Chrome Is Using

Chrome normally follows your operating system's proxy settings, but extensions, policies and command-line flags can override them. Open chrome://net-internals/#proxy in the address bar. It shows the effective proxy configuration Chrome is actually using right now. Common surprises:

  • A proxy left behind by a VPN, ad blocker or debugging tool you uninstalled.
  • A PAC script URL (auto-config) pointing to a server that no longer exists.
  • A proxy-switching extension with an old profile selected. See browser extension proxy switching.
  • A policy from your employer or school that forces a proxy.

Step 2: Test the Proxy Port Outside Chrome

Before changing anything, confirm whether the proxy is reachable from your machine at all:

# macOS / Linux
nc -vz global.nodeproxies.xyz 8080

# Windows PowerShell
Test-NetConnection global.nodeproxies.xyz -Port 8080

# Full request through the proxy
curl -x http://USERNAME:[email protected]:8080 https://api.ipify.org

If nc or Test-NetConnection fails, something between you and the proxy blocks the port: a firewall, a restrictive office or school network, or a typo in the hostname. If they succeed and curl prints an IP, the proxy is fine and the problem is Chrome's configuration.

Step 3: Fix the Setting Where It Lives

Windows

Open Settings, then Network & Internet, then Proxy. Check "Use a proxy server" and "Use setup script". If you don't intend to use a system proxy, turn both off. If you do, set the address to global.nodeproxies.xyz and port 8080. Windows doesn't store proxy passwords here; Chrome will prompt for them on first use. Separately, some tools set the WinHTTP proxy, which you can inspect with netsh winhttp show proxy and clear with netsh winhttp reset proxy from an elevated prompt.

macOS

Open System Settings, then Network, select your active connection, click Details, then Proxies. Turn off any entry you don't recognize, including Automatic Proxy Configuration. To use NodeProxies, enable Web Proxy (HTTP) and Secure Web Proxy (HTTPS) with server global.nodeproxies.xyz and port 8080. Our macOS proxy settings guide has screenshots-level detail.

Linux

On GNOME, check Settings, then Network, then Network Proxy. Also check environment variables, since Chrome launched from a terminal can pick them up: run env | grep -i proxy and unset any stale http_proxy or https_proxy values.

Chrome launched with a flag

If a shortcut or script starts Chrome with --proxy-server=..., that overrides system settings. Edit the shortcut or script. Note that Chrome's flag doesn't accept credentials in the URL; you'll be prompted for them, or you can use an extension that handles proxy auth.

Common Mistakes That Cause This Error

  1. Wrong port. HTTP proxies on NodeProxies use 8080; SOCKS5 uses 1080. Entering 1080 in an HTTP field, or 8080 as a SOCKS host, breaks the connection.
  2. Credentials typed into the address field, like USERNAME:[email protected]. Operating system proxy fields take only host and port.
  3. Leading http:// in a host field that expects a bare hostname.
  4. A network that blocks outbound connections on non-standard ports. Try from another network, such as a phone hotspot, to confirm.
  5. Using SOCKS5 with a username and password in Chrome. Chrome doesn't support SOCKS5 authentication, so use the HTTP endpoint in the browser.

Quick Reset if You Don't Need a Proxy

If you just want Chrome working again: turn off system proxy settings, disable proxy extensions, remove any --proxy-server flag, then reload chrome://net-internals/#proxy and click "Re-apply settings". The effective configuration should read "direct://".

Setting Up Chrome with NodeProxies

Generate credentials in the dashboard, then follow how to set up a proxy in Chrome using global.nodeproxies.xyz:8080. Add -country-us or another code to the username for country targeting. Once it's working, check the exit IP with what is my IP. If you don't have an account yet, register here.

FAQ

What causes ERR_PROXY_CONNECTION_FAILED?

Chrome is configured to use a proxy it can't reach: a wrong host or port, a blocked network path, or a stale setting from a VPN, extension or PAC script.

How do I turn off the proxy in Chrome?

Chrome uses system settings, so turn off the proxy in Windows or macOS network settings, disable any proxy extension, and remove --proxy-server from your shortcut.

Is ERR_PROXY_CONNECTION_FAILED a problem with my credentials?

No. Credentials are only checked after a connection is made. Wrong credentials lead to a login prompt or a 407, not this error.

Why does the error appear only on one network?

That network probably blocks outbound traffic on the proxy port or forces its own proxy. Test the port with nc or Test-NetConnection on both networks.

NodeProxies

Ready to get started?

90M+ residential, mobile & datacenter proxies. Datacenter from $0.30/GB, residential from $0.42/GB. No contracts.

Create free account