> For the complete documentation index, see [llms.txt](https://docs.shieldproxies.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shieldproxies.com/troubleshooting/common-proxy-errors.md).

# Common Proxy Errors

Understand common proxy HTTP and network errors and what each usually means.

A proxy error does not always mean the proxy itself is offline. The response can come from the proxy gateway, the target website, your authentication settings, or your application.

## HTTP error guide

| Error                                 | What it usually means                                      | What to check                                                                          |
| ------------------------------------- | ---------------------------------------------------------- | -------------------------------------------------------------------------------------- |
| **400 Bad Request**                   | The request sent by your application is malformed.         | URL, headers, request format, application settings.                                    |
| **401 Unauthorized**                  | The target website or API rejected its own authentication. | Target account, API key, login or request credentials.                                 |
| **403 Forbidden**                     | The target refused the request.                            | Target-specific blocking, IP reputation, headers, cookies, browser or TLS fingerprint. |
| **407 Proxy Authentication Required** | The proxy authentication was rejected.                     | Proxy username/password, IP whitelist, endpoint, port, protocol and account status.    |
| **429 Too Many Requests**             | The target is rate-limiting the traffic.                   | Request rate, concurrency, IP reuse, session behavior and retry settings.              |
| **5xx**                               | A server-side error occurred.                              | Whether the response came from the target, CDN, proxy gateway or upstream provider.    |

{% hint style="info" %}
A **403** or **429** from one target does not by itself mean the proxy is dead. Test the same proxy against a neutral endpoint or proxy tester before concluding that the connection is broken.
{% endhint %}

## Timeout, connection refused or reset

Network-level failures include:

* connection timed out
* connection refused
* connection reset
* TLS handshake failure
* DNS failure
* empty response

Test the same proxy against more than one unrelated destination. If it fails everywhere, the issue is more likely to be proxy, upstream, authentication, or network related. If it works elsewhere but fails on one target, the issue is more likely target-specific.

## A successful HTTP status can still be blocked

Some websites return **HTTP 200** while showing a CAPTCHA, challenge page, access-denied message or limited content. Check the returned page, not only the HTTP status.

## Related guides

* [Proxies Not Working](https://docs.shieldproxies.com/troubleshooting/proxies-not-working.md)
* [Proxy Works in Tester but Not in App or Site](https://docs.shieldproxies.com/troubleshooting/proxy-works-in-tester-but-not-in-app-or-site.md)
* [Proxy Authentication & 407 Errors](https://docs.shieldproxies.com/troubleshooting/proxy-authentication-and-407-errors.md)
* [Open a Support Ticket](https://docs.shieldproxies.com/support-and-community/open-support-ticket.md)
