• Resolved ellmann creative

    (@ellmanncreative)


    Hey there.

    We once asked about the IP range of the scanner/network, since until we deploy a site live we’re using IP-based (and fwDNS-based) access. Obviously this messes with WordFence. The answer you gave us at the time was the equivalent of 69.46.36.0/27.

    Has this range expanded? We’ve recently been seeing some issues initiating manual scans, typically ending in “Scan failed”, but it looks to be random – so, my first idea was “maybe it’s failing connection from outside this range”.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @ellmanncreative, thanks for getting in touch.

    The range you mention would’ve been correct at the time of your previous advice but a server migration performed a number of months ago introduced a new series of IPs that should be allowed. This is not likely to often change but we do have a page where they are always kept up to date for your reference.

    You can check them at: https://www.wordfence.com/help/advanced/#servers-and-ip-range

    Let me know how that goes for you.

    Peter.

    Thread Starter ellmann creative

    (@ellmanncreative)

    So, those three (top) IPs (as of 2021/06/01) should be an exhaustive list of IPs my webhost should see as “origin” for WordFence, yeah?

    Plugin Support wfpeter

    (@wfpeter)

    Hi @ellmanncreative,

    That’s correct, if you use or are likely to use Central you could also allow the three below too to prevent connection errors occurring.

    Thanks again,

    Peter.

    Thread Starter ellmann creative

    (@ellmanncreative)

    Thank you.

    I consider this support request resolved to my satisfaction.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Scanner IP range update?’ is closed to new replies.