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

Proxy authentication failed: how to fix it

Topic: Errors and fixes All answers

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 seeLikely causeWhat to do
A browser dialog that returns after each submitThe proxy rejects what you type, or the browser never sends itRecopy the details; see the post on the Chrome password prompt
curl prints 407Wrong login, password or a set allowlistPass them with the proxy-user option, not inside the address
A script library raises a proxy error that mentions 407The library read the proxy URL differentlyEncode special characters, or pass the credentials in separate fields
ProxyJam Connector shows AUTH on its badgeThe stored credentials were rejected twiceEdit the profile and enter them again; guides are on docs.proxyjam.com
A SOCKS5 proxy with a password fails in ChromeChrome sends no SOCKS5 credentialsUse 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.

Quick answers about failed sign-ins

Is this the same as error 407?

Mostly yes. The proxy answers 407, and tools word it as authentication failed or required. The shared checks are on the 407 page. Proxy error 407: Proxy Authentication Required

Why did the password stop working after I set an allowlist?

Setting an allowlist for an order switches the password off for all of its clients, and an empty list turns password sign-in back on. Proxy authentication

Why does Chrome keep asking for the password?

Chrome takes no credentials from its proxy settings, so it shows a dialog on each 407. The post on the dialog explains the loop and what to do. Proxy password prompt

Related pages