Website Maintenance & Hosting

Cloudflare Error 1020 or 403 Blocking WordPress Visitors? Diagnose the Security Event

Use the blocked request as evidence. This guide explains how to collect a Ray ID, locate the responsible Cloudflare security feature, make a narrow correction and verify that customers can complete the action that failed.

Editorial portrait illustration for: Cloudflare Error 1020 or 403 Blocking WordPress Visitors? Diagnose the Security Event
Editorial illustration using Nithu’s supplied portrait; not a client incident screenshot or measured result.
In this guide

If a legitimate visitor receives Cloudflare error 1020 or a 403 block on your WordPress site, find the security event for that request before changing protection. The event identifies which feature and rule acted. Repairing that specific match is more reliable than disabling Cloudflare or allowing a customer’s entire network without understanding the cause.

A 403 response alone does not identify Cloudflare. WordPress, a security plugin, your host or another proxy can return the same status. Preserve the error page, response details and timestamp so you can establish where the refusal happened.

Know what 1020 means today

Cloudflare’s current 1020 documentation describes a configured security feature blocking a request and returning HTTP 403. It specifically distinguishes 1020 from the block response used by WAF custom and managed rules. Avoid treating every WAF refusal as the same error or following a fix written for a different security feature.

The customer’s screenshot is useful, but the matching event matters more than the wording on the screen. Record whether the visitor was browsing, logging in, submitting a form or returning from a payment provider. A page can load while a later background request is blocked.

Collect a small, useful incident record

  • The full affected page or endpoint URL, with confidential query values removed from ordinary support messages.
  • The time of failure and timezone, plus the Cloudflare Ray ID if displayed.
  • The visible error and the action immediately before it appeared.
  • The browser, device and whether the visitor was signed in.
  • Whether a second trusted test connection reproduces the same failure.

If an administrator asks the visitor for their public IP to locate an event, use an appropriate private channel and retain it only as needed for support. Never request a password, session cookie or payment-card details to diagnose a block. Avoid sending full browser archives that may contain authentication data without review.

Find the rule that acted

In the Cloudflare account for the affected zone, open security analytics and locate the Events view. Search using the Ray ID or other available request details, with the correct time range. Cloudflare’s Security Events documentation explains the investigation tools and available event detail. Visibility and historical availability depend on the account and product.

Read the security source, action and rule identifier. Then compare the request’s hostname, path, method and other relevant attributes with the rule’s intent. Ask whether the rule matched a legitimate action accidentally, whether the request was malformed, or whether the integration is using an unexpected endpoint.

If no event appears, work through these possibilities:

  1. Wrong context: confirm the account, zone and hostname, and allow for timezone differences.
  2. Wrong request: check the blocked submission or background call, rather than only the page the visitor initially opened.
  3. Incomplete visibility: review the available retention, sampling and product logs with the account administrator.
  4. Another system returned 403: compare host access logs and WordPress security logs to identify its source.

Make the smallest justified correction

The owner can collect evidence and identify the customer journey. A Cloudflare administrator should review the rule and preserve its existing configuration before editing. The WordPress developer should check whether the application sent a valid request and whether recent custom code changed its path, method or data format.

A correction might narrow an overly broad expression, adjust a documented integration expectation or create a tightly scoped exception for a confirmed false positive. The right action depends on the feature. Do not paste a WAF skip expression into a different product’s configuration and assume it has the same effect.

Avoid site-wide exemptions for checkout, administration or an entire country merely because one legitimate request failed. Shared IP addresses and changing mobile networks also make permanent customer-IP allowances brittle. Write down the exact rule change, its purpose, review date and rollback step.

The safer Cloudflare WAF rollout guide covers broader configuration planning. Keep this incident focused on the event that blocked the visitor. If only a form submission fails, the Contact Form 7 request diagnosis may help investigate the WordPress side.

Retest the action, then its result

Repeat the same journey on the previously affected browser and connection where practical. Test the precise blocked endpoint through normal site use. Confirm that the server accepted the request and that the intended result exists: an enquiry record, successful login or correctly reconciled order.

For a payment-related return, check payment-provider and WooCommerce records before retrying the purchase. Passing the block page does not tell you whether the original payment completed. Test other critical journeys affected by the rule’s scope and inspect fresh events for unexpected matches.

Keep reviewing security logs after the change, using the WordPress logging guide to coordinate application evidence. Successful customer access and preserved protection both belong in the acceptance record.

FAQs

Can a visitor remove error 1020 themselves?

The site owner controls the relevant security configuration. A visitor can send the screenshot, time and Ray ID through the site’s support channel; repeated attempts do not repair the rule.

Does every Cloudflare WAF block show 1020?

No. Current Cloudflare documentation distinguishes 1020 from WAF custom and managed rule block responses. Use the matching security event to identify the responsible feature.

Why can I open the homepage but not submit a form?

The submission is a separate request and may match a different rule. Collect evidence for the failed form request and verify both the submission and the stored enquiry after repair.

Prepared for website owners by Nithu / Suthakaran Nithursan. Dated advisory facts link to primary sources. Examples are illustrative and are not client results or guarantees.