- Image based on crazymax/fail2ban:1.1.1 with inotify-tools - Filters npm-scanner and npm-wplogin, tested with fail2ban-regex in the build - jail.local generated from .env, optional npm-wplogin and recidive - Watcher reloads the jails when NPM creates a new proxy host log - check command, docs, testbed for LXC Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
737 B
737 B
Changelog
All notable changes are listed here. Versions follow Semantic Versioning.
[Unreleased] – 0.1.0
First version, generalised from a host-installed fail2ban setup.
- Image based on
crazymax/fail2ban:1.1.1, addsinotify-tools - Filters
npm-scannerandnpm-wplogin, tested withfail2ban-regexduring the image build jail.localgenerated from.envat every start (whitelist, chain, retries, ban times)- Optional jails
npm-wploginandrecidive - Watcher reloads the jails when NPM creates a new proxy host log
- Second log directory for
jlesage/nginx-proxy-manager; the same directory is never read twice checkcommand: writes the configuration and runsfail2ban-client -t