net::ERR_PROXY_CONNECTION_FAILED
Chrome couldn't reach the proxy at all. The login, the tunnel and the website never come into it.
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.
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.
| Error | Where it fails | Read |
|---|---|---|
| ERR_PROXY_CONNECTION_FAILED | Reaching the proxy (name, port, network) | this page |
| ERR_TUNNEL_CONNECTION_FAILED | The proxy refused the tunnel, often the login | Puppeteer tunnel error |
| ERR_NO_SUPPORTED_PROXIES | Chrome can’t use the proxy as given (login in SOCKS5) | ERR_NO_SUPPORTED_PROXIES |
| 407 Proxy Authentication Required | Reached the proxy, login missing or wrong | Selenium proxy login |
Check it step by step
Run these on the machine where the browser runs. Replace USER and PASS with your proxy login.
# 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/jsonIf 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.
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?
How do I fix ERR_PROXY_CONNECTION_FAILED in Chrome without a proxy?
Why does Puppeteer give ERR_PROXY_CONNECTION_FAILED?
Is ERR_PROXY_CONNECTION_FAILED the same as ERR_TUNNEL_CONNECTION_FAILED?
Keep reading
net::ERR_NO_SUPPORTED_PROXIES: Chrome Proxy With Login and SOCKS5
Why Chrome, Puppeteer and Playwright fail with ERR_NO_SUPPORTED_PROXIES or refuse SOCKS5 with a login, and two setups that work. Tested on Chrome 156.
5 min read · #puppeteer#playwright
git: Proxy CONNECT aborted and 407 From Proxy (Fix)
git clone through a proxy fails with Proxy CONNECT aborted or 407 after CONNECT. Why it happens, the one git config line that fixes it, and SSH remotes.
4 min read · #errors#authentication
Proxy Password With Special Characters (@ : # %)
A proxy password with @, :, # or % breaks the proxy URL. What curl, requests, httpx, Node and Go say, which encoding fixes it, and three traps we found.
6 min read · #authentication#errors
Residential proxies, pay per GB
HTTP and SOCKS5. Country, city and sticky sessions in the username. No subscription.