Quick answer
A blocked request can come from a firewall rule, bot control, rate limit, or another protection. Identify the exact event before changing security settings so a narrow issue does not become a broad reduction in protection.
Before you begin
Record the affected URL, action, time zone, visible error, and any request or Ray ID. Confirm the website and Cloudflare zone under review.
What to do
- Reproduce the legitimate action once if safe and identify the matching event through authorized security access. Avoid repeatedly submitting payments or forms.
- Inspect the action, rule, and request characteristics available in the event. Distinguish an edge block from an application or hosting error.
- Compare the request with the intended website behavior and rule purpose. A request being blocked does not automatically mean the protection is incorrect.
- If a false positive is confirmed, prepare the narrowest appropriate adjustment and review its security effect. Avoid disabling an entire protection layer as a first step.
- Test the original action and relevant unwanted behavior after the approved change. Record the rule scope and how to reverse it.
How to check the result
The legitimate workflow should work without a broader exception than necessary. Verify the actual request outcome; a saved dashboard rule is only configuration evidence.
If you need help
Send redacted event details and reproduction steps through support. Network captures can contain cookies, tokens, or form data. Do not publish them or change origin exposure, authentication, or certificate validation simply to bypass an unexplained block.
Related help
- Connect Your Domain: DNS, Nameservers & Cloudflare
- Use website error logs to diagnose a failed request
- Report a website problem so it can be reproduced
Official references
Reviewed October 31, 2026. Interfaces, vendor availability, and account features can change. Check your current account before making changes.
