roles/common: use pyinotify backend for nginx fail2ban jail
This seems to be automatically selected, but on some other servers I notice it is not. I will set it here explicitly so fail2ban does not fall back to the inefficient "polling" or incorrect "systemd" backends.
This commit is contained in:
parent
68f0b85eb3
commit
0ffb1b1a36
@ -9,6 +9,7 @@ banaction=nftables[type=allports]
|
|||||||
# Integrate with firewalld and ipsets
|
# Integrate with firewalld and ipsets
|
||||||
banaction = firewallcmd-ipset
|
banaction = firewallcmd-ipset
|
||||||
{% endif %}
|
{% endif %}
|
||||||
|
backend = pyinotify
|
||||||
logpath = /var/log/nginx/*-access.log
|
logpath = /var/log/nginx/*-access.log
|
||||||
# Try to find a non-existent wp-login.php once and get banned. Tough luck.
|
# Try to find a non-existent wp-login.php once and get banned. Tough luck.
|
||||||
maxretry = 1
|
maxretry = 1
|
||||||
|
Loading…
Reference in New Issue
Block a user