From d73f11c52fa18e0d8d6cd950792598b5ca1cd421 Mon Sep 17 00:00:00 2001
From: Patryk <41372217+patbel-pwr@users.noreply.github.com>
Date: Tue, 6 Oct 2020 14:06:58 +0200
Subject: [PATCH] Add reminder to restart fail2ban after making changes

---
 Fail2Ban-Setup.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/Fail2Ban-Setup.md b/Fail2Ban-Setup.md
index 06ab5c0..ae11264 100644
--- a/Fail2Ban-Setup.md
+++ b/Fail2Ban-Setup.md
@@ -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