If when trying to access a website, scrape competitor prices on Wildberries, or run multiple accounts through an anti-detect browser, you encounter a white screen with the message "Access denied" and error codes 1020, 1005, or 1006 — it means Cloudflare has blocked your IP address. Let's explore what each code means, why this happens specifically to arbitrageurs, SMM specialists, and sellers, and how to configure proxies so that blocks no longer interfere with your work.
What is Cloudflare and why does it block IPs
Cloudflare is a service that stands "in front of" millions of websites around the world: from small online stores to large marketplaces and social networks. It protects websites from DDoS attacks, bots, scrapers, and suspicious traffic. When a request to a site passes through Cloudflare, the system analyzes dozens of parameters: the reputation of the IP address, geolocation, browser behavior, request headers, click speed, and even whether the time zone matches the browser language.
If even one of the parameters raises suspicion, Cloudflare displays a captcha, a "Checking your browser" verification page, or immediately issues an access error with a specific code. For an ordinary user with home internet, this is rare. However, for those who work with multiple accounts, scrape data, or run ads from different locations — this is a daily problem. Users of data center proxies encounter such blocks more often because their IP addresses are widely used by bots and easily end up on the blacklists of reputation databases that Cloudflare uses.
Error 1020: Access Denied — what does it mean
Error 1020 is the most common Cloudflare error encountered by scrapers and automated scripts. It means that one of the custom security rules (Firewall Rules) set by the website owner has been triggered. This could be a rule to "block requests without a referer", "block User-Agents from headless browsers", "block more than N requests per minute from one IP", or "block all traffic from a specific country".
In practice, it looks like this: you open a product page on the marketplace to monitor the price, and instead of content, you see "Sorry, you have been blocked. Error code 1020". Most often, the reason is too high a frequency of requests from one IP address, using a browser without full rendering (for example, a simple HTTP client instead of a real browser), or the absence of cookies and headers that real users have.
Important: Error 1020 is almost never related to temporary server overload — it is a deliberate block based on a security rule. Simply refreshing the page will not lift it.
Error 1005: Access Denied by country or network
Error 1005 means that the website owner has blocked access for an entire country, region, or range of IP addresses (subnet). This is a typical situation for marketers testing Google Ads or Facebook Ads from different geos: if the landing site is targeted only at a US audience, and you access it from an IP identified as Russia, India, or Vietnam, Cloudflare may immediately cut off such traffic.
The same logic works in reverse — foreign services and social networks sometimes block entire blocks of IP addresses from hosting providers and data centers because historically, spam and fraud have come from there. If you are an arbitrageur testing creatives for a specific country's audience but are using proxies from another region or with data center IPs, there is a high likelihood of encountering Error 1005 instead of a normal landing page load.
Error 1006: IP or ASN blocking
Error 1006 is similar to 1005, but a bit more specific: a specific IP address or an entire autonomous system (ASN) is blocked — that is, the entire pool of addresses belonging to a specific hosting provider or data center. This is the most unpleasant error for users of cheap data center proxies: if the proxy provider uses IP ranges from well-known cloud hosting (AWS, DigitalOcean, OVH, and similar), many websites with Cloudflare ban these ranges entirely in advance, even before you make your first request.
SMM specialists and marketplace sellers often complain specifically about Error 1006 when trying to access Instagram, TikTok, or Avito through proxies: the account seems to be "clean", actions are moderate, but the site still blocks access — because the IP address itself has been on Cloudflare's blacklist long before your visit.
| Error Code | Reason for Blocking | Typical Situation |
|---|---|---|
| 1020 | Triggered a custom Firewall rule | Frequent scraping, no cookies, suspicious User-Agent |
| 1005 | Blocking by country or subnet | Accessing from a geo that does not match the target audience of the site |
| 1006 | Blocking a specific IP or ASN of hosting | Using data center proxies with a "compromised" range |
Why these errors are more common among arbitrageurs and SMM
The logic of Cloudflare is based on the reputation of the IP address and behavioral patterns. An ordinary home user has a "clean" IP: it belongs to the provider, real people access it, and requests are rare and diverse. For an arbitrageur or SMM specialist, the picture is different: traffic from one IP can go to dozens of ad accounts, requests to Facebook Ads or TikTok Ads come in batches, and if the same data center proxy is used for several accounts simultaneously — this is a direct signal for the security system.
The same goes for scraping marketplaces: monitoring prices on Wildberries, Ozon, or Avito implies hundreds of requests per hour to the same sections of the catalog. If all requests come from one or several neighboring data center IPs, Cloudflare on the marketplace's side will sooner or later issue Error 1020 or 1006, even if the script is written carefully and does not violate any explicit rules.
An additional factor is anti-detect browsers. Dolphin Anty, AdsPower, Multilogin, and GoLogin effectively mask the browser fingerprint, but if all profiles in them are connected through the same IP or through a proxy with a bad reputation, browser-level masking won't help: Cloudflare blocks not by fingerprint but by network address.
How to fix Cloudflare errors using proxies
The main principle for solving the problem is to change the IP address to one that initially has a higher trust level in the eyes of the security system. Simply refreshing the page or restarting the router almost never helps, as the block is tied either to a specific address or to an entire range. Here’s a working algorithm:
- Identify the error code — 1020, 1005, or 1006 — to understand the nature of the block (rule, geo, or IP range).
- If it’s 1005 — change the geo proxy to one that matches the target audience of the site.
- If it’s 1006 — switch from data center addresses to residential proxies, whose IPs belong to real home providers and are not listed in ASN blacklists.
- If it’s 1020 — reduce the frequency of requests, add delays between actions, and use IP rotation to avoid exceeding the limits of the rule.
- For working with mobile applications and social networks (Instagram, TikTok), consider mobile proxies — cellular operators use one IP for thousands of real subscribers, so IP blocks are extremely rare there.
For one-off tasks — quickly checking a landing page from another country or single scraping — sometimes data center proxies are sufficient, as they are faster and cheaper. However, if the task is regular — monitoring prices on marketplaces, managing dozens of ad accounts, or multi-accounting on social networks — the reputational risk of data center IPs is justified only over short distances.
Which type of proxy to choose: comparison
| Proxy Type | Risk of Error 1020/1005/1006 | Suitable for which tasks |
|---|---|---|
| Data Center Proxies | High — ranges are often blacklisted | Fast scraping without strict protection, speed testing |
| Residential Proxies | Low — IPs of home providers | Multi-accounting, marketplace monitoring, Facebook Ads farming |
| Mobile Proxies | Minimal — shared IP of the operator | Instagram, TikTok Ads, tasks highly sensitive to bans |
Proxy setup in Dolphin, AdsPower, and browser — step by step
To eliminate Cloudflare errors in an anti-detect browser, proxies need to be connected to each profile separately, rather than using one IP for multiple accounts. Here’s how to do it in popular tools:
In Dolphin Anty: open the profile → "Proxy" tab → select type (HTTP/SOCKS5) → insert IP, port, username, and password → click "Check" to test the connection → save the profile. After that, visit the site where the error previously occurred and check if the block has been lifted.
In AdsPower: when creating a new profile in the "Proxy" section, select "Custom" → specify the protocol, host, port, and authorization details → use the built-in IP check to ensure that the geo proxy matches the region you need (this is critical for error 1005).
In a regular browser (for tests without anti-detect): in Chrome or Firefox, manually specify the SOCKS5 or HTTP proxy through network settings, or use a proxy manager extension to avoid altering system settings. After changing the IP, be sure to clear cookies before re-accessing — sometimes the block on Cloudflare's side is tied not only to the IP but also to the session data of the browser.
Tip: when setting up IP rotation for scraping, set the address change interval to no less than several minutes for the same section of the site — too frequent rotation from one ASN can also appear suspicious to Cloudflare.
Checklist: how to avoid repeated blocks
- Check the geo of the proxy before launching ads — it should match the target audience of the landing page.
- Do not use one IP for multiple accounts simultaneously in an anti-detect browser.
- For scraping marketplaces, add pauses between requests and imitate real user behavior.
- For social networks (Instagram, TikTok, VK), prefer mobile or residential IPs over data center ones.
- Clear cookies and cache when changing proxies to avoid conflicts between the old session and the new IP.
- Monitor User-Agent and other headers — they should match a real browser, not default script values.
- If the error recurs on the same ASN — change the proxy provider or type of connection.
Conclusion
Cloudflare errors 1020, 1005, and 1006 are not bugs or temporary failures, but a deliberate reaction of the security system to a suspicious IP address or behavior. Error 1020 signals the triggering of a custom rule, 1005 indicates blocking by country or subnet, and 1006 signifies the banning of a specific IP or an entire ASN range. In most cases, the problem is resolved not by changing the code or script settings, but by switching to a type of proxy that initially has a higher trust level in reputation databases.
If you regularly encounter blocks while monitoring Wildberries and Ozon, managing Facebook Ads and TikTok Ads accounts, or working with dozens of profiles in Dolphin Anty and AdsPower, it is worth switching to residential proxies — they use IPs of real users and almost never fall under Cloudflare blocks by ASN. For tasks particularly sensitive to bans on social networks, mobile IPs can also be considered as an additional layer of protection against repeated access errors.