mykey/Fail2Ban-Dashboard---NPM
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: note NPM is included, link to NPM site, list ports in quick start

Browse Source
This commit is contained in:
gitea
2026-02-20 20:51:25 +00:00
parent e5fefb152b
commit d05a1e21ab
1 changed files with 7 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
README.md
View File

@@ -1,6 +1,8 @@
# F2B Control Center # F2B Control Center
> Fail2Ban management dashboard for Nginx Proxy Manager — bans scanners, bots, and exploit probers automatically, with a browser UI to monitor and control everything. > Fail2Ban management dashboard for [Nginx Proxy Manager](https://nginxproxymanager.com) — bans scanners, bots, and exploit probers automatically, with a browser UI to monitor and control everything.
**Includes NPM.** The compose file spins up both Nginx Proxy Manager and the F2B dashboard together. See [nginxproxymanager.com](https://nginxproxymanager.com) for how to configure your proxy hosts.
![F2B Control Center — main dashboard](Screenshots/Full%20Ban%20Grid.png) ![F2B Control Center — main dashboard](Screenshots/Full%20Ban%20Grid.png)
@@ -58,7 +60,10 @@ Open `docker-compose.yml` and set `SUBNETS_TO_IGNORE` to your local network rang
docker compose up -d docker compose up -d
``` ```
Dashboard is at `http://YOUR_HOST:4000`. | Service | URL |
|---|---|
| F2B Dashboard | `http://YOUR_HOST:4000` |
| NPM Admin UI | `http://YOUR_HOST:81` |
On first start the container populates a persistent config volume from the bundled defaults and begins monitoring NPM logs immediately. No manual fail2ban setup required. On first start the container populates a persistent config volume from the bundled defaults and begins monitoring NPM logs immediately. No manual fail2ban setup required.