Question
Wordpress Droplet 20.04 issue with fail2ban plugin obsolete filters
- Posted on February 18, 2023
- DigitalOcean DropletsWordPress
Asked by Jochen Goldenstein
Hi I am using the wordpress droplet on ubuntu 20.04.The Wp-fail2ban plugin updated to version 5.0 and I get issues about obsolete filters
-
wordpress-hard.confis obsolete (version 4.4.0.8). -
wordpress-soft.confis obsolete (version 4.4.0.4). -
wordpress-extra.confis obsolete (version 4.4.0.4). You should update yourfail2banfilters as soon as possible.
How can I update?
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!
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.
Hollie's Hub for Good
Working on improving health and education, reducing inequality, and spurring economic growth? We’d like to help.
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.
I found the answer: To update the filters you have to download them from the plugins.svn.wordpress.org directory and move them to the filter directory of fail2ban.
I found this solution in this german blog post www.my-it-brain.de/wordpress/wordpress-mit-fail2ban-vor-brute-force-angriffen-schuetzen/
The docs I found addressing this issue are here: https://docs.wp-fail2ban.com/en/5.0/maintenance.html Gotta read them carefully as they aren’t the most beginner-friendly.
But the Site Health warning doesn’t go away even after following the instructions and updating the 3 conf files, similar to @Red de Leon’s previous comment.
Anyone got any solves?
I’m having the same problem using the one-click WordPress installer and even after updating the three conf files to the current 2023 versions from SVN, it’s still saying that the filters are outdated.
I also noticed that when I SSH in using the web console, there is a readme that says fail2ban is installed in mu-plugins, but it’s not installed there. It’s in the regular plugins directory.