Hi Rhodie,
Thanks for the suggestion!
At the moment, WP Armour doesn’t have integration with fail2ban. I’m not very familiar with its implementation myself, but I’ll need to investigate further to see if this is feasible or something we could support in the future.
Appreciate you bringing it up!
Best,
Dinesh
Hi Rafa,
Thanks for sharing the link.
I checked the page but couldn’t find the JavaScript from our plugin being loaded there. For testing purposes, could you please try temporarily disabling the LiteSpeed Cache plugin and let if know ?
Best regards,
Dinesh
Thread Starter
rhodie
(@rhodie)
Hi Dinesh, and thanks for the reply. Basically, you would just need to log a line with the offending IP address to the server log. Example from wp-fail2ban-redux: “Authentication failure for admin from 209.141.44.35”
(BTW, I think you meant to post the reply to Rafa in a different thread.)
Hi @rhodie,
Thanks for the clarification and yes, you’re absolutely right, that previous reply was meant for another thread (apologies for the mix-up!).
Logging the offending IP address in a structured format like you mentioned (e.g.,
Authentication failure for admin from 209.141.44.35) makes perfect sense and would be a solid approach for fail2ban integration.
I’ll look into adding an option in WP Armour to log spam attempts with IP addresses to the server log in a format that fail2ban can track. It seems like a useful feature that could benefit many users.
Appreciate the suggestion and the example — it really helps!
Best regards,
Dinesh
