net::ERR_PROXY_CONNECTION_FAILED

Chrome couldn't reach the proxy at all. The login, the tunnel and the website never come into it.

5 min read
Chrome connects to the proxy, then opens a tunnel to the site. ERR_PROXY_CONNECTION_FAILED is a failure of the first step: the proxy's address could not be resolved or its port could not be reached.Where the request stopsChromeProxyWebsitename or portnever reachednet::ERR_PROXY_CONNECTION_FAILEDa 407 or a refused tunnel shows up as a different errorChrome · Puppeteer · Playwright · Selenium

In short

The proxy host didn’t resolve or its port didn’t answer. Test the exact same host and port with curl -x from the same machine. If curl can’t connect either, fix the address, the port or the network; if you didn’t mean to use a proxy, find what still sets one.

curl -x host:portchrome://net-internals/#proxy

Through a proxy, Chrome works in two steps. First it opens a TCP connection to the proxy. Then, for an https:// page, it sends CONNECT and the proxy opens a tunnel to the site, checking the login on the way.

Chromium’s own error list defines ERR_PROXY_CONNECTION_FAILED as a failure of the first step: resolving the proxy’s name or connecting a socket to it. Failures during CONNECT are explicitly not included. So a wrong password never produces this error, and neither does a website that blocks you.

In Chrome the page says There is something wrong with the proxy server, or the address is incorrect. Puppeteer and Playwright throw it from page.goto(), Selenium as unknown error: net::ERR_PROXY_CONNECTION_FAILED.

A typo in host or port

--proxy-server=via.proxies.vison:9000 doesn’t resolve, and a port the proxy doesn’t listen on refuses the connection. Copy host and port again, and keep the login out of --proxy-server: Chrome ignores user:pass@ there anyway.

A local proxy that isn’t running

Setups that wrap an authenticated proxy in a local one (proxy-chain in Node, selenium-wire, mitmproxy) point Chrome at 127.0.0.1:<port>. If that helper crashed, was closed too early or listens on another port, Chrome finds nothing there. Start the helper before the browser and close it after.

A firewall between you and the proxy

Office networks, some cloud providers and some VPNs only allow outgoing traffic on ports 80 and 443. A proxy on 9000 or 10000 then can’t be reached from there, while the same code works at home. nc -vz host port shows quickly whether the port is open from that machine.

A proxy you didn’t mean to use

In normal browsing the cause is usually a leftover: a system proxy from an old VPN or tool, a PAC script, or a proxy extension. Open chrome://net-internals/#proxy to see what Chrome is actually using, then remove it where it was set.

ErrorWhere it failsRead
ERR_PROXY_CONNECTION_FAILEDReaching the proxy (name, port, network)this page
ERR_TUNNEL_CONNECTION_FAILEDThe proxy refused the tunnel, often the loginPuppeteer tunnel error
ERR_NO_SUPPORTED_PROXIESChrome can’t use the proxy as given (login in SOCKS5)ERR_NO_SUPPORTED_PROXIES
407 Proxy Authentication RequiredReached the proxy, login missing or wrongSelenium proxy login

Check it step by step

Run these on the machine where the browser runs. Replace USER and PASS with your proxy login.

terminal
# 1. Does the name resolve?
nslookup via.proxies.vision

# 2. Is the port reachable from here?
nc -vz via.proxies.vision 9000

# 3. Does a request go through the proxy?
curl -x http://via.proxies.vision:9000 -U "USER-country-us:PASS" https://ipinfo.io/json

If step 2 fails, the problem is the network or the address, not your code. If step 3 works, give the browser exactly the same host and port, and pass the login the way your tool wants it: Selenium, Playwright, nodriver.

puppeteer.mjs
import puppeteer from "puppeteer";

const browser = await puppeteer.launch({
  args: ["--proxy-server=http://via.proxies.vision:9000"], // host and port only, no login here
});
const page = await browser.newPage();
await page.authenticate({ username: "USER-country-us", password: "PASS" });
await page.goto("https://ipinfo.io/json");
console.log(await page.evaluate(() => document.body.innerText));
await browser.close();
What does ERR_PROXY_CONNECTION_FAILED mean?
Chrome could not open a connection to the proxy server: either the proxy's host name didn't resolve, or nothing answered on its port. It happens before any login or tunnel, so it is never caused by a wrong password.
How do I fix ERR_PROXY_CONNECTION_FAILED in Chrome without a proxy?
Something still sets a proxy. Check the system proxy settings (Windows: Settings, Network, Proxy; macOS: Network, Details, Proxies), proxy or VPN extensions, and chrome://net-internals/#proxy for what Chrome is using. Turn the leftover off.
Why does Puppeteer give ERR_PROXY_CONNECTION_FAILED?
The ‑‑proxy-server address is wrong or unreachable: a typo in the host, the wrong port, a local proxy (proxy-chain, mitmproxy, selenium-wire) that isn't running, or a firewall that blocks outgoing connections to that port. Check the same host and port with curl from the same machine.
Is ERR_PROXY_CONNECTION_FAILED the same as ERR_TUNNEL_CONNECTION_FAILED?
No. ERR_TUNNEL_CONNECTION_FAILED means Chrome reached the proxy but the proxy refused the tunnel, often because of a missing or wrong login. ERR_PROXY_CONNECTION_FAILED means Chrome never reached the proxy.

Residential proxies, pay per GB

HTTP and SOCKS5. Country, city and sticky sessions in the username. No subscription.