Files
Levente PolyakandChristian Heusel 4a6d338c1c fail2ban: go aggressive and maximum resource sparing with nginx-limit-req
This change can be revisited in a later stage, for the time being we
should prefer maximum resource sparing and minimal "time to action".

The error.log only contains abusers anyway as nginx already did the
counting before adding entries to the log. In best case we can relax
this slightly so offenders will first get graceful http deny codes for a
certain time, but right now the priority is to reduce resources,
time-to-action while maximizing bantime to avoid repeating abusers once
a day. Subsequently also raise the bantime to 1 week.
2025-10-13 19:09:13 +02:00

15 lines
227 B
Django/Jinja

#
# {{ansible_managed}}
#
[nginx-limit-req]
enabled = true
filter = nginx-limit-req
logpath = /var/log/nginx/*/error.log
findtime = 1sec
bantime = 1w
maxretry = 1
# Do not fail2ban archweb's rss limit.
ignoreregex = rsslimit