A site is blocking your proxy: what we need to see

When a website blocks or challenges requests through your proxy, the first question is whose side the problem is on: the proxy's, the site's or your client's. Three quick tests usually answer it, and the details below let us take it from there.

Narrow it down first

1. Fetch an IP-echo page through the proxy, for example https://api.ipify.org. If an address comes back, the proxy is working and the site is the one saying no.
2. Fetch the target without the proxy. If that fails too, the proxy is not involved.
3. Try a second, unrelated site through the proxy. If only one site fails, it is that site's filtering.

A refusal from the proxy itself looks different from a site's block; 407 or 403: find out who answered shows how to tell them apart in one command.

What to send

• The target: the site and the exact page or API address. Leave out pages that sit behind your personal login.

• What came back: the status code and what the response looked like: an error page, a CAPTCHA, an empty body, a redirect.

• When: date, time and time zone, and whether it fails every time or only sometimes.

• How you connect: the command or client settings, password removed:

  bash

  curl -v -x http://HOST:PORT -U "USERNAME:REDACTED" https://api.ipify.org
  

• The exit IP: what the IP-echo page returned through the same proxy.

• What you tried: a fresh connection or another IP, a slower rate, a normal browser.

• The proxy: its ID from the proxy page, and whether it is ISP or datacenter.

The quickest route is Report an issue on the proxy's page with Blocked by the target site selected; it attaches the proxy for you. Email support@proxyhive.io works too.

What to leave out

Passwords, API keys, card numbers, and screenshots that show any of them. None of it helps with a block.