Error on IP detection

I would remove varnish. and use apc and memcached, also https://www.ads-software.com/extend/plugins/hyper-cache/. it looks to me like varnish is serving its own ip. Varnish adds a layer of complexity that imo isnt worth the headache by the time your done futzin with the vcl file to handle cookies and find that your site isnt any faster. apc is easy enough and installing memcached is a 3 step ordeal with no config neccesary.

see https://rtcamp.com/tutorials/why-we-never-use-varnish-with-nginx/
they also have a great tutorial for installing APC

Thanks for the response WCat!

At this moment, we are behind a managed server in which he had no access to the setup of the box, so we cant do such a thing.

Is there an alternative way for Wordfence to bypass this problem?

We are having the same issue with Varnish and Wordfence.

At one point, the admins were actually blocked as the plugin through we were fake googlebots.

We are using Apache and varnish. Does anyone know which option to select for ‘how does Wordfence get IP addresses’? The issue happened after we selected ‘Get X-Forwarded-For HTTP Header’.

Varnish has certainly improved the speed of the site more than just Supercache and W3TC, so we would ideally like to get it working with Wordfence.

Hi Guys,

Can you tell me which HTTP header Varnish uses to send the real IP of clients to the web server?

Thanks,

Mark.

Hello and thanks for your answer mmaunder!

The header sent is:

X-Varnish:·1817241226·1817236706(CR)(LF)