Hi @astridw, thanks for getting in touch!
I think there’s a chance a false-positive is blocking the communication your plugin requires to connect via REST API.
There is a chance that Live Traffic is picking up the block, so it’s worth checking your Live Traffic page. You should be able to see which rule caused the block by clicking the entry (or “eye” icon) to expand it. Sometimes you are presented with a “ADD PARAM TO FIREWALL ALLOWLIST” button here that could solve the problem going forward.
Learning Mode while logged in as an admin may help if you have no luck with the above. From the Wordfence Dashboard click on Manage WAF. Then you will see Basic Firewall Options > Web Application Firewall Status. Change the option to Learning Mode. Now perform or trigger the backup that was causing the issue. Wordfence may learn that the communications taking place at this time are normal and will allow them in the future. After you have finished testing, make sure to switch the WAF from Learning Mode back to Enabled and Protecting.
Let me know how you get on!
Peter.
Thanks a lot for reaching out to me!
I did not see your message until today.
I guess the problem is that I don’t know exactly what triggers the warning message. But I will have a closer look so that I can find the problem.
If you have any hints, I would highly appreciate it.
I will check in again as soon as I have more insights. Thanks again!
-
This reply was modified 3 years, 6 months ago by
AstridW.
Okay, it seems that I’ve found the reasons and the solution.
I’m sharing it here so that anyone with the same issue may find the help needed.
The problem was the plugin: WP Fastest Cache
I went to the preferences for the plugin and in the tab “Ausschließen” (exclude?) I added at the bottom for JS a new rule with “Contains: real-queue/v1”
Since I added this little thing, I did not get any error messages anymore.
If it’ll come back again, I’ll keep you informed. But for now I guess my problem is solved. Thanks a lot!
