Mitchell Krog

@fstltna your problem is with this jail you have (below). There is no such jail that comes with Fail2ban by default, if you installed this new jail/filter yourself it's broken....

@fstltna also you don't need to put the ignore IP line in all the jails, only once at the top of your jail.local

Zip your entire fail2ban folder for me and email it to me so I can test it in a VM for you [email protected]

It's late here in South Africa I'll have to look at this in the morning but here's an article of mine worth reading https://ubuntu101.co.za/security/fail2ban/fail2ban-persistent-bans-ubuntu/

Make sure you use a jail.local file and not the main jail.conf for your own configurations my article has lots of info in it read carefully and slowly

Another tip... disable ALL jails and enable them one by one, EACH time starting and stopping the Fail2Ban service... that way you quickly find a jail with a messy configuration.

Awesome well done you are learning fast. Seems I will have some competition from you one day.

Hi @robert1112 yes you should use `logpath = %(apache_error_log)s` if that does not work then your main fail2ban config is not setup properly. Check how your paths have been specified...

No don't change them all to error.log .... some jails require reading an error.log file but 99% of jails require reading an access.log file.

What filter is that and why are you trying to change it from the defaults?