What is the difference between a 407 and a 402 from a proxy?

407 Proxy Authentication Required means the username or password was rejected. 402 Payment Required, which Roam returns explicitly, means the credentials were valid but the account has no balance left. Providers that return 407 for both make an empty wallet look identical to a typo.

Can special characters in a proxy password break the connection?

Yes, whenever the password travels inside a URL. A # truncates everything after it and @ or : split the URL into the wrong fields. In antidetect browsers you paste the password into its own field so this is safe, but the same password in a curl URL will fail. Use curl's -U flag instead of embedding credentials.

Antidetect browser proxy not working? Read the error code first

Q: Why does GoLogin say the proxy is not working when the credentials are correct?

Most often the connection type is wrong or the username modifiers are malformed. GoLogin's Your proxy mode sends the Login field verbatim, so a stray space or a capitalised country code makes the gateway reject the whole credential. Set connection type to HTTP, keep modifiers lowercase, and retest.

Q: What does AdsPower proxy connection test failed actually mean?

AdsPower tests the proxy by fetching an IP-detection URL of its own choosing. Residential exits are frequently rate-limited by those endpoints, so the test can fail while the proxy itself works. Change the IP checking platform in AdsPower settings and retest before assuming the proxy is broken.

Published: 26 July 2026 · Covers GoLogin, AdsPower, Multilogin, Kameleo, BitBrowser and Hubstudio

TL;DR: "Proxy failed" in an antidetect browser is three different problems wearing the same label. 407 means your credentials were rejected — almost always a malformed username modifier, not a wrong password. 402 means the credentials were fine and the balance is empty. A timeout with no code usually means the browser's own test URL is blocked from residential IPs, and your proxy is working. Find the code before you change anything.

407 → credentials402 → balanceTimeout → the test URL

Every antidetect browser reports proxy problems with a red dot and a sentence like "connection failed". None of them show you the HTTP status the proxy actually returned, which is the one piece of information that tells you what is wrong. This guide maps each symptom to its real cause, and shows how to get the status code out of the browser in under a minute.

Get the actual error code first

Before touching any setting, ask the proxy directly from a terminal. This takes ten seconds and eliminates half the possibilities:

curl -x http://gw.roamproxy.com:41080 -U 'username-country-us:password' \
     -o /dev/null -s -w '%{http_code}\n' https://api.ipify.org

Note the -U flag. Do not write the credentials into the URL as http://user:pass@host — if the password contains #, everything after it is discarded as a URL fragment and you will chase a phantom authentication failure. We lost an afternoon to exactly that.

What you get back	What it means	Go to
`200`	The proxy works. The browser is the problem.	Per-browser fixes
`200`, but sites still hang	Connection is fine, traffic is not	Connected but nothing loads
`407`	Credentials rejected	Authentication
`402`	Valid credentials, empty balance	Balance
Hangs, then times out	Network path or wrong port	Network

Roam is deliberate about returning 402 Payment Required when the wallet is empty rather than folding it into 407. Many providers return 407 for both, which makes "I ran out of credit" indistinguishable from "I typed the password wrong" — you end up re-entering correct credentials over and over.

407: it is usually the username, not the password

Residential gateways encode routing options into the username: country, sticky session, sometimes protocol. Roam uses username-country-us-session-abc123. The gateway parses that string strictly, so a formatting slip rejects the whole credential and looks exactly like a wrong password.

Uppercase country codes. -country-US fails where -country-us works. Copying a country code out of a table is the usual source.
A trailing space. Pasting from a dashboard often brings one along. It is invisible in the field and fatal to the parse.
A country with no inventory. A valid-looking code for a country the pool cannot serve is rejected at auth time, not at connect time.
Modifiers in the password field. The modifiers belong on the username. In the password field they are simply a wrong password.

Test the bare username with no modifiers at all. If that returns 200, the credentials are sound and the fault is in the modifier string.

402: the credentials are fine

A metered proxy stops passing traffic the moment the balance cannot cover the next chunk. Everything worked yesterday, nothing changed in the config, and today every profile fails at once — that pattern is a balance, not a bug. Top up and the same credentials resume working with no reconfiguration. Trial accounts hit this the moment the free allowance is spent, which for a browser profile loading real pages can be a single afternoon.

Timeouts: port and protocol

Roam accepts both HTTP and SOCKS5 on the same port, 41080, detecting which one you are speaking from the first byte. That is unusually forgiving — most gateways give each protocol its own port, and picking the wrong one produces a hang rather than a clean error, because the proxy is waiting for a handshake you are never going to send.

If a connection hangs rather than failing fast:

Confirm the port. A proxy on the wrong port does not refuse you politely; it waits.
Turn off any VPN or system-wide proxy. Two proxies in series fail in ways that look like one broken proxy.
Check corporate or ISP egress filtering on high ports. If curl from your phone's hotspot works and your desk does not, that is your answer.

When curl returns 200 but the browser still fails

This is the most common case, and in most of these the proxy was never broken.

GoLogin proxy not working

Set Connection type to HTTP explicitly rather than leaving it on Auto. Auto-detection guesses from the port, and a port that serves both protocols — like ours — can be guessed wrong. The Login field is passed through verbatim, so a space picked up while pasting travels with the credential and gets it rejected — retype the last few characters rather than trusting the paste. If the profile shows Connected but pages do not load, the fingerprint's timezone and the exit country probably disagree, and the site is blocking on that mismatch, not on the IP.

AdsPower proxy connection test failed

AdsPower validates a proxy by fetching an IP-detection service, and which service it uses is configurable under the IP checking platform setting. Those free endpoints aggressively rate-limit residential ranges — a shared residential IP may already be over their limit through no fault of yours. Switch the IP checking platform to a different provider and retest. If curl gave you 200 and AdsPower says the test failed, believe curl.

Multilogin proxy check failed

Multilogin runs its own reachability check before letting a profile start and applies a short timeout. Residential exits are slower to first byte than datacenter ones — a couple of seconds is normal — and a distant exit can exceed that window while being perfectly usable. Try a nearer country first to confirm the credentials, then move to the country you actually need.

Kameleo, BitBrowser, Hubstudio

All three follow the same pattern: a built-in check against a third-party URL, with the underlying error hidden. The diagnosis order does not change — curl first, then the browser's test URL, then the config.

The one that is genuinely your proxy

If curl returns 200 but the exit IP is a hosting provider rather than a consumer ISP, nothing is broken and everything is wrong: you are on a datacenter IP being sold as residential. Check the exit with an IP and ASN lookup — the ASN should belong to a consumer ISP, not to a cloud host. An antidetect browser cannot rescue a transparent or datacenter exit; the fingerprint will be immaculate and the IP will still give you away. Our open-source proxyprobe grades a whole list for this in one pass.

FAQ

Why does GoLogin say the proxy is not working when the credentials are correct?

Usually the connection type or the username modifiers. Set connection type to HTTP rather than Auto, keep country codes lowercase, and check for a trailing space in the Login field — GoLogin passes it through verbatim and the gateway rejects the whole string.

What does "AdsPower proxy connection test failed" actually mean?

That AdsPower could not reach its chosen IP-detection URL through the proxy. Those endpoints rate-limit residential ranges heavily, so the test fails while the proxy works. Change the IP checking platform in settings and retest.

What is the difference between 407 and 402?

407 means the credentials were rejected. 402 means they were accepted and the balance is empty. Roam returns them separately on purpose; providers that collapse both into 407 make an empty wallet look like a typo.

Can special characters in the password break things?

Only when the password travels inside a URL — # truncates it and @ or : split it into the wrong fields. Antidetect browsers give the password its own field, so they are safe. In curl, use -U user:pass instead of embedding credentials in the URL.

Should I use HTTP or SOCKS5?

For antidetect browsers, HTTP. It is what every one of them expects by default, and Roam serves both on port 41080 anyway. Reach for SOCKS5 only when a tool specifically requires it.

Setting one up from scratch instead of debugging one? Start here: GoLogin · AdsPower · Multilogin · Kameleo · choosing proxies for antidetect browsers. Roam is $2/GB metered with a 300MB free trial, no card required — enough to prove a profile connects before you pay for anything.