CF blocks itself

Hi,

For an account in the Free plan - if you enabled “Security > Bots > Bot Fight Mode”, and then go to “Speed > Observatory” and run a test, it fails with a message like:
"
Test failed

We were not able to run test for account-domain/.
Before you run another test, check the URL is correct, the server is responding, and the firewall is not blocking requests. (Status code: 403)
"
A. The text - if a firewall is blocking, HTTP error of 403 cannot happen as the traffic will not pass layer 3/4. Consider enhancing the text

B. At “Security > Events” you will see the blocking events with the following attributes:
Service: Bot fight mode
ASN: AS15169 GOOGLE
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36 CloudflareObservatory/1.0

If this anti-bot service is disabled - the scan passes just fine.

So, it looks like an enabled “Bot Fight Mode” is blocking it blocks your own Observatory scan service.

FYI.

This is expected. Observatory is an automated tool, which is what Bot Fight mode is designed to block.

2 Likes

So why it doesn’t happen in the Pro plan?

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.