From 2f1c0b31f3d03e9fe51ced6c49b066bf005604f8 Mon Sep 17 00:00:00 2001 From: Jonghee Son Date: Sat, 11 Jun 2022 16:23:46 +0900 Subject: [PATCH] Added instruction for using systemd-journal for fail2ban. --- Fail2Ban-Setup.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/Fail2Ban-Setup.md b/Fail2Ban-Setup.md index 3ebadd3..82f188c 100644 --- a/Fail2Ban-Setup.md +++ b/Fail2Ban-Setup.md @@ -161,6 +161,13 @@ 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. +**Tip**:If you are using systemd to manage vaultwarden, you can use systemd-journal for fail2ban: +``` +backend = systemd +filter = vaultwarden[journalmatch='_SYSTEMD_UNIT=your_vaultwarden.service'] +``` +Use these instead of `logpath = ` variable. + **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/)