• Dear Pleskians! The Plesk Forum will be undergoing scheduled maintenance on Monday, 7th of July, at 9:00 AM UTC. The expected maintenance window is 2 hours.
    Thank you in advance for your patience and understanding on the matter.

Resolved Ubuntu 24.04 - Fail2ban not working

khuramrr

New Pleskian
Server operating system version
Ubuntu 24.04
Plesk version and microupdate number
18.0.61
18.0.61 on Ubuntu 24.04

fresh install and fail2ban doesn't work.

any solution?


systemctl status fail2ban
× fail2ban.service - Fail2Ban Service
Loaded: loaded (/usr/lib/systemd/system/fail2ban.service; enabled; preset: enabled)
Drop-In: /usr/lib/systemd/system/fail2ban.service.d
└─50-ensure-log.conf
Active: failed (Result: exit-code) since Fri 2024-05-17 09:01:44 PKT; 7min ago
Duration: 286ms
Docs: man:fail2ban(1)
Process: 200860 ExecStartPre=/bin/mkdir -p /run/fail2ban (code=exited, status=0/SUCCESS)
Process: 200862 ExecStartPre=/bin/sh -c umask 077; touch /var/log/fail2ban.log (code=exited, status=0/SUCCESS)
Process: 200864 ExecStart=/usr/bin/fail2ban-server -xf start (code=exited, status=255/EXCEPTION)
Main PID: 200864 (code=exited, status=255/EXCEPTION)
CPU: 222ms

May 17 09:01:44 systemd[1]: Starting fail2ban.service - Fail2Ban Service...
May 17 09:01:44 a systemd[1]: Started fail2ban.service - Fail2Ban Service.
May 17 09:01:44 fail2ban-server[200864]: 2024-05-17 09:01:44,806 fail2ban.configreader [200864]: WARNING 'allowipv6' not defined in 'Definition'. Using default one: 'auto'
May 17 09:01:44 fail2ban-server[200864]: 2024-05-17 09:01:44,902 fail2ban [200864]: ERROR No module named 'asynchat'
May 17 09:01:44 systemd[1]: fail2ban.service: Main process exited, code=exited, status=255/EXCEPTION
May 17 09:01:44 systemd[1]: fail2ban.service: Failed with result 'exit-code'.
 
Back
Top