Replies: 3
My site has been intermittently encountering the error in the linked screenshot, and I’m not clear what blocking rule is being triggered. Rate limiting is disabled and we turned off participation in the Wordfence Security Network because it was triggering too many 503 errors for our visitors as well.
Which brings me to my next theory. We’re currently hosting it on Liquid Web Cloud Sites, and we’re using the X-Forwarded-For HTTP header method for determining IP address. This has 2 IP addresses listed in the plugin settings, one of which I believe is the Cloud Sites load balancer in addition to mine client IP address. I’m wondering if this is normal behavior, having 2 IP addresses, and if not, could it explain why the 503 error is happening (because perhaps all requests have the same common IP addresses coming from Liquid Web alongside the true client IP, and the blocking rules are being triggered for some visitors incorrectly based on those common IPs.
Ideas welcome!