• Has anyone experienced an issue where WF adds the server IP to its block list for triggering Rate Limit rules? I’d assume WF wouldn’t need the server IP to be added to the whitelist but am I wrong assuming that?

Viewing 3 replies - 1 through 3 (of 3 total)
  • I’ve seen it happen every so often. It’s usually because something on your site is connecting back to itself (we do to start scans but only once a day) or because that you need to change the way WF gets its IPs on the options page. The easy way to check for the latter would be to watch live traffic and see if every IP looks the same or is unique. If they look the same change the setting I mentioned, save, and check live traffic. When you start seeing real IPs of visitors, then keep that setting and see if the problem persists. Adding the server IP to the whitelist on the options page will fix the issue but if you aren’t getting unique IPs it means you will be whitelisting all traffic to the site.

    tim

    Thread Starter helloelectro1

    (@helloelectro1)

    I think I am able to trace it back to implementing xVarnish. Once I disabled it, no more issue. I realized it after I read a little more into how it functions. For Varnish and Reddis, is there a particular setting in WF you recommend?

    Hello!
    You should be able to get it working if you change the setting for how Wordfence gets IPs on the Wordfence Options page. Please check out our docs on this here.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Wordfence blocking the server IP?’ is closed to new replies.