Cloudflare Error 1020: what it means and how to respond
A Cloudflare Error 1020 page is not a normal server failure.
It is the Cloudflare-protected website telling your client that a firewall rule has denied the request. The rule may be broad or narrow, but the practical result is the same: the origin content is not served to that request. This guide explains the signal, separates it from neighbouring HTTP and Cloudflare errors, and gives a practical checklist for changing automated request behaviour.
What Cloudflare Error 1020 means
Cloudflare Error 1020 is the Access Denied error. It appears when a request violates a firewall rule configured by the Cloudflare-protected website. The rule could be aimed at a particular path, a request pattern, a client fingerprint, a network range, or a combination of conditions. Sending too many requests is one possible reason, but it is not the only one. Treat the response as a policy decision by the site, not as proof that the site is down.
A useful first distinction is between a browser check and an automated request. If the same page loads normally in an ordinary browser but an automated client receives 1020, the problem is likely in how the automated request is presented or paced. That points toward request identity, proxy choice, request frequency, or the tooling used to drive the browser.
How 1020 differs from 403, 429, 503 and 520
Cloudflare Error 1020 is specifically a firewall-rule denial. It is not the same as a plain 403 status code, a 429 rate-limit response, a 503 service-unavailable response, or a 520 origin error. Those codes can appear for different reasons and may call for different responses. The related-question list below links to separate explanations for each of those cases so you can compare the signals rather than treating every block as one problem.
Use the error code as a diagnostic clue. If the response is 1020, start with the site's firewall policy and your request profile. If the response is 429, pacing and rate limits deserve attention first. If the response is 503 or 520, the origin or service availability may be involved. The code narrows the investigation; it does not by itself prove intent or guarantee that a particular workaround will succeed.
A practical checklist for reducing 1020 responses
Work through the following checks before assuming the site is permanently closed to automation:
- Confirm the page still works in a normal browser. If it does not, investigate the site or your network first.
- Review request volume and timing. Reduce burstiness and add sensible delays where appropriate.
- Review the client identity presented by your tooling. Automated browser drivers can expose patterns that ordinary browsing does not.
- Review proxy quality and rotation. A reliable proxy provider can change the network identity of requests, but it does not override a site's rules.
- Consider a maintained browser-automation tool such as undetected-chromedriver or a similar option, paired with appropriate proxies, when the goal is to present a more ordinary browser session.
- If managing this yourself is not the right fit, a scraping API can handle request delivery and blocking mitigation on your behalf.
These are mitigation options, not guarantees. A site can change its firewall rules at any time, and a technique that works for one property may not work for another.
Worked example: browser works, script gets 1020
Suppose a product page opens normally in your desktop browser, but a script requesting the same URL receives a Cloudflare 1020 page. The contrast is the useful evidence. The site is reachable, so the next question is what differs between the two requests: the client fingerprint, the network address, the request rate, or the automation stack.
A reasonable sequence is to slow the script, check whether the automation driver is exposing an obvious pattern, and test with a reputable proxy arrangement. If the page still returns 1020, the firewall rule may be targeting more than simple frequency. At that point, either refine the request profile further or use a scraping API that is designed to handle blocked requests. Record what changed between attempts so you can tell which adjustment mattered.
Learn more about scraping without blocks
If you want a broader treatment of request pacing, proxies, browser automation, and block mitigation, see the linked guide on web scraping without getting blocked. It expands on the practices summarised here and gives more context for choosing between self-managed tooling and a scraping API.
Frequently asked questions
What causes Cloudflare Error 1020?
It is caused by a request violating a firewall rule set by the Cloudflare-protected website. Sending too many requests is one possible trigger, but the rule may also target request patterns, client identity, or network characteristics. The error means the request was denied by policy, not that the site is necessarily unavailable.
Is Cloudflare Error 1020 the same as a 429 rate-limit error?
No. A 429 status code is specifically about rate limiting, while 1020 is an Access Denied response tied to a firewall rule. A 1020 can be triggered by excessive requests, but it can also arise from other rule conditions. The distinction matters because the first diagnostic step differs: for 429, review pacing and limits; for 1020, review the request profile against the site's firewall policy.
How can I avoid Cloudflare Error 1020 when scraping?
Improve the request behaviour rather than retrying blindly. Reduce burstiness, review the client identity exposed by your automation tooling, consider a maintained browser driver such as undetected-chromedriver, and pair it with reliable premium proxies where appropriate. A scraping API is an alternative if you prefer to delegate request delivery and block mitigation. None of these options guarantees access, because the site controls its firewall rules.
Why does the page work in my browser but return 1020 to my script?
The difference is usually in the request itself: the client fingerprint, network address, request rate, or automation stack. If the page loads normally in a browser, focus on what your script presents differently. Adjust pacing, review the driver, and test with a reputable proxy arrangement before concluding the site is entirely inaccessible.