Wordfence blocking internal ips

  • Resolved easy_c0mpany80

    (@easy_c0mpany80)


    6 years, 3 months ago

    I have WordPress running inside Docker containers for various sites on a host. I recently changed from Sucuri to Wordfence on some of these sites and Im now starting to see some reports of blocked ips that are the internal/private ips of the container that the WP site is running on eg 172.18.0.3. The number of blocks is very small, less than 10 per day and Im not seeing any real affect on traffic. Is this something I need to be concerned about and/or is there a way to fix this?

    thanks

Viewing 2 replies - 1 through 2 (of 2 total)

  • Hi @easy_c0mpany80,

    Wordfence should automatically whitelist private IP addresses.

    Can you take a look at /wp-content/plugins/wordfence/libwfIPWhitelist.php?

    On line number 13: it should read '172.16.0.0/12',: can you confirm that it is not commented out with //?

    Note: 172.16.0.0/12 means that it will whitelist every IP between 172.16.0.0 and 172.31.255.255, which includes the IP address you listed.

    Dave

    Hi again!

    We haven’t heard back from you in a while, so I’ve gone ahead and marked this thread as resolved. If you’re still having issues with Wordfence, please feel free to open another thread!

    Dave

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Wordfence blocking internal ips’ is closed to new replies.