Connection failures, slow proxies and account issues: a troubleshooting guide

Before changing IPs, check your local network, protocol, credentials, location, session and destination restrictions in order.

1. Connection failure: check configuration

• Are host, port, username and password complete?
• Does the tool's protocol match the proxy?
• Were extra spaces or newlines copied into the settings?
• Do your firewall, business network or server security rules block the port?

2. Authentication failure: check credential parameters

Proxy providers may include country, city and session parameters in credentials. Client escaping can cause authentication errors. For 407, authentication failed or invalid credentials, recopy the complete generated configuration first.

3. Location mismatch: check how it is measured

IP databases may show adjacent cities or an ISP's location. Cross-check several sources and your actual destination to see whether the location meets your needs.

4. Slow speed: isolate proxy and destination latency

• Test another session in the same country for a peer-specific problem.
• Test another country for regional route congestion.
• Test the destination directly to check its own response time.
• Use timeouts and bounded retries rather than waiting indefinitely.

5. Account issues: look beyond the IP

Account checks may consider IP, browser profile, login region, request frequency, cookies, time zone, language and history. Repeated IP changes can make matters worse. Keep a consistent environment and appropriate activity rate.

6. Recommended troubleshooting order

1. Test newly generated settings from the dashboard.
2. Verify protocol, credentials and port.
3. Open an IP-check page to verify the exit.
4. Open the destination homepage to check for destination-side blocking.
5. Retest with another session in the same country.
6. If problems persist, contact support with the error, configuration format, target country and test time.