Skip to content

Proxy errors

ERR_PROXY_CONNECTION_FAILED

Chrome could not open a connection to the proxy you configured. Check the address and port first, then whether the browser is using the profile you think it is.

A Chrome-family error shown when the browser cannot reach the configured proxy at all. It is a browser-side message, so the cause is usually in the proxy settings rather than on the network.

Error
ERR_PROXY_CONNECTION_FAILED
Comes from
Varies, see below

Where this error comes from

ERR_PROXY_CONNECTION_FAILED is generated by Chrome, Edge, Brave and other Chromium browsers. It is not an HTTP status code and never comes from a server. The browser is reporting that it tried to reach the proxy and could not.

Because it is browser-side, the information it carries is limited. The browser does not distinguish between a wrong port, a firewall and a proxy that is down. All of those produce the same message, which is why the error feels uninformative.

The fastest way to make progress is to take the browser out of the picture and test the same proxy with curl. If curl works and the browser does not, the fault is in the browser configuration, and you have halved the search space.

curl -sS -o /dev/null -w '%{http_code}\n' \
  --proxy proxy.example.com:8000 --proxy-user 'USER:PASS' \
  https://example.com

Settings that are usually wrong

When curl succeeds and the browser fails, it is nearly always one of a short list of configuration mistakes.

  1. The scheme is wrong. An HTTP proxy configured as SOCKS5, or the reverse, fails immediately. Check which the order specifies.
  2. The port is wrong. Providers often run different proxy types on different ports, and copying the port from an older order is easy to do.
  3. The system proxy is set instead of the browser proxy, or the other way round. Chrome on Windows and macOS uses the system settings by default, so a browser extension and the system can disagree.
  4. An extension is overriding the setting. Proxy extensions take precedence over system configuration, and a disabled extension can still hold a stale profile.
  5. The address is being sent through a PAC file that no longer resolves, which fails before any proxy is contacted.

Why the browser cannot prompt for credentials

Chromium browsers will show a username and password dialog for a proxy that answers with 407. If the proxy never answers, there is nothing to prompt for, and you get this error instead.

That distinction is useful. Being asked for credentials means the browser reached the proxy, which is progress. Seeing ERR_PROXY_CONNECTION_FAILED means it did not get that far.

If you are automating a browser, note that most automation frameworks cannot fill the native proxy dialog, which is why they take credentials as launch arguments or through an extension instead.

Checking what the browser is really using

Chrome exposes its live proxy resolution state on an internal page, which is more reliable than reading the settings UI. It shows the effective configuration, including anything an extension has imposed.

Open chrome://net-internals/#proxy to see the current proxy settings as the network stack sees them. If what is listed there does not match what you configured, an extension or policy is overriding you.

Fixing it on each platform

Where the proxy is configured differs by operating system, and the browser does not always use the setting you edited.

  1. Windows: Chrome follows the system proxy under Settings, Network and Internet, Proxy. Changing Chrome's own settings opens that same panel, so an extension is the only way to give Chrome a proxy of its own.
  2. macOS: the system proxy lives in System Settings, Network, then Details and Proxies for the active interface. Each network service holds its own configuration, so a setting applied to Wi-Fi does nothing on Ethernet.
  3. Linux: behaviour varies by desktop. Chromium reads the GNOME setting on some distributions and the http_proxy environment variable on others, and launching with --proxy-server removes the ambiguity entirely.
  4. Any platform: launching with --proxy-server="http://host:port" bypasses system and extension configuration completely, which makes it the quickest way to prove whether the proxy itself is reachable.

Automation and headless browsers

Automation frameworks hit this error for a reason that does not apply to normal browsing: they usually cannot answer the credential dialog. Puppeteer and Playwright both accept a proxy server as a launch argument, but the username and password have to be supplied separately, through the framework's own authenticate call or a bundled extension.

A common symptom is that the proxy works perfectly in a normal browser window and fails in the automated one. That is almost always missing credentials rather than a bad address. Check that the authentication step runs before the first navigation, because a page load started earlier will fail on its own.

Frequently asked questions

Is this error from the website?

No. It is generated by the browser itself and means it could not reach the proxy. No server was involved.

Why does curl work when Chrome does not?

Almost always a browser configuration difference: the wrong scheme or port, a conflicting extension, or system settings overriding the browser.

Why am I not asked for a username and password?

The browser only prompts when the proxy answers with 407. This error means it never got a reply.

How do I see what proxy Chrome is actually using?

Open chrome://net-internals/#proxy, which shows the effective configuration including anything an extension has set.

Ready to try it?

Create an account, add funds from US$1 and pick your country and proxy type.