APO for WP causes Wordfence bans for logged in users which cause bans for all
-
Hi,
first of all thanks for the effort aroung APO for WP. I really like the concept & the ide. Tried it out in morning & activated it on our sites.
Everything seemed to work fine, unitl users started getting blocked by Wordfence ( general block. 503 code, can’t find more info why )… It’s either that generally Wordfence doesn’t see the incoming traffic after APO enabled as trustworthy, or that there are some settings that cause this.
Now what seems strange and not really expected is that when APO was enabled, Wordfence showed all our user traffic, or most of it atleast, from the US – this is strange but I suppose it’s a feature of APO.. because we don’t use a VPN or anything else. After disabling APO, the IPs & their countries are back to our European countries as they should be… What’s worse is that it seems that Wordfence seems to think, that all users come from the same IP ( which I suppose is Cloudflare’s edge ), and therefore there is way too high of a chance, that it blocks some actions of some users and by that it blocks the IP and blocks all users = site is inaccessible. Even https://www.uptimerobot.com saw the sites as offline, because it got rerouted through the same IP and received a 503 response as all other users…
Until we solve this issue, we’ll need keep APO disabled ( sad face )
Wordfence IP setting is on:
“Use the Cloudflare “CF-Connecting-IP” HTTP header to get a visitor IP. Only use if you’re using Cloudflare.”I hope we manage to solve this soon! Thanks! ??
- The topic ‘APO for WP causes Wordfence bans for logged in users which cause bans for all’ is closed to new replies.