Proxy authentication failed: how to fix it
In short: Proxy authentication failed means the proxy was reached but refused your sign-in. What you see depends on the client, so start from the symptom table. Chrome never sends SOCKS5 credentials, and changing the protocol in the dashboard changes the details to use, so copy them again afterwards.
The proxy accepted your connection and then refused to sign you in. The shared checks (fresh credentials, URL encoding, the allowlist) are on the page for error 407. The table here starts from what your client shows, because the same refusal reads differently in each tool.
Find your client
| What you see | Likely cause | What to do |
|---|---|---|
| A browser dialog that returns after each submit | The proxy rejects what you type, or the browser never sends it | Recopy the details; see the post on the Chrome password prompt |
| curl prints 407 | Wrong login, password or a set allowlist | Pass them with the proxy-user option, not inside the address |
| A script library raises a proxy error that mentions 407 | The library read the proxy URL differently | Encode special characters, or pass the credentials in separate fields |
| ProxyJam Connector shows AUTH on its badge | The stored credentials were rejected twice | Edit the profile and enter them again; guides are on docs.proxyjam.com |
| A SOCKS5 proxy with a password fails in Chrome | Chrome sends no SOCKS5 credentials | Use an allowlist, an HTTP endpoint or Firefox |
Chrome and SOCKS5
Chrome implements no SOCKS5 authentication, so no setting makes it send a SOCKS5 username and password. Firefox and ProxyJam Connector in Firefox can. If you must stay in Chrome, use the proxy over HTTP, or put the address you connect from on the allowlist for the order.
After you change the protocol
Change protocol in your dashboard switches an order between HTTP and SOCKS5. The port and credentials to use are the ones the row shows after the change, so copy them again and update every client, script and saved profile that still holds the old ones. The static IP stays the same while the order is active (Terms of Service, section 2.5).
If it still fails
Email support@proxyjam.com with the order number, the exact message and the name of the client, and we will troubleshoot it with you. A proxy that does not accept a connection with the credentials we issued is a defect once we confirm it (Refund Policy, section 1), and that report goes to billing@proxyjam.com within 24 hours of payment (section 4). The two sign-in methods are compared in proxy authentication methods, and the proxies are on the ISP proxies page. Read the Refund Policy for the full terms of a refund.
