fail2ban kept "banning" IPs that kept hammering my Docker ports — the bans were landing in the wrong iptables chain
Spent days wondering why fail2ban kept banning IPs that kept hammering my Docker-published WordPress login. The bans were inserted, "fail2ban-client status" said banned — but the traffic never stopped. The reason: on a Docker host, fail2ban's default action drops rules into the INPUT chain.