after a week of testing i found the following:
if SSL is disabled on a domain fail2ban works as expected. if SSL is enabled fail2ban won't work anymore.
Looking at the access logs the only difference is the protocoll:
'- 100.100.100.100 - - [08/Apr/2021:14:09:54 +0200] "POST /wp-login.php HTTP/1.1" (will get blocked)
'- 100.100.100.100 - - [08/Apr/2021:14:14:17 +0200] "POST /wp-login.php HTTP/2" (wont get blocked)
looking at the filter set in /etc/fail2ban/filter.d/aaP_test1.reventor.eu_cc.conf i see that that only HTTP/1 is tracked:
[Definition]
failregex = <HOST> -.- .HTTP/1.* .* .*$
ignoreregex =
any bot using HTTP/2 is allowed endless trys in password guessing. i think that's a big safety issue.
how can it be changed to block all protocolls?