• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question List based permanent bans with fail2ban

Hi AusWeb,

Quoted from another thread:
Hi UFHH01,

I'm facing a similar issue with all my Magento websites. Bot trying to hack. username/password using a common URL.

I pmed you about Fail2Ban, trying to ban few IPs. I only need a guidelines. Could you please have a look?
... and the ( previous ) additional private message ( :rolleyes: ) if I can help you here in your thread, is kinda strange and pushy, sorry. Pls. leave a decision up to me, if I would like to answer to a forum - thread.



Nevertheless, my recommendation is to use the "recidive" - jail, which bans previous banned intruders for a longer time ( i.e. 3/6 months, or even a year, depending on your unique settings ). If you start manual addings, you will have a never-ending-hobby and the effect is the same. ;)

if there is a way i can do it without restarting fail2ban everytime new IP added that would be great.
You have two options, to RELOAD the Fail2Ban - configuration, or a Fail2Ban - jail, without a Fail2Ban - restart:

Reload the Fail2Ban - configuration:

fail2ban-client reload

Reload a Fail2Ban - jail:

fail2ban-client reload JAIL-NAME
 
Back
Top