From ddb23d83d6eb09103cca686c58564b5b628625a6 Mon Sep 17 00:00:00 2001 From: Kofl Date: Sun, 27 Oct 2019 23:20:11 +0100 Subject: [PATCH] chain=FORWARD works fine with reverse proxy --- Fail2Ban-Setup.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Fail2Ban-Setup.md b/Fail2Ban-Setup.md index 1784589..67fd679 100644 --- a/Fail2Ban-Setup.md +++ b/Fail2Ban-Setup.md @@ -63,6 +63,9 @@ action = iptables-allports[name=bitwarden, chain=FORWARD] **NOTE**: Do not use this if you use a reverse proxy before docker container. If proxy, like apache2 or nginx is used, use the ports of the proxy and do not use chain=FORWARD, only when using Docker **without** proxy! +**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. + Feel free to change the options as you see fit. ## Testing Fail2Ban