# Response Codes

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.

{% hint style="warning" %}
 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.
{% endhint %}

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

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


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://developers.oxylabs.io/proxies/mobile-proxies/response-codes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.