Proxy errors and what they mean

Every refusal from the proxy comes with a status code, and most with a one-line reason in the body. Read the body first; it usually names the fix.

Code	Meaning	Fix
407	Key wrong or missing, or the account is disabled	Re-copy the key; check the URL carries credentials
402	Balance is empty	Top up — requests resume immediately
403	Your IP is not on your allowlist, or the target is a private address	Add your IP on the Proxies page
429	Too many connections at once, or repeated failed logins	Slow down, reuse connections
502	Port not supported, no IP for your targeting, or a passing failure	Read the body; an empty 502 usually clears on retry

These codes come from the proxy itself. A block page or CAPTCHA from the website you are visiting is a different problem — see "Blocked by the website" below.

407 — the most common one

Almost always a typo or a shell problem:

• Copy the key from the portal again; do not retype it.
• Check the proxy URL actually carries credentials: http://KEY:TIER@host:port. A client that drops them gets a 407 on every request.
• zsh users: $KEY:standard is silently mangled, because zsh reads :s as a modifier. Write ${KEY}:standard.

403 — the allowlist

If you turned on IP restriction on the Proxies page, only the addresses listed there can connect. With the restriction on and no addresses listed, every connection is refused. Add the IP your requests actually come from — on a server, that is the server's IP, not your home connection.

Billed at the wrong rate?

A password that does not start with a recognised tier is not refused: the request runs at your account's default tier. If usage shows up under a tier you did not expect, check the spelling of the tier in the password.

502 — which one is it?

• "Port … is not supported" — the proxy connects only to common ports (80, 443, 8080, 8443, 22, 465, 587, 993, 995, 5060).
• "No connection is available for the requested location" — your targeting is too narrow right now. See targeting.
• Empty body — a temporary failure. Retry.

Blocked by the website

If the proxy connects but the website shows a block page or a CAPTCHA, the site is reacting to the traffic, not to your account. Try cleanproxy or mobile, slow down, reuse a sticky session instead of switching IP on every request, and send the headers a real browser would.

Still stuck? Open a ticket with the exact command, the status code and the response body.