Response Codes
These are the most common response codes you can get while using our Shared Datacenter Proxies. If you receive any other response code, get in touch with our support for more information.
400 Bad Request
A proxy server can return this error code if the request did not contain a host to connect to or if there was a generic error when parsing an HTTP request. Make sure your request is correctly formed and include the URL in the request, then try again.
407 Proxy Authentication Required
Request lacks proxy authentication information, or username or password is invalid. Include the Proxy-Authorization header in your request and make sure your username and password are correctly formed, then try again.
500 Internal Server Error
A proxy server has encountered an internal error. Retry request at a later time.
502 Bad Gateway
A proxy server received an invalid response from the upstream server. Retry request.
Response Code 502 signifies that the IP assigned to your session ID is no longer available. If you encounter this error, there are two ways to work around it. The first is to wait for one minute, and the system automatically assigns a new IP address to your session ID. Another approach is to switch to a new session ID (i.e., change the sessid parameter) – this way, you will receive a new IP address.
522 Timeout
A proxy server did not receive a response from the upstream server in time. Retry request.
525 No Exit Found
Custom HTTP status code means the proxy could not find an exit node that satisfies the request. Change the request filter parameters or try again at a later time.
Last updated