Response Codes

Learn about different response codes for Residential Proxies. Understand issues under the codes and resolve common status errors.

Errors originating from our infrastructure will include additional information in the X-Error-Description response header. This header provides details about the error and guidance on what to do next.

If you receive an error from the targeted website, this header will not be included in the response. In such cases, please review your scraping setup and see if it helps resolving the issue.

If you encounter a response code not listed here, please reach out to Customer Success or your Account Manager for further assistance.

Response Code	Error Message	Description
400	Bad Request	Could not parse the request. Please check if the request is formatted correctly.
400	Bad Request	SOCKS version unsupported. Please use SOCKS5 to make requests.
400	Bad Request	Unsupported parameters were used. Please contact support or your account manager if you have any questions.
400	Bad Request	Invalid HTTP request received. Please try again.
403	Access Denied	Restricted target. Please contact support or your account manager if you have any questions.
407	Access Denied	Access denied: user authentication failed. Please check your credentials and try again.
407	Access Denied	Access denied: traffic limit reached. Please contact support or your account manager if you have any questions.
500	Internal Server Error	Internal server error: we have encountered an internal error. Please try again.
502	Bad Response	Invalid HTTP response received during the request. Please try again.
502	Bad Response	Invalid response received during the request. Please try again.
502	Bad Gateway	Session failed. Please start a new session.
502	Bad Gateway	Exit node not found (session ended). Try using different filters (or start a new session).
502	Bad Gateway	We have encountered an error. Please try again.
502	Bad Gateway	Client disconnected. Please try again.
504	Timeout	Request timed out. Please try again.
504	Timeout	Unable to reach the target. Please check if the target URL is correct and try again.
522	Bad Response	Invalid response received during the request. Please try again.