Fail2Ban not starting after auto "security" updates


You will have to now fix the jail for apache-api that neither has a log file to watch, as defined in your `/etc/fail2ban/filter.d/apache-api’ file, you can similarly ‘touch’ it for a work around, this also needs to be a bug that you report

Understand that at this point you are not protected by either of those ‘jails’

(I believe that current versions of fail2ban will not outright fail for a mis-configured jail)


Thanks for the info, I will try the touch workaround in a few moments.
I didn’t leave the system running without the firewall, it was shutdown.


This is what fixed it for me:

Found it on:


This fixed the same issue for me, thanks Chris.