From 75aea9196243cc87c3f6ddb348b0c4a01f196d0f Mon Sep 17 00:00:00 2001 From: "Simon L." Date: Sun, 27 Apr 2025 19:50:59 +0200 Subject: [PATCH] fail2ban-cc: add example how to unban a specific ip-address Signed-off-by: Simon L. --- community-containers/fail2ban/readme.md | 1 + 1 file changed, 1 insertion(+) diff --git a/community-containers/fail2ban/readme.md b/community-containers/fail2ban/readme.md index 851cb03c..cb78639c 100644 --- a/community-containers/fail2ban/readme.md +++ b/community-containers/fail2ban/readme.md @@ -4,6 +4,7 @@ This container bundles fail2ban and auto-configures it for you in order to block ### Notes - If you get an error like `"ip6tables v1.8.9 (legacy): can't initialize ip6tables table filter': Table does not exist (do you need to insmod?)"`, you need to enable ip6tables on your host via `sudo modprobe ip6table_filter`. - If you get an error like `stderr: 'iptables: No chain/target/match by that name.'` and `stderr: 'ip6tables: No chain/target/match by that name.'`, you need to follow https://github.com/szaimen/aio-fail2ban/issues/9#issuecomment-2026898790 in order to resolve this. +- You can unban ip addresses like so for example: `docker exec -it nextcloud-aio-fail2ban fail2ban-client set nextcloud unbanip 203.113.167.162`. - See https://github.com/nextcloud/all-in-one/tree/main/community-containers#community-containers how to add it to the AIO stack ### Repository