> For the complete documentation index, see [llms.txt](https://docs.iproyal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.iproyal.com/proxies/residential/proxy/making-requests/response-codes.md).

# Response Codes

When a request fails, Residential Proxies return an HTTP response code to indicate what went wrong. Use these codes to diagnose issues and adjust your configuration accordingly.

**500 - Internal Error**

An internal process failed - such as an inability to verify or resolve a request component. Retry the request. If the issue persists, contact IPRoyal Support.

**503 - No Exits Available**

No proxy exit nodes match the filters you specified. Review your session parameters (such as country, city) and verify that the requested location or filter combination is currently available.

**504 - Exit Connection Failed**

An exit node was selected but could not establish a connection. This is typically a transient network issue. Retry the request or adjust your target parameters.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.iproyal.com/proxies/residential/proxy/making-requests/response-codes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.