Proxy error 407: Proxy Authentication Required
In short: Error 407, Proxy Authentication Required, means the proxy received your request but did not accept who sent it. Check the credentials first and, in allowlist mode, the address you connect from. The limit of 100 concurrent sessions per proxy is a separate fair-usage term, so check the sign-in first.
A 407 is the proxy’s way of saying “sign in first”. It reached the proxy, so the address and port are right; what failed is the authentication step that comes before any page is fetched.
What to check, in order
- Username and password. Copy them again from the order in your dashboard
and paste them without a trailing space. A password with characters such as
@,:or#must be percent-encoded when you write it inside a proxy URL. - Where the client sends them. Some tools ignore credentials typed into the proxy address and ask for them separately, so use that tool’s own username and password fields.
- IP allowlist mode. If the proxy is set to accept only listed addresses, the address you connect from must be on the list. Check your current public IP and add it, because a home or office address can change.
Where each client asks for the credentials
The same 407 looks different in each client, and the fix depends on where that client keeps the credentials it sends to the proxy:
- A browser shows a sign-in dialog. If it returns after you submit, the proxy rejected what you typed. The post on the Chrome proxy password prompt explains why Chrome asks again.
- A command-line tool or script prints the status 407 or a proxy error. Pass the login and password through the tool’s own proxy-user option, or percent-encode them inside the URL.
- An extension keeps the credentials with the proxy profile. If it stops asking after rejections, open the profile and enter them again.
Test it with one command
Take the browser out of the picture and send a single request with curl. Replace the
four values with the ones from your dashboard row, and keep the address as http:// even when the target page uses HTTPS:
curl -I -x http://HOST:PORT -U LOGIN:PASSWORD https://example.com
A 200 or a redirect means the proxy accepted the sign-in, so the fault is in the
client you used before. A 407 means the proxy still rejects these details. Compare
them with the row once more, and check whether an allowlist is set, because it switches
the password off for the order. For an HTTPS tunnel that fails with another message, see
tunnel connection failed.
Once the credentials match, the same request goes through, and a client that kept failing will connect after you re-enter them. If they still fail, proxy authentication failed goes deeper, and the ISP proxies page describes what you are connecting to.
