We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Add Note for Synology DSM Docker Users
Add fix for Docker deployments with Fail2Ban v1.1.1.dev1
Fix filter vulnerability against potential username DoS injection
Noticed that which iptables-common.local, fail2ban tried to REJECT instead of DROP. Change is also present in sosandroid's repo, see issue #6.
Updated Fail2Ban Setup (markdown)
Add note for cloudflare tunnels users to ensure Client Ip header is set correctly
Correct the action resolution in the note for Docker users
Remove conflicting notes on `chain` for Docker setups
Added instruction for using systemd-journal for fail2ban.
Added informations for Cloudflare proxy users
fix typo
Replaced bitwarden with vaultwarden
Changed bw-data to vw-data according to the README
Project renaming
Update the documentation to accomodate for HOST instead of ADDR value
Fix filter name on the action associated to bitwarden_rs-admin filter
Match filter.d with jail.d naming convention
Better indentation and fixed code blocks
Raspbian changed name to Raspberry Pi OS & typos/formatting
Use your default/configured banaction_allports. Name is set automatically
Do not conflict with Bitwarden jail added upstream https://github.com/fail2ban/fail2ban/pull/2567/files
Add reminder to restart fail2ban after making changes
Add a tip about using a reverse proxy with fail2ban
fixed typo
Adding link to docker compose file for Synology
Adding TOC
admin jail - findtime missing