This is due to a change in Ubuntu 22.04 and not related to ISPConfig or manual vs. auto-install. That's why you did not have this issue on Ubuntu 20.04. You can find this in our issue tracker here: https://git.ispconfig.org/ispconfig/ispconfig-autoinstaller/-/issues/114
ok, what I did to resolve this problem seems to be a onetime- command at the end (5 minutes ago): systemctl disable fail2ban systemctl enable fail2ban After a reboot, it looks like fail2ban is starting now as it should, "fail2ban-client status" is working without having to "start" it anymore.
I installed the Ubuntu minimum 22.04.3 LTS. All the options given here didn't work for me. I had no fail2ban working and also no logs from Postfix under the Monitoring. To solve it I did this: apt install inetutils-syslogd Then reboot and after that systemctl enable fail2ban It did not start because it couldn't read the logs (the mail log was not there), which was solved by installing inetutils-syslogd, after that rebooted start fail2ban. All logs are working now. Maybe this helps for others. I reproduced it, because i had made a snapshot during the install steps.
