From aaff4f7e74dea8cbf22ae946afc2cd20146955eb Mon Sep 17 00:00:00 2001
From: jonathanmmm <32403139+jonathanmmm@users.noreply.github.com>
Date: Fri, 3 May 2019 10:34:00 +0200
Subject: [PATCH] Add some explenation to log file path and that extended
 logging is default

---
 Fail2Ban-Setup.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Fail2Ban-Setup.md b/Fail2Ban-Setup.md
index a64ac77..105ed21 100644
--- a/Fail2Ban-Setup.md
+++ b/Fail2Ban-Setup.md
@@ -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