• 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 Creating a new fail2ban jail restarts the service

JVG

Regular Pleskian
Server operating system version
Debian 12
Plesk version and microupdate number
18.0.70 #1
Hi,

when creating a new fail2ban jail in fail2ban (v1.1.0) through the Plesk UI (v18.0.70#1), the fail2ban service is restarted, clearing the banned IPs and forcing to restore all the previous bans. This causes a spike in CPU usage until all the IPs are banned again.

Is that the desired behaviour when creating new jails? Because it's a problem when you have to create a new "emergency jail" when there's a ddos attack to a website.

In previous versions of Plesk+Fail2ban (18.0.44#3 + v0.11.2) , when you created a custom new jail the previous jails didn't change, and the service wasn't restarted.
 
Back
Top