• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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

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
 
You must log in or register to reply here.

Similar threads

F
Issue Fail2ban error with Almalinux ¿nf_tables?
Replies
1
Views
705
Fede Marsell
F
A
Issue Problems with fail2ban
Replies
1
Views
1K
Kaspar@Plesk
Kaspar@Plesk
wakabayashi
Resolved Fail2Ban - Postfix not working for SASL (bug?)
Replies
4
Views
2K
mizar
mizar
K
Resolved Plesk panel update fails with "certificate has expired"
Replies
3
Views
609
Sebahat.hadzhi
Sebahat.hadzhi
T
Issue mysqldump: Got error: 1932: "Table 'psa.WebsitesDiagnostic' doesn't exist in engine" when using LOCK TABLES
Replies
6
Views
653
TrevorM
T
Back
Top