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 that the proxy server could not fulfill a valid request.
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 at the moment. The Err-Code and Err-Msg fields provide the exact reason.
503 General Service Error
| Err-Code | Err-Msg |
|---|---|
| 503.0 | Unspecified error |
503 No Such User
| Err-Code | Err-Msg |
|---|---|
| 503.1.1 | Invalid user or password |
| 503.1.2 | Unable to get user |
503 No Traffic Left
| Err-Code | Err-Msg |
|---|---|
| 503.2.1 | No traffic left |
503 Target Host Denied
| Err-Code | Err-Msg |
|---|---|
| 503.3.1 | Target host denied |
503 Target Port Denied
| Err-Code | Err-Msg |
|---|---|
| 503.4.1 | Target port denied |
503 Node Is Offline
| Err-Code | Err-Msg |
|---|---|
| 503.5.1 | Node is offline |
| 503.5.2 | Node connection latency |
503 Connection Is Closed
| Err-Code | Err-Msg |
|---|---|
| 503.6.1 | Connection is closed |
503 Incorrect Host Name
| Err-Code | Err-Msg |
|---|---|
| 503.7.1 | Incorrect host name |
503 Node Has Rejected the Request
| Err-Code | Err-Msg |
|---|---|
| 503.8.1 | Node has rejected the request |
| 503.8.2 | Node has rejected the request as target host resolve failed |
| 503.8.3 | Node has rejected the request as target connect failed |
| 503.8.4 | Node has rejected the request as connect to server failed |
| 503.8.5 | Node has rejected the request as target host is denied |
503 No Exit Node
| Err-Code | Err-Msg |
|---|---|
| 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 |
| 503.9.9a | Node not assigned to port as 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 |
| 503.9.16a | Unable to get node from master due to node bad ID |
| 503.9.16b | Unable to get node from master due to node not connected |
| 503.9.17 | Session exists but node is down, not re-allocating, rotation mode 2 |
| 503.9.18 | No exit node for preflight |
503 Bad Target Connection IP
| Err-Code | Err-Msg |
|---|---|
| 503.10.1 | Bad slv local connection IP version |
| 503.10.2 | Bad slv remote connection IP version |
| 503.10.3 | Bad target IP version |
503 No Exit Node at Pool
| Err-Code | Err-Msg |
|---|---|
| 503.11.1 | Pt service failure |
| 503.11.2 | Pt bad input |
| 503.11.3 | Pt net failed |
| 503.11.4 | Pt no exit node by filter |
| 503.11.5 | Pt timeout |
504 Gateway Timeout
A 504 status indicates that the proxy node did not respond in time.
504 Node Connect Timed Out
| Err-Code | Err-Msg |
|---|---|
| 504.1.1 | Node connect timed out |
Troubleshooting Tips & Best Practices
- Validate Credentials: Verify proxy username and password for 407 and 503.1.x errors.
- Monitor Usage: Track bandwidth usage to avoid “No traffic left” errors.
- Review Filters: Loosen or adjust filtering criteria when facing 503.9.x or 503.11.x errors.
- Rotate Exit Nodes: Switch nodes if the current node is offline, rejected, or unresponsive.
- Check Target Restrictions: Review target host, target port, and target IP version for 503.3.x, 503.4.x, 503.8.x, or 503.10.x errors.
- Adjust Timeouts: Tune client-side request timeouts to avoid premature connection failures.