• 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.

fail2ban

  1. Azurel

    Question Sudden drop in Fail2Ban banned IPs — anyone else seeing this?

    Hi everyone, for years, my total number of banned IPs hovered around 3,000. Over the past few days, I’ve noticed that the number of banned IPs has dropped to around 700. That’s unusually low, and quite a surprise. Has anyone else noticed something similar? Fewer attacks would be welcome, but...
  2. miagg

    Resolved Backup Manager unable to back up banned IP addresses

    After upgrading to AlmaLinux 9 and Plesk 18.0.80, backup manager shows this warning on every backup. Unable to back up banned IP addresses. Error: f2bmng failed: ERROR:__main__:Failed to get packages by files: package manager returned 5 lines instead of expected 3. Command was ['/bin/rpm'...
  3. N

    Issue Ban ipv6 error

    if i try to ban ipv6 i have this error "ArithmeticError: Bit shift by negative number (Address.php:871)"
  4. O

    Issue LogBrowser, Fail2ban and SASL filter

    Good morning, I've read a lot about 'problems' with Fail2ban sals filter, and the "solution" was to use postfix[mode=auth], but in my case it doesn't work. After a little troubleshooting, I have found this inconsistency beetween what is showed on LoBbrowser and what I found on maillog...
Back
Top