> 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/proxy-works-in-tester-but-not-in-app-or-site.md).

# Proxy Works in Tester but Not in App or Site

Troubleshoot a proxy that passes a proxy tester but fails in your application, browser, bot, or target website.

A proxy tester confirms that the tester can connect through the proxy. It does not guarantee that every website or application will accept or correctly use that proxy.

## First identify where the failure happens

{% stepper %}
{% step %}

### Test the proxy independently

Use [Test Your Proxies](https://docs.shieldproxies.com/using-your-proxies/test-your-proxies.md).

If the proxy fails in the tester as well, continue with [Proxies Not Working](https://docs.shieldproxies.com/troubleshooting/proxies-not-working.md).
{% endstep %}

{% step %}

### Test a neutral destination

Try the same proxy against a simple IP-check or neutral HTTPS endpoint using another client where possible.

If neutral destinations work but the target website fails, the proxy is connecting and the issue is likely target-specific.
{% endstep %}

{% step %}

### Compare your application settings

Check that your application uses the same:

* proxy hostname or IP
* port
* protocol, such as HTTP/HTTPS or SOCKS5
* username and password, or IP whitelist authentication
* session ID or sticky-session configuration
* target URL
  {% endstep %}

{% step %}

### Check application-specific behavior

If the proxy works in another client but not your application, review:

* timeout values
* DNS handling
* redirects
* retry behavior
* concurrency
* connection reuse
* cookies
* request headers
* browser or TLS fingerprinting
  {% endstep %}
  {% endstepper %}

## When the target returns 403 or 429

If a tester and neutral endpoint work but the target returns **403**, the target is refusing the request. If it returns **429**, the target is rate-limiting the traffic.

Changing proxy configuration can sometimes help, but these responses do not automatically indicate that the proxy itself is offline.

{% hint style="warning" %}
Shield Proxies can help verify whether the proxy connection is functioning, but a working proxy does not guarantee that a specific third-party website, bot, or automation tool will accept the traffic.
{% endhint %}

## Related guides

* [Common Proxy Errors](https://docs.shieldproxies.com/troubleshooting/common-proxy-errors.md)
* [Proxy Authentication & 407 Errors](https://docs.shieldproxies.com/troubleshooting/proxy-authentication-and-407-errors.md)
* [Sticky & Rotating Session Troubleshooting](https://docs.shieldproxies.com/troubleshooting/sticky-and-rotating-session-troubleshooting.md)
* [Open a Support Ticket](https://docs.shieldproxies.com/support-and-community/open-support-ticket.md)
