Troubleshooting

When a website blocks or flags your IP

Websites keep an eye on where their visitors come from. When a visit looks unusual to them, they might put up a CAPTCHA, ask you to verify a login, slow your requests down or refuse the page altogether. A ProxyGuys proxy gives you several ways to respond, from a new IP in the same city to a different city altogether. Work down this page in order: the first steps take the least effort.

Why sites push back

Each site has its own rules and rarely tells you which one you tripped. The usual triggers are:

  • a lot of requests from one address in a short time;
  • traffic that looks automated, like identical requests at a fixed rhythm;
  • an address, cookie or browser profile the site already connects with trouble;
  • a visitor arriving from outside the region the site expects.

A new IP helps when the site has flagged the address. It won't help when the site has flagged your account, or recognises your browser from its cookies, which is why the steps below cover sessions as well as IPs.

1. Confirm the site sees the proxy

In the same browser profile or script that hit the block, open https://api.ipify.org?format=json or https://httpbin.org/ip. If it shows your own connection's address, traffic isn't going through the proxy at all, and the fix is in your tool's proxy settings rather than the IP.

Don't be thrown if a lookup site puts you in a different city or state from the one you chose. Those sites use their own databases, and a mobile IP can show up somewhere else. That's normal on mobile networks.

2. Get a new IP

Press Change IP on the proxy in My Proxies, or pick Rotate IP now from its ⋮ menu. The proxy gets a new IP in the same city on the same carrier, usually within 30 to 90 seconds. You can do this once every 60 seconds.

When a script spots the block, it can fix it on its own with the change-IP link from ⋮ → Copy change-IP link. Opening the link changes the IP without a login, so keep it as private as a password. The rotation guide covers the links in detail.

3. Start a clean session

A fresh IP can still be linked to the old one if you arrive with the same cookies. Before you try the site again:

  • clear that site's cookies, or open a new browser profile;
  • in an anti-detect browser, start a new profile instead of reusing the flagged one;
  • in a script, create a new session or client object so old cookies aren't sent.

4. Move to another city

If each new IP in the same place gets challenged, change location. Click the proxy's location (it reads City, ST) or choose Change location from the ⋮ menu. Use the "Search city or state…" box, narrow it with the carrier chips (All, Verizon, AT&T, T-Mobile), and press Connect on a row that has free phones. For a quick jump somewhere new, press Random city. Leave about 3 minutes between location changes.

Locations cover cities across the US, and which carriers a given city offers depends on what's available at the time. If a site expects visitors from a certain region, pick a city there, then check again with an IP lookup.

5. Change your pace

Heavy, repeated requests are better spread across IPs. Turn on automatic rotation in the Rotation column (every 5, 10 or 30 minutes, or hourly) and lower your request rate. For logged-in accounts, the opposite tends to work better: keep one steady IP per account, because an account that keeps jumping between addresses can look suspicious too.

Still blocked?

If a site turns away every IP and city you try, the block is most likely tied to your account, your browser setup or how the requests are made, not to the address. If the problem is the proxy itself, for example it won't load any site, open a ticket from Tickets in the dashboard.