Cloudflare Error 1006: Access Denied for Your IP

What the error means

According to the Cloudflare documentation, errors 1006, 1007 and 1008 mean access is denied because the IP has been banned. The ban is set by the site owner in their security rules, not by Cloudflare.

Cloudflare states directly that its support cannot override security settings set by the site owner. In other words, only the owner can lift the ban.

Through a proxy, the site sees not your address but the proxy's exit IP. The pool is shared: another customer may have used this IP before, and the owner's rule may have appeared before you.

Causes

• The site owner banned a specific IP. For example, after unwanted activity from this address.
• A range of addresses is banned. The rule covers the whole subnet or the ISP (ASN) network that includes the IP.
• A country is banned. The site accepts visitors only from certain countries.
• A network type is banned. Some sites close access, for example, to datacenter addresses.

How to fix it

1. Check which address and country you exit from: My IP through the same proxy.
2. Make sure the country in the proxy settings matches the one the site is intended for.
3. If you need access for work, write to the site owner. Include the Ray ID from the error text: with it, the owner can find which rule was triggered.
4. Do not try to get around the ban: the Prokso acceptable use policy forbids getting around restrictions a site has imposed.
5. If you believe the error repeats on all sites and from all addresses, check the proxy in the proxy checker and write to support with the time and the plan name.

How to check that it works

Open another site through the same proxy, for example the My IP page. If other sites open, the proxy works, and the refusal comes from a rule of the specific site.

Two-minute diagnosis

First paste the line into the proxy checker. If the proxy works there, the cause is in your app or its settings. If not, test the line from a terminal:

curl -v -x "http://USERNAME:PASSWORD@gw.prokso.com:823" https://api.ipify.org

• A < HTTP/1.1 407 line right after CONNECT means the proxy answered. The name after the code, for example NO_USER, points to the cause.
• The proxy answered CONNECT with 200 and then another code arrived - the proxy works, and that answer came from the website.
• No answer at all, only a timeout - the connection never reached the proxy: check the host, port and network.