mirror of
https://github.com/dani-garcia/vaultwarden
synced 2024-09-28 21:48:57 +02:00
Add reminder to restart fail2ban after making changes
parent
ad2e0e8af6
commit
d73f11c52f
1 changed files with 7 additions and 0 deletions
|
@ -163,6 +163,10 @@ Do not use this if you use a reverse proxy before docker container. If proxy, li
|
|||
**NOTE on the NOTE above**:
|
||||
Thats at least not true for running on Docker (CentOS 7) with caddy as reverse proxy. chain=FORWARD is absolutely fine and working with caddy as reverse proxy.
|
||||
|
||||
You need to restart fail2ban for changes to take effect:
|
||||
|
||||
`sudo systemctl restart fail2ban`
|
||||
|
||||
Feel free to change the options as you see fit.
|
||||
|
||||
|
||||
|
@ -204,6 +208,9 @@ Note: Docker uses the FORWARD chain instead of the default INPUT chain. Therefor
|
|||
```
|
||||
action = iptables-allports[name=bitwarden, chain=FORWARD]
|
||||
```
|
||||
You need to restart fail2ban for changes to take effect:
|
||||
|
||||
`sudo systemctl restart fail2ban`
|
||||
|
||||
## Testing Fail2Ban
|
||||
|
||||
|
|
Loading…
Reference in a new issue