How to use fail2ban for web login security behind loadbalancer

I am securing my wordpress login with fail2ban. Fail2ban reads the access logs and evaluates 403 messages - HTTP status header set by wordpress function status_header() - which are created whenever a login fails. Now the issue: since my site is behind a DO load balancer, all 403 errors are therefore associated with internal DO IPs.Is there any way to log the’real’ user IP instead of the one from the loadbalancer?

Best Clemens

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

The outside client’s real source IP is in the X-Forwarded-For header. (Load Balancer reference)

Getting fail2ban to look at that header will involve making sure your HTTP server logs include that header, and then adjusting fail2ban to match on it.

Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up

card icon
Get our biweekly newsletter

Sign up for Infrastructure as a Newsletter.

Sign up
card icon
Hollie's Hub for Good

Working on improving health and education, reducing inequality, and spurring economic growth? We’d like to help.

Learn more
card icon
Become a contributor

You get paid; we donate to tech nonprofits.

Learn more
Welcome to the developer cloud

DigitalOcean makes it simple to launch in the cloud and scale up as you grow – whether you’re running one virtual machine or ten thousand.

Learn more ->
DigitalOcean Cloud Control Panel
Get started for free

Enter your email to get $200 in credit for your first 60 days with DigitalOcean.

New accounts only. By submitting your email you agree to our Privacy Policy.

© 2023 DigitalOcean, LLC.