Skip to content

Append documentation about fail2ban usage #90

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
fguillot merged 1 commit into from
May 27, 2026
Merged

Append documentation about fail2ban usage #90

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions content/en/v1/admin/security.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,6 +59,32 @@ However, **after three failed authentication attempts via the user API**, the ac

Kanboard does not block IP addresses since bots can use multiple anonymous proxies. However, you can use external tools like [fail2ban](http://www.fail2ban.org) to prevent massive scans.

One can set up a fail2ban filter for kanboard with the following (edit for your needs; check documenation on fail2ban for setting this up):

```
# /etc/fail2ban/filter.d/kanboard.local

[INCLUDES]
before = common.conf

[Definition]
failregex = ^.*Kanboard: user.*authentication failure with IP address: <HOST>$
journalmatch = _COMM=php-fpm
```

```
# /etc/fail2ban/jail.local

...

[kanboard]
enabled = true
ignoreip = 127.0.0.1 ::1
```

Make sure that your php server has set `error_log` to a valid value and that your fail2ban config is reading from the correct logs or no logs will be output on authentication error.
Note that fail2ban depends on log outputs to work properly.

Default settings can be changed using these configuration variables:

```php
Expand Down