Docs: Added instructions for Docker fail2ban configuration. (#8642)

This commit is contained in:
Nathaniel Sabanski 2019-10-23 07:07:32 -07:00 committed by zeripath
parent b4b0e22f5f
commit c2fca23b2c

View file

@ -26,7 +26,7 @@ on a bad authentication:
2018/04/26 18:15:54 [I] Failed authentication attempt for user from xxx.xxx.xxx.xxx 2018/04/26 18:15:54 [I] Failed authentication attempt for user from xxx.xxx.xxx.xxx
``` ```
So we set our filter in `/etc/fail2ban/filter.d/gitea.conf`: Add our filter in `/etc/fail2ban/filter.d/gitea.conf`:
```ini ```ini
# gitea.conf # gitea.conf
@ -35,12 +35,11 @@ failregex = .*Failed authentication attempt for .* from <HOST>
ignoreregex = ignoreregex =
``` ```
And configure it in `/etc/fail2ban/jail.d/jail.local`: Add our jail in `/etc/fail2ban/jail.d/gitea.conf`:
```ini ```ini
[gitea] [gitea]
enabled = true enabled = true
port = http,https
filter = gitea filter = gitea
logpath = /home/git/gitea/log/gitea.log logpath = /home/git/gitea/log/gitea.log
maxretry = 10 maxretry = 10
@ -49,6 +48,23 @@ bantime = 900
action = iptables-allports action = iptables-allports
``` ```
If you're using Docker, you'll also need to add an additional jail to handle the **FORWARD**
chain in **iptables**. Configure it in `/etc/fail2ban/jail.d/gitea-docker.conf`:
```ini
[gitea-docker]
enabled = true
filter = gitea
logpath = /home/git/gitea/log/gitea.log
maxretry = 10
findtime = 3600
bantime = 900
action = iptables-allports[chain="FORWARD"]
```
Then simply run `service fail2ban restart` to apply your changes. You can check to see if
fail2ban has accepted your configuration using `service fail2ban status`.
Make sure and read up on fail2ban and configure it to your needs, this bans someone Make sure and read up on fail2ban and configure it to your needs, this bans someone
for **15 minutes** (from all ports) when they fail authentication 10 times in an hour. for **15 minutes** (from all ports) when they fail authentication 10 times in an hour.