From fa667e14e23a7ab52c38c8b50e3db63359b6a20d Mon Sep 17 00:00:00 2001
From: GeekCorner <45696571+GeekCornerGH@users.noreply.github.com>
Date: Sun, 22 May 2022 15:56:15 +0200
Subject: [PATCH] Added informations for Cloudflare proxy users

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

diff --git a/Fail2Ban-Setup.md b/Fail2Ban-Setup.md
index 2972a90..3ebadd3 100644
--- a/Fail2Ban-Setup.md
+++ b/Fail2Ban-Setup.md
@@ -161,6 +161,9 @@ Do not use this if you use a reverse proxy before Docker container. If proxy, li
 **NOTE on the NOTE above**:  
 That's 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.
 
+**NOTE FOR CLOUDFLARE USERS**
+If you use cloudflare proxy, you'll need to add Cloudflare in your actions list, like in [this guide](https://niksec.com/using-fail2ban-with-cloudflare/)
+
 Reload fail2ban for changes to take effect:
 
 ```bash
@@ -211,6 +214,8 @@ Note: Docker uses the FORWARD chain instead of the default INPUT chain. Therefor
 ```INI
 action = iptables-allports[name=vaultwarden-admin, chain=FORWARD]
 ```
+**NOTE FOR CLOUDFLARE USERS**
+If you use cloudflare proxy, you'll need to add Cloudflare in your actions list, like in [this guide](https://niksec.com/using-fail2ban-with-cloudflare/)
 
 Reload fail2ban for changes to take effect: