If your Residential Proxy works normally but stops connecting after you add location, ASN, OS, or other targeting criteria, the proxy itself may still be working correctly. In many cases, there simply isn't a matching Residential exit available at that moment.
This guide will help you narrow down what's causing the connection failure. For instructions on configuring targeting parameters, see our Residential Proxy Targeting documentation.
➡️ Why Targeted Connections May Fail
Why does my proxy work without targeting but fail when I add targeting?
Residential Proxies use real devices connected to the Rayobyte network. These devices can come online and offline throughout the day, so the number of IPs matching a particular set of targeting criteria can change over time.
The more specific your request becomes, the smaller the matching pool will generally be. Country-level targeting usually provides broader availability, while criteria such as a specific city, ZIP/postal code, ASN, or multiple combined filters can significantly narrow the available pool.
If no matching exit is currently available, your request may fail rather than automatically return an IP that doesn't match your requested criteria.
➡️ Troubleshooting Your Targeting
How can I tell whether targeting is causing the problem?
Start with the simplest possible connection and gradually add the targeting criteria your workflow requires.
- Test your Residential Proxy without any targeting criteria.
- If the connection works, add your required country and test again.
- Add one additional targeting criterion at a time.
- Test after each change to identify which criterion causes the connection to stop working.
- If the request fails, remove the most specific criterion and try again.
- Retry after a short delay, since Residential availability can change as devices come online and offline.
This makes it much easier to determine whether you're dealing with a general connection problem or simply limited availability for a particular targeting combination.
For the available targeting options and configuration instructions, see our Residential Proxy Targeting documentation.
What should I try if a specific city, ZIP, or ASN isn't connecting?
Try broadening your targeting temporarily.
- If a ZIP/postal code isn't available, try the city, region/state, or country instead.
- If a city isn't available, try the broader region/state or country.
- If an ASN isn't available, test with fewer additional targeting criteria to see whether an exit from that network is currently online.
- If you're combining several criteria, remove them one at a time until the connection succeeds.
Once you've confirmed that a broader target works, you can gradually narrow your request again.
➡️ Common Connection Symptoms
What does my connection error mean?
The exact cause can vary, but these are some common symptoms when troubleshooting targeted Residential Proxy connections:
| Symptom | Possible Cause | What to Try |
|---|---|---|
| Authentication error | Credentials or connection configuration may be incorrect | Test the proxy without targeting and verify your authentication settings. |
| Connection timeout | A matching Residential exit may not currently be available | Retry after a short delay or broaden your targeting. |
| HTTP proxy error 552 | Your requested targeting criteria may not currently have a matching exit | Remove the narrowest targeting criterion and test again. |
| SOCKS5 connection failure | The connection was rejected or a usable matching exit wasn't available | Test SOCKS5 without targeting first, then add targeting criteria one at a time. |
| Correct country but unexpected city or region | Different IP geolocation databases may report different locations | Check the exit IP using another reputable geolocation provider. |
For the latest Residential Proxy error information, see our Rayobyte Proxy Docs.
➡️ Location Doesn't Match?
Why does an IP lookup site show a different location?
IP geolocation information comes from third-party databases, and different providers can report different city, region, or other location information for the same IP.
If your proxy connects and the country is correct but a more specific location looks different than expected, check the exit IP using more than one reputable geolocation provider before assuming the targeting failed.
If multiple providers consistently show a location that doesn't match your requested target, contact our Support team with an example so we can take a closer look.
➡️ Need Help?
If you've confirmed that your proxy works without targeting but a normally available target repeatedly fails, our Support team is happy to help investigate.
When contacting us, please include:
- The targeting criteria you're trying to use
- Whether the proxy works without targeting
- Which targeting criterion causes the connection to fail, if you've isolated it
- The protocol you're using (HTTP/HTTPS or SOCKS5)
- The exact error message or error code you're receiving
- A recent example and approximate time of the failed request
Important: Please mask your proxy password and any other sensitive credentials before sending screenshots, logs, or connection examples.
Email: support@rayobyte.com
Submit a Ticket: Contact Rayobyte Support