Need help?

Our experts have had an average response time of 13.52 minutes in October 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

CloudFlare OWASP inbound blocking – How to resolve

by | Nov 25, 2021

Wondering how to resolve CloudFlare OWASP inbound blocking? We can help you.

As part of our Server Management Services, we assist our customers with several CloudFlare queries.

Today, let us see how our Support techs resolve this error.

How to resolve CloudFlare OWASP inbound blocking?

Basically, the Cloudflare WAF contains mainly 2 packages.

Cloudflare Managed Ruleset:

These rules are manage by Cloudflare WAF Engineers.

For “security reasons”, the rule patterns are not provided as this would increase the likelihood that a malicious party could learn to bypass the rules.

OWASP ModSecurity Core Rule Set:

These rules are not manage by Cloudflare.

They are created by the OWASP Group 14 and Cloudflare integrates with this OWASP package as part of our WAF for additional security.

Today, let us see the different methods followed by our Support Techs to resolve it.

1. Firstly, add the IP(s) doing the request to the IP Access Rules 30 in the allowlist, if the users connecting to your backend are always using the same IP address.

This is the best solution as it does not affect the site security.

2. Then, disable the affected WAF rule(s)

This will reduce the security of the site, but will stop the requests from getting blocked/challenged.

3. Next, bypass the WAF with a Firewall Rule

Here, you can create a Firewall Rule with the bypass action for the WAF to deactivate for a specific combination of parameters.

4. Next, disable the Web Application Firewall from the request endpoint.

This will result in lower security, as the WAF will no longer applicable on that location.

This action is done by using Page Rules

5. Then if the rule blocking is 981176, it means it was block by the OWASP rules.

You need then to decrease the OWASP sensitivity.

If decreasing the OWASP sensitivity doesn’t solve the issue, you might need to apply one of the other actions describe above (1, 2, 3 or 4).

6. Then, use Waf Overrides API

There is a way to disable one WAF rule for a specific URI.

The feature is known as the URI-Controlled WAF.

[Stuck in between? We’d be glad to assist you]


In short, today we saw steps followed by our Support Techs to resolve CloudFlare OWASP inbound blocking.


Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.



Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center


Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]


Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid


Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie


These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.