Wordfence Blocked it own IP address

  • Resolved siteadvice

    (@siteadvice)


    1 week, 3 days ago

    I’m a longtime Wordfence user and I’ve never seen this before. Just got locked out of a site with this message:
    Your access to this site has been limited by the site owner. Your access to this service has been limited. (HTTP response code 503)
    When I managed to gain access I discovered that the IP address of the server had been blocked, presumably locking everyone out of the site.
    Possibly the problem was that the site was long overdue for an update. It was running WordPress 6.0.9 with Wordfence 8.0.3. I’ve upgraded WordPress now!

Viewing 1 replies (of 1 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @siteadvice,

    Sometimes, I’ve seen hosts add/change CDNs such as Cloudflare, or proxy servers (so IP detection that was previously working now doesn’t).

    If IP detection on your site is now incorrectly detecting the server’s IP for each visitor rather than their IP, legitimately triggered blocks for somebody else may block all visitors including yourself. Take note of your own IP on your main device:?https://www.whatsmyip.org.

    Head over to Wordfence > All Options > General Wordfence Options > How does Wordfence get IPs and reference the area under that section that says Detected IPs and Your IP with this setting. See if any of the options there when picked accurately reflect your IP. If one does that isn’t currently selected, don’t forget to hit the SAVE CHANGES button in the top-right after you’re done.

    We do have some documentation around Cloudflare, Litespeed etc. but I don’t want to necessarily bombard you with that if it can be solved with the above method. Let us know if you need further assistance with that.

    Many thanks,
    Peter.

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.