Shared Proxy HTTP Error Codes Reference
HTTP error codes for shared Residential, Mobile & Datacenter Proxies.
4xx Client Error Codes
Errors in the 4xx range indicate issues with the client’s request to the proxy.
| Status Code | Description |
|---|---|
| 400 | Bad Request |
| 407 | Proxy Authentication Required |
Example Responses
HTTP/1.1 400 Bad Request
Connection: close
Content-Length: 0
HTTP/1.1 407 Proxy Authentication Required
Proxy-Authenticate: Basic realm="proxy"
Connection: close
Content-Length: 0
5xx Server Error Codes
Errors in the 5xx range indicate the proxy server failed to fulfill a valid request. A sample 503 response:
HTTP/1.1 503 No exit node
Content-Length: 0
Err-Code: 503.9.6
Err-Msg: Unable to get node for required filters
503 Service Unavailable
A 503 status means the proxy cannot handle the request right now. The Err-Code and Err-Msg fields pinpoint the exact failure.
| Err-Code | Err-Msg |
|---|---|
| 503.0 | Unspecified error |
| 503.1.1 | Invalid user or password |
| 503.1.2 | Unable to get user |
| 503.2.1 | No traffic left |
| 503.3.1 | Target host denied |
| 503.4.1 | Target port denied |
| 503.5.1 | Node is offline |
| 503.6.1 | Connection is closed |
| 503.7.1 | Incorrect host name |
| 503.8.1 | Node has rejected the request |
| 503.9.1 | No exit node |
| 503.9.2 | Node is not connected |
| 503.9.3 | User session is empty |
| 503.9.4 | Empty session result |
| 503.9.5 | Unable to get node or node not connected |
| 503.9.6 | Unable to get node for required filters |
| 503.9.6a | Unable to get node for required filters after session TTL expired |
| 503.9.6b | Unable to get node for required filters after node bindTTL expired |
| 503.9.7 | Unable to get node for required filters as not selected or not connected |
| 503.9.8 | Empty next node for required filters |
| 503.9.8a | Empty next node for required filters after session TTL expired |
| 503.9.8b | Empty next node for required filters after node bindTTL expired |
| 503.9.9 | Node not assigned to port as not selected or not connected |
| 503.9.10 | Bad port index type 1 |
| 503.9.11 | Bad port index type 2 |
| 503.9.12 | Unable to assign node to port type 1 |
| 503.9.13 | Unable to assign node to port type 2 |
| 503.9.14 | Unable to assign node to port type 3 |
| 503.9.15 | Unable to assign node to port as not match |
| 503.9.16 | Unable to get node from master |
504 Gateway Timeout
The 504 status indicates that the proxy node did not respond in time.
| Err-Code | Err-Msg |
|---|---|
| 504.1.1 | Node connect timed out |
Troubleshooting Tips & Best Practices
- Validate Credentials: Always verify proxy username/password for 407 and 503.1.x errors.
- Monitor Usage: Track your bandwidth to avoid “No traffic left” errors.
- Review Filters: Loosen or adjust filtering criteria when facing 503.9.x errors.
- Rotate Exit Nodes: If encountering offline or unresponsive nodes, switch nodes.
- Adjust Timeouts: Tune client and proxy timeouts to prevent premature timeouts.