• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Resolved Fail2Ban Update By Plesk?

learning_curve

Golden Pleskian
The question has been asked before by others: Question - fail2ban update because it was last updated, prior to Obsidian being upgraded to General Release status: Change Log for Plesk Obsidian yet there's still no sign or inclination, that this well overdue update, will be arriving anytime soon...

You can't (well not very easily....) upgrade Fail2Ban yourself - if you're using Plesk Obsidian - as it's a Plesk enhanced version of the general release Fail2Ban that you're using, similar in many ways to the Plesk enhanced PHP releases which Plesk do a great job of!

The current Fail2ban release via Plesk is this one: https://github.com/fail2ban/fail2ban/compare/0.10.3.1...0.11.2 The current Fail2Ban general release is this one: Release 0.11.2 (2020/11/23) - heal-the-world-with-security-tools · fail2ban/fail2ban and the differences between them are here: https://github.com/fail2ban/fail2ban/compare/0.10.3.1...0.11.2

Can anybody from Plesk tell us more?
 
Well.... no reply yet so a quick bump.
Also for reference, this thread: Question - Plesk Firewall/ CSF but a link from within it: How to Install and Configure CSF which includes this:
(Quote): "...Another key function of CSF is that it will check for failed login authentications on mail servers (IMAP, Exim, uw-imap, Dovecot, Kerio), Ftp servers (Pure-ftpd, Proftpd, vsftpd), OpenSSH servers, and Plesk & cPanel servers for replacing software such as fail2ban..."
 
Would love to hear from Plesk about this. You could in theory compile the latest f2b from source and replace the plesk-native library. I don't believe there's any component that *requires* the Plesk optimized binaries to run,

Edit: Will try this when I get a chance to and report back
 
Last edited:
For now, I can only say that we have plans for updating this component in Q2.
Please be patient.
 
As far as replacing f2b from source:

Code:
rpm -q fail2ban

Should show plesk's fail2ban package, ie

fail2ban-0.10.3.1-2.centos.7+p18.0.33.1+t210225.1402.noarch

Remove the packages:

Code:
yum remove fail2ban

Then install from epel-repo (must have epel installed)

Code:
yum install fail2ban --disablerepo="PLESK_18_0_VER-extras"

(replace VER with Plesk version)

Code:
rpm -q fail2ban

Should show something without the +18.0.3

Restart the fail2ban service daemon with systemctl

fail2ban-client status -> this should show all your previously active jails.

The downside to this is that it will disable the Plesk fail2ban interface. I have not found a workaround for this and probably won't recommend doing this.
 
Back
Top