Troubleshooting
Common Proxy Configuration Problems and How to Troubleshoot Them
Diagnose authentication failures, connectivity issues, and configuration mistakes with a calm, step-by-step troubleshooting approach.
Most proxy issues come from configuration: wrong credentials, mismatched host/port, client settings, or secrets that never reached the runtime environment.
This is a learning guide, not a checkout page. To buy, open the matching product page or Pricing.
Work through the checklist below before opening a wide-ranging ticket—then use FAQ, Knowledge Base, or Contact if you still need help.
Authentication and credentials
- Confirm username and password match the dashboard values
- Check for trailing spaces or outdated secrets in CI variables
- Verify whether your plan uses password auth, allowlisting, or both
- Rotate credentials if they may have been exposed
Connectivity and client setup
- Confirm protocol and port expected by your HTTP client or tool
- Test from a clean environment to isolate local network filters
- Review tool-specific proxy settings (system vs application vs extension)
- Check whether regional targeting is set to a location you actually need
When to escalate
If authentication and client settings look correct and failures persist, gather timestamps, product type, and sanitized logs, then contact support. Avoid pasting live credentials into tickets.
Fast isolation steps
Confirm protocol (HTTP vs SOCKS5), credentials, and country before changing code. Test with a single sticky session from a known-good client, then reintroduce concurrency.
Common failures include wrong protocol, expired plan, allowlist mismatches, and clients that ignore system proxy settings. Fix those before buying more IPs.
- 401/407 → auth or plan status
- Timeouts → endpoint host/port or local firewall
- Wrong geo → country targeting not applied in the dashboard