Add Nginx Jails to Fail2Ban
Plesk has - praise be - increasingly better supported Nginx, now with the option to use only Nginx, which is great.
That being so, now we need the next logical step: The Fail2Ban Jails for Apache are available, but will have no effect, as Apache is not used at all any more. So we need some Jails for Nginx.
This is not exactly rocket science, there are plenty of examples to be found on the web, the Fail2Ban distribution has some, and here's an article on digitalocean:
https://www.digitalocean.com/community/tutorials/how-to-protect-an-nginx-server-with-fail2ban-on-ubuntu-14-04
Search for: fail2ban nginx 404
E.g. https://nichteinschalten.de/apache-nginx-404-fail2ban-regex/
Note The 404 code is in proxyaccesslog + proxyaccessssllog, do not look in proxyerror_log (which says it in words, not codes:
"failed (2: No such file or directory), client: 173.244.36.57," And seems to sum messages over much longer times. Is it rotated at all?
Enough tips, I'm sure Plesk Team can do a great job.
Come on guys, vote this one up!
Thanks, Tim
Tim Reeves
shared this idea
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
—
IG
-
Othmane
commented
I use only nginx, so it's very important.
-
JT
commented
As I only use NGINX I would strongly support this proposal!
-
Tim Reeves
commented
After 1.5 years I'm surprised that so few upvotes happened - it appears that people either don't use the "Nginx only" possibility very much, or they do but just don't care about the jails.
I gave up waiting and got around to creating the neccessary jails myself, see my blog article (in German): https://timreeves.de/internet-technologie/plesk-wordpress-fail2ban-jails-fuer-nginx/
Would be great if Plesk could take up the energy I've put in, and make them available in the distribution.