Change language
English Русский Deutsch Español Français Italiano Українська Tiếng Việt Türkçe Bahasa Indonesia हिन्दी 日本語 Português 中文
Menu
Pricing
Proxies
Solutions
Resources

ERR_PROXY_CONNECTION_FAILED: what it means and how to fix it

Topic: Errors and fixes All answers

In short: ERR_PROXY_CONNECTION_FAILED means your browser could not open a connection to the proxy itself, so no request ever reached a website. The usual causes are a mistyped host or port, a protocol that does not match, an expired proxy, or a network that blocks the port. Fix the proxy address first, because wrong credentials give a different error.

The browser tried to open a connection to the proxy and failed. The request never reached a website, and no username or password was checked yet, so the fault sits somewhere between your device and the proxy address that you typed in.

What to check, in order

  1. Host and port. Open My Proxies in your dashboard and copy the address again, in the form HOST:PORT. One wrong digit, a stray space or a port taken from another order is enough to fail.
  2. Protocol. Each row shows HTTP or SOCKS5. A browser set to SOCKS5 for an HTTP proxy, or the reverse, fails at once. If you changed the protocol in the dashboard, copy the port again, because the details it shows after a change are the ones to use.
  3. Expiry. The Expires column shows when the period ends, and a proxy stops working then. If the time has passed, extend the order, which keeps the address.
  4. Another proxy in the way. A system proxy, a VPN or an extension that also sets a proxy can overrule yours. Turn the others off and test again.
  5. Your network. A firewall, a company network or a security program can block the proxy port. Try another network, such as a phone hotspot, to tell the cases apart.

Test the proxy outside the browser

If the browser still fails, send one request from another tool, such as curl, using the same host, port and credentials. When that works, the fault is in the browser or an extension. Should it fail as well, the cause is the address, the network or the order itself. Our proxy checker sends the same request from our side: if the proxy answers there and not from your device, look at your network first. When the check page What Is My IP loads through the proxy and shows the static address from your row, the proxy is fine.

If the checks pass

Suppose the details match, the order is active and a second network fails the same way. Then email support@proxyjam.com with the order number and a screenshot of the error, and we will look at the order with you. If you think the IP has a defect, report it to billing@proxyjam.com within 24 hours of payment. The Refund Policy, sections 1 and 4, counts no connection with the credentials we issued as a defect once we confirm it. For the full path from the order to a working browser, read how to use a static IP proxy. The proxies are on the ISP proxies page.

Quick answers about this error

Is this error caused by wrong credentials?

No. Wrong or missing credentials produce a 407 answer from the proxy, and for that the proxy has to be reachable. This error means the browser never got that far. Proxy error 407: Proxy Authentication Required

Does an expired proxy cause it?

Possibly. The Expires column of your dashboard shows when the period ends, and a proxy stops working then. Extending the order keeps the same address. Terms of Service

Should I ask for another IP?

Not first. The address is not replaced during the period you paid for (Terms of Service, section 2.5). If the proxy does not accept a connection with the credentials we issued, section 1 of the Refund Policy treats it as a defect we confirm, and section 4 says to report it to billing@proxyjam.com. Refund Policy

Related pages