HTTP status codes
| Code | Meaning | Cause | Fix |
|---|---|---|---|
| 403 | Invalid request configuration | Bad geo flag, malformed parameter | Re-check username syntax; see Residential setup |
| 407 | Proxy Authentication Required | Wrong credentials or password reset | Expand 407 accordion below |
| 411 | Account blocked | TOS violation, billing problem, anti-abuse trigger | Contact support |
| 464 | Connection not permitted | Target on our restricted list | Contact support if legitimate |
| 465 | No proxies available | No IPs match your targeting | Add -strict-off or broaden targeting |
| 466 | Bandwidth limit reached | Out of GB | Top up |
| 467 | Session bandwidth limit | Per-session -limit- cap hit | Release / new session |
| 500 | Internal server error | Server-side issue | Retry with backoff |
| 502 / 504 | Gateway error | Upstream timeout | Retry; check status page |
| 517–569 | Various internal errors | Server-side | Retry with backoff |
Connection-level errors
| Error | Cause | Fix |
|---|---|---|
| Proxy connection timed out | Network path or target unreachable | Test with api.ipify.org to isolate |
| TUNNEL_CONNECTION_FAILED | HTTPS CONNECT blocked, wrong port, or restricted target | Check protocol/port; see if target is restricted |
| SOCKS rejected | Used SOCKS5 on HTTP port | Use correct port |
malformed HTTP response "\x01\x01..." | Used HTTP on SOCKS port | Use correct port |
| net::ERR_TUNNEL_CONNECTION_FAILED (Chrome) | Wrong port/protocol | Re-generate proxy |
Recv failure: Connection reset | Proxy refused (wrong protocol or restricted destination) | Check protocol; check restricted list |
proxy-error JSON responses
These come back as JSON instead of HTTP status codes:| Response | Cause | Fix |
|---|---|---|
{"proxy-error":"country-XX-asn-YY target was not found"} | Strict matching, no available IPs for that combination | Add -strict-off or broaden targeting |
{"proxy-error":"ASN should be used with country."} | -asn- flag without -country- flag | Add -country-XX |
{"proxy-error":"..."} (other) | Targeting / configuration issue | Check username syntax |
407: Proxy Authentication Required
407: Proxy Authentication Required
The most common error. Causes in order of likelihood:
- Proxy password was reset — Update credentials everywhere. See Authentication: resetting.
- Wrong username format — Typo in
country-,session-, orlifetime-segments. Re-copy from the generator. - Hit a rate or bandwidth cap — Check the dashboard.
464: Connection not permitted
464: Connection not permitted
Destination is on our restricted list. Switch targets or contact support.
465: No proxies available
465: No proxies available
No IPs match your geo-targeting. Broaden targeting (drop city or ASN), add
-strict-off to allow fallback, or try later when pool composition changes.466: Bandwidth limit reached
466: Bandwidth limit reached
Top up in the dashboard. See Billing.
SOCKS / HTTP mismatch errors
malformed HTTP response or SOCKS rejected = wrong protocol on wrong port. Each EclipseProxy product has separate HTTP and SOCKS5 ports:
| Product | HTTP rotating | HTTP sticky | SOCKS5 rotating | SOCKS5 sticky |
|---|---|---|---|---|
| Residential | 9000 | 10000 | 11000 | 12000 |
| Mobile | 5555 | 5555 | 6666 | 6666 |
61234, SOCKS5 62234, and UDP 65535 (the only product with UDP). See ISP setup.
Re-generate the proxy with the correct protocol selected.
When contacting support
Include:- Exact error (full text or HTTP status code)
- Proxy string (mask the password)
- Target URL (if shareable)
- What you’ve already tried from this page
See also
- Common issues: diagnostic flow for proxy down, slow, wrong country, fraud score, etc.