From 315ff7bd46e6c01dcca34c742786f13910ee68ca Mon Sep 17 00:00:00 2001
From: M2Shawning <38200049+M2Shawning@users.noreply.github.com>
Date: Sat, 27 Apr 2019 14:29:30 -0500
Subject: [PATCH] Add troubleshooting for log file generation

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

diff --git a/Fail2Ban-Setup.md b/Fail2Ban-Setup.md
index 42cdf86..7cb0a44 100644
--- a/Fail2Ban-Setup.md
+++ b/Fail2Ban-Setup.md
@@ -57,6 +57,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.
 
 ## Setting Up Fail2Ban for the Admin Page
 
@@ -83,4 +84,4 @@ logpath = /path/to/bitwarden.log
 maxretry = 5
 bantime = 14400
 findtime = 14400
-```
\ No newline at end of file
+``
\ No newline at end of file