• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Almalinux - Fail2Ban - Dont Start - BUG ?

marcelhalls

New Pleskian
Server operating system version
AlmaLinux 8.10 (Cerulean Leopard)
Plesk version and microupdate number
Plesk Obsidian v18.0.63_build1800240825.09 os_RedHat el8
I have a problem that after the last Plesk update, fail2ban no longer starts.

I searched the forum and did several things:
Reinstallation of fail2ban;
Recreate log files;
Remove fail2ban and remove files from /etc/fail2ban then reinstall;

And it was not possible to start it.

The error log is very vague, empty! It does not indicate the reason for the error!

I attached the error messages.

I don't know what else to do!

Sometimes I think that by switching to Ubuntu I will have fewer problems.
 

Attachments

  • Screenshot_65.png
    Screenshot_65.png
    44.5 KB · Views: 6
  • Screenshot_66.png
    Screenshot_66.png
    195.5 KB · Views: 6
  • Screenshot_67.png
    Screenshot_67.png
    58.6 KB · Views: 5
  • Screenshot_69.png
    Screenshot_69.png
    40.2 KB · Views: 6
[SOLVED]

A ticket was opened with Plesk (by the way, I recommend it to everyone, the paid support is very TOP)

And it was identified that my fail2ban is not compatible with Python 3.9.

Plesk Support created a way to use version 3.6 (which already normalized my fail2ban) and created a "lock" so that future Plesk updates do not remove this fix.

Until fail2ban is compatible with version 3.9 in Python
 
Back
Top