• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue Firewall IP Ban (fail2ban) Wordpress

Alaa Mansour

Basic Pleskian
Hello, everybody, after I have migrated the server, fail2ban no longer ban ip addresses automatically, and put them in a list in the firewall, I have to di it manually, even though the rules of the jails are as same as previous.
I can see the IP address in the list of banned ip under the jail, but I want a permanent ban in the firewall.

what I'm missing?
thanks
Screenshot 2022-01-05 at 08.12.34.png
Screenshot 2022-01-05 at 08.17.18.png
Screenshot 2022-01-05 at 08.11.56.png
 
I am trying to understand your issue but I can't. I believe you have wrong expectations. Fail2Ban doesn't ban anything automatically (hence I am probably misunderstanding you - I am not native English speaker). It will ban only if a specific trigger happens. From your screenshot it seems it is working fine.

Moreover (this is open for debate) but I don't think you'll have any tangible success in permanently adding some IP ranges into anything because most of the serious attackers rotate their IP ranges anyway. Meaning that they change their IP all the time.

That's why (for example) when you go to Fail2Ban settings you'll see that "IP address ban period" is set to a very short amount of time, not permanent. You can set it to whatever but I don't think this will yield any success in practice. Actually opposite. It can cause practical issues for someone legit. If you closely inspect Wordfence firewall (as another example), they also suggest banning for only a couple of hours/minutes, not permanently.
 
I am trying to understand your issue but I can't. I believe you have wrong expectations. Fail2Ban doesn't ban anything automatically (hence I am probably misunderstanding you - I am not native English speaker). It will ban only if a specific trigger happens. From your screenshot it seems it is working fine.

Moreover (this is open for debate) but I don't think you'll have any tangible success in permanently adding some IP ranges into anything because most of the serious attackers rotate their IP ranges anyway. Meaning that they change their IP all the time.

That's why (for example) when you go to Fail2Ban settings you'll see that "IP address ban period" is set to a very short amount of time, not permanent. You can set it to whatever but I don't think this will yield any success in practice. Actually opposite. It can cause practical issues for someone legit. If you closely inspect Wordfence firewall (as another example), they also suggest banning for only a couple of hours/minutes, not permanently.
I have added all these IP address manually, I have enabled (IP address ban period = 604800 seconds)
 
Back
Top