Proxy errors
403 Forbidden when using a proxy
The target site received your request and refused it. The proxy worked. Something about the request, or the reputation of the exit IP, made the site say no.
A 403 comes from the website, not the proxy. The request arrived and the site decided to refuse it, usually because of what the request looked like rather than where it came from.
- Error
- 403 Forbidden
- Comes from
- The target website
403 is the site talking, not the proxy
This is the single most important distinction, and the one that sends people down the wrong path. A 403 is returned by the web server you are trying to reach. Your request travelled through the proxy successfully, reached the destination, and was rejected there.
Compare it with 407, which comes from the proxy itself and means your credentials failed. If you are seeing 403, authentication worked and the connection is sound. Changing your proxy password will not help.
This also means a 403 is billable traffic. The request went out and a response came back, so it counts against bandwidth in a way that a rejected 407 does not.
Why sites return 403 to proxied traffic
Sites refuse requests for several different reasons, and they all surface as the same status code. Working out which one you are hitting is most of the job.
- The exit IP is recognised as a datacenter address. Many sites treat datacenter ranges as non-human by default. This is the most common cause and the hardest to argue with.
- The IP has a poor history. Shared addresses carry the behaviour of everyone who used them before you.
- The request looks automated. A missing or default User-Agent, no Accept-Language, no Referer, or a header order that does not match any real browser.
- You are geo-blocked. The site serves that country a 403 regardless of anything else about the request.
- A bot-protection service is in front of the site. Cloudflare, Akamai and similar products return 403 when a challenge is not completed.
- You are logged out of something that needs a session, so the resource genuinely is forbidden to you.
Find out which one it is
Run the same request three ways: without a proxy, through the proxy with default headers, and through the proxy with realistic browser headers. The combination that works tells you the cause without guessing.
# 1. no proxy, baseline
curl -sS -o /dev/null -w '%{http_code}\n' https://example.com/page
# 2. through the proxy, default headers
curl -sS -o /dev/null -w '%{http_code}\n' \
--proxy proxy.example.com:8000 --proxy-user 'USER:PASS' \
https://example.com/page
# 3. through the proxy, browser-like headers
curl -sS -o /dev/null -w '%{http_code}\n' \
--proxy proxy.example.com:8000 --proxy-user 'USER:PASS' \
-H 'User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/140.0 Safari/537.36' \
-H 'Accept-Language: en-US,en;q=0.9' \
-H 'Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8' \
https://example.com/pageWhat each outcome means
If 1 and 3 succeed but 2 fails, your headers were the problem and you can fix this in your own code today. This is the best outcome and more common than people expect.
If 1 succeeds and both 2 and 3 fail, the exit IP is the problem. A datacenter address is being filtered. Moving to an ISP or residential proxy is the real fix, because no amount of header tuning changes what network the address belongs to.
If all three fail, the problem is not the proxy at all. The URL, your account state, or the site itself is refusing everyone. Check the page in a normal browser before going further.
If 1 fails and 2 succeeds, you are the one being geo-blocked, and the proxy is doing exactly its job.
Choosing a fix that lasts
Header tuning is cheap and worth doing properly, but it only addresses requests that look automated. If the site is filtering by network, the durable answer is an address type the site does not treat with suspicion: ISP addresses sit on ranges registered to consumer internet providers, and residential addresses are real household connections.
Be realistic about the ceiling. A site running serious bot protection is not going to be solved by a different IP alone, and a 403 that persists across address types is the site telling you clearly that it does not want automated access. At that point the question is whether the data is available another way, such as an official API.
Frequently asked questions
Does a 403 mean my proxy is broken?
No. A 403 comes from the target website and proves the proxy delivered your request.
Will switching country fix a 403?
Only if the cause is geo-blocking. If the site is filtering datacenter ranges, a different country of the same type behaves the same.
Do 403 responses cost bandwidth?
Yes. The request and the response both travel, unlike a 407 which is rejected at the proxy.
Is a residential proxy guaranteed to avoid 403?
No. It removes the datacenter signal, which is often the cause, but a site with strong bot protection can still refuse the request.
Ready to try it?
Create an account, add funds from US$1 and pick your country and proxy type.