Check on the options page for “how wordfence gets its IP’s and pick the option that best fits your hosting situation. If you are unsure, its ok to try them all and scan in between to see which one works. Let me know if this fixes it for you.
tim
I called our host support and asked them about this, trying to get the options set correctly. They enabled the x-forwarded-for header in Varnish and confirmed the web server’s access log is now showing the correct visitor IP address instead of the local server’s IP address, and then I chose that setting within the WF options, but it still doesn’t report actual IPs.
We have 25 sites now that are all reporting incorrect information. What changed in WordFence and why? This is pretty frustrating.
Try cycling through those drop down options and see if one of the other ones fix it. Don’t change with hosting provider since we know they fixed the initial problem.
tim
