Ray ID identifies each request with a random string, it won’t be useful here.
What you should do is create a WAF exception, so that this specific rule is skipped when certain conditions match, such as the relevant URI Path + your IP address, for instance.
I added my ip4 address + the uri and it lets me thru with the rulesets active. They now challenge the security but once thru it is fine. I don’t mind the extra step if it is safer. Thanks for the advice. I thought I tried that before though I didn’t use two conditions
In all likelihood another rule (or perhaps another Cloudflare security feature) is doing this. If it’s another Managed Rule, you can if you wish add this other rule in the same WAF exception you created.
Did you create the WAF Exception, as suggested? If so, you can edit it to add this other rule you’ve just identified.
You can also create a WAF Custom Rule with action set to Skip, and list all security features you want skipped for requests from your IP, as long as you have control of it.
I am about ready to just turn it off while I work. I already have to switch to dev mode when I do that. I wish I could be a web engineer and a web content manager with two heads and four hands.
As noticed by @epic.network your rule will never match because you’re trying to match the hostname (example.com) against the URI field, which represents /path?query-string:
Also, when I suggested you matched both IP and path, I was thinking a rule that would only apply to a limited set of paths. Since you seem to want to match it against any request, you could simply remove the URI part, and just match against your IP address.
Your screenshot shows the block with an “OWASP Score” of 38, which implies that you have it set to be pretty aggressive. You could also try reducing the overall threshold and paranoia levels:
