Error codes reference
Every error you might see from EclipseProxy proxies: HTTP status codes, SOCKS5 replies and connection-level errors
When something fails, the error code tells you what to fix.
HTTP status codes
These are the codes the Residential gateway returns. Other products return the standard HTTP proxy codes; 407 is by far the most common everywhere.
| Code | Meaning | Cause | Fix |
|---|---|---|---|
| 402 | Payment Required | Out of bandwidth | Top up |
| 403 | Forbidden | Target on our restricted list | Contact support if legitimate |
| 407 | Proxy Authentication Required | Wrong credentials or password reset | Expand 407 accordion below |
| 502 | Bad Gateway | The upstream connection failed or timed out | Retry; check the status page |
| 503 | Service Unavailable | Nothing can serve that username: unknown -pool- code, -asn- without -country-, an ISP with a non-Vega network pinned, or a pinned network that lacks a feature you asked for | Fix the username; drop the -pool- pin. See Residential setup |
SOCKS5 replies
| Reply | Same as | Fix |
|---|---|---|
| Authentication failed | HTTP 407 | Re-copy credentials from the generator |
| Connection not allowed by ruleset (0x02) | HTTP 403 | Restricted target |
| Network unreachable (0x03) | HTTP 503 | Fix the username; see above |
| Host unreachable (0x04) | HTTP 502 | Retry |
| Connection refused (0x05) | HTTP 402 | Top up |
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 |
402: Payment Required
Out of bandwidth. Top up in the dashboard. See Billing.
403: Forbidden
Destination is on our restricted list. Switch targets or contact support.
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. - Wrong account — Each product has its own credentials; Residential credentials don't work on Mobile ports and vice versa.
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 |
Residential also serves 3030 (HTTP) and 2020 (SOCKS5), where the username decides sticky vs rotating; that is what the generator emits.
ISP is static — there's no rotating/sticky split, so it doesn't fit the columns above. It uses HTTP/HTTPS 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
Cuts ticket resolution time in half.
See also
- Common issues: diagnostic flow for proxy down, slow, wrong country, fraud score, etc.