Add some explenation to log file path and that extended logging is default
parent
58df24afa6
commit
aaff4f7e74
|
@ -62,7 +62,7 @@ If it works correctly and your IP is banned, you can unban the ip by running:
|
|||
```
|
||||
sudo fail2ban-client set bitwarden unbanip XX.XX.XX.XX
|
||||
```
|
||||
If Fail2Ban does not appear to be functioning, verify that the path to the Bitwarden log file is correct. For Docker: If the specified log file is not being generated and/or updated, make sure the `EXTENDED_LOGGING` env variable is set to true.
|
||||
If Fail2Ban does not appear to be functioning, verify that the path to the Bitwarden log file is correct. For Docker: If the specified log file is not being generated and/or updated, make sure the `EXTENDED_LOGGING` env variable is set to true (which is default) and that the path to the log file is the path inside the docker (when you use /bw-data/:/data/ the log file should be in /data/... to be outside the container).
|
||||
|
||||
## Setting Up Fail2Ban for the Admin Page
|
||||
|
||||
|
|
Loading…
Reference in New Issue