I’m really sorry to say, but we’re in the same bucket
And I can confirm I’ve experienced it while testing and troubleshooting on a Free and Pro plan.
Same error, same thing, different ruleset. No way to bypass / add exception.
Other people are also reporting this and experiencing the same issue on a Free plan and topics which can be found using .
Furthermore, as on a Free plan, currently we cannot “Add an exception” for that or some other particular “Managed Rule” because there is no button for it, yet, as it exists for a Pro plan which contains it.
There was some rumors that we should switch (not sure how!) to the new WAF on a zone with a Free plan, however I couldn’t manage to do the “migration” from the old WAF to the new WAF on a zone with a Free plan yet as described at the link from below. Seems like the mission impossible as it doesn’t work at all.
There are a lot of topics, and currently no answer on this one yet
I’ll update my post once I’ve got some feedback information, I hope.
You could try to add the IP to the WAF → Tools → IP Access Rules with the action “allow”, maybe that would help, but that’s really not the permanent solution on those kind of cases.