Dashboard

Port is set via PORT environment variable: . To change the port via Web UI, remove the PORT environment variable and restart the container.

⚠️ Port changes require a container restart to take effect.

This URL is used by all Fail2Ban instances to send ban alerts back to Fail2Ban UI. For local deployments, use the same port as Fail2Ban UI (e.g., http://127.0.0.1:8080). For reverse proxy setups, use your TLS-encrypted endpoint (e.g., https://fail2ban.example.com).

This secret is automatically generated and used to authenticate ban notification requests. It is included in the fail2ban action configuration.

Choose the GeoIP lookup provider. MaxMind requires a local database file, while Built-in uses a free online API.

Path to the MaxMind GeoLite2-Country database file.

Maximum number of log lines to include in ban notifications. Most relevant lines are selected automatically.

Choose the countries for which you want to receive email alerts when a block is triggered.

If set to true, the bantime will be calculated using the formula: bantime = findtime * (number of failures / maxretry) * (1 + bantime.rndtime).

If enabled, all jails will be enabled by default. When disabled, jails must be explicitly enabled.

The number of seconds that a host is banned. Time format: 1h = 1 hour, 1d = 1 day, 1w = 1 week, 1m = 1 month, 1y = 1 year.

Default banning action (e.g. iptables-multiport, iptables-allports, firewallcmd-multiport, etc). It is used to define action_* variables.

Banning action for all ports (e.g. iptables-allports, firewallcmd-allports, etc). Used when a jail needs to ban all ports instead of specific ones.

A host is banned if it has generated 'maxretry' failures during the last 'findtime' seconds. Time format: 1h = 1 hour, 1d = 1 day, 1w = 1 week, 1m = 1 month, 1y = 1 year.

Number of failures before a host gets banned.

Space separated list of IP addresses, CIDR masks or DNS hosts. Fail2ban will not ban a host which matches an address in this list.