It is our backend website that is affected. Cloudflare is displaying a challenge page when we use some critical functions. However, it appears as this popup in which we can see just HTML and not actually interact with it. If anyone has any ideas, that would be great as it is blocking critical functions for us.
If it comes from Cloudflare, you should be able to see the challenged or blocked event under the Security tab → Events at Cloudflare dashboard for your zone and know exactly which security option was triggered.
Once you find them, click on a particular one to find more details about it (user-agent, IP, HTTP version …). If yes, could you share some details which service was triggered that blocked you?
Wonder if it was Browser Integrity Check or something else was triggered such as Custom WAF rule with e.g. JS Challenge, if you’ve got some, based on the one of the criteria.
Hi, thank you very much for helping!
Yes I did find one event that started it:
It was one event that Cloudflare blocked successfully based on Managed rules - Cloudflare Managed Ruleset efb7b8c949ac4650a09736fc376e9aee, rule Anomaly:Header:User-Agent - Fake Bing or MSN Bot (ae20608d93b94e97988db1bbc12cf9c8).
Unfortunately, 66 seconds later it started “Managing” our internal computers’ “challenges” based on Managed rules - Cloudflare OWASP Core Ruleset (4814384a9e5d4991b9815dcfc25d2f1f), Rule 949110: Inbound Anomaly Score Exceeded (6179ae15870a4bb7b2d480d4843b323c). We were unable to use particular functions on particular computers.
I can see now that the OWASP ruleset will need some tweaking so that this doesn’t happen again, especially with our internal addresses. It did manage to block some attacks during the time it accidentally blocked us, so that’s great without a doubt.
Thank you for pointing me in the right direction!