Troubleshooting
Troubleshooting
The problems people actually run into, what causes them and how to fix them. Start by running one request with curl, which separates a setup problem from a proxy problem in a minute.
Updated 16 October 2026
First step, always#
Run the proxy through curl with -v, or through the proxy checker. If it works there and not in your program, the proxy is fine and the program's settings are not.
curl -v -x http://USER:PASS@HOST:PORT https://api.ipify.orgIt does not connect#
| Symptom | Likely cause | Fix |
|---|---|---|
| An antidetect browser says the proxy check failed | SOCKS5 type with an HTTP port | On ISP and datacenter use the port plus one for SOCKS5, or set the type to HTTP |
407 Proxy Authentication Required | Wrong username or password, or a whitelist that does not include your current address | Copy the credentials again from the order. If you rotated them, update every config |
| The exit IP is your own | The program is not using the proxy | Check that the proxy is set where this program reads it. Some ignore the system proxy |
| Works in curl, not in the browser | Browsers send no password to SOCKS5 | Use the HTTP port, the Chrome extension or the IP whitelist |
| Hangs for about two minutes, then drops | A closed port such as SSH, RDP or mail, or a firewall on your side | Use the service on an open port, or check your own firewall |
402 Payment Required on residential | The gigabyte balance has run out | Buy more traffic. Existing lines start working again |
403 on every site through a residential line | A line generated with an outdated login format | Generate the lines again |
The site blocks or challenges you#
| Symptom | Likely cause | Fix |
|---|---|---|
403 or a captcha on a bank, payment or exchange site | Those categories are blocked on purpose | No proxy type gets around it |
403, 429 or captchas from an ordinary site | Too many requests, or a pattern the site recognises | Slow down and add jitter, switch from rotating to sticky sessions on sites that track a journey |
| Blocks on a strict platform with datacenter IPs | The site scores hosting networks low | Move to ISP, residential or mobile |
| Blocks right after login on ISP or datacenter | The browser and the connection disagree about the OS | Set an OS fingerprint that matches the browser and keep the User-Agent consistent |
The location looks wrong#
- DNS goes around the proxy. With SOCKS5 use
socks5h://or the client's remote DNS option. See DNS through SOCKS5. - The browser gives itself away. Timezone, language and WebRTC must match the exit country. Antidetect browsers set them from the proxy when that option is on.
- Geolocation databases disagree. Each service keeps its own database, and they update at different speeds. Compare a few, and trust the one your target uses.
- Residential without a country. A line without
-country-exits anywhere in the pool.
Residential#
| Symptom | Likely cause | Fix |
|---|---|---|
| The IP changed in the middle of a login | A rotating line, or the device went offline | Use a sticky line with a longer rotation time, or ISP for long sessions |
| Five generated lines give the same IP | They are sticky lines with the same session, or the lines are rotating and you compared one request each | Rotating lines are identical by design. For distinct IPs at once generate sticky lines |
| Gigabytes disappear faster than expected | Background traffic of the browser | See why the balance goes fast |
| A city keeps failing | Few devices free there right now | Widen the target to the country |
ISP and datacenter#
| Symptom | Likely cause | Fix |
|---|---|---|
| OS spoofing seems to do nothing | An address in the whitelist, or connections opened before the switch | Clear the whitelist and open new connections |
| The whitelist stopped letting you in | Your public address changed | Add the new address, or go back to the password |
| All proxies of an order stopped at once | The order expired | Renew it within 2 days to keep the same IPs. See after expiry |
Mobile#
| Symptom | Likely cause | Fix |
|---|---|---|
| Device shows Offline | It dropped off the carrier's network | It usually returns within minutes. If not, write to support and the device is swapped |
| Traffic stops in the evening | The daily allowance is used up | It resets the next day. Avoid speed tests |
| Change IP is greyed out | The 5 minute cooldown between changes | Wait for the countdown |
| Connections dropped all at once | The IP changed, by hand or on the timer | Reconnect. Turn the timer off if it gets in the way |
Telegram#
See Telegram does not connect. The short version: update Telegram, then try other servers and both ports.
Didn't find the answer?
Support answers in the chat on this site around the clock. On Telegram the reply usually comes fastest, and a ticket gets an answer by email.
