sdgoij/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-01-16 20:50:33 +00:00
Code Issues Packages Projects Releases Wiki Activity

Clarified that changing Client IP header in admin panel could yield wrong results if using a proxy that's set up to configure which headers to use to determine the client's IP address.

tsanga13
2025-08-04 00:28:12 -05:00
parent 66553ab45e
commit 88c376a521
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
Fail2Ban-Setup.md

@@ -130,7 +130,7 @@ ignoreregex =
`fail2ban.filter [5291]: ERROR No 'host' group in '^.*Username or password is incorrect\. Try again\. IP: <ADDR>\. Username:.*$'`
Please Use `<HOST>` instead of `<ADDR>` in `vaultwarden.local`
**Tip:** Cloudflare users, make sure you set your Client IP header to `CF-Connecting-IP` in admin panel -> advanced settings -> Client IP header, else the clients real IP will not be logged/banned. Not necessary if you're using a proxy that's set up to configure which headers to use to determine the client's IP address; otherwise logging the Docker network address when traffic doesn't come from Cloudflare.
**Tip:** Cloudflare users, make sure you set your Client IP header to `CF-Connecting-IP` in admin panel -> advanced settings -> Client IP header, else the clients real IP will not be logged/banned. Not necessary if you're using a proxy that's set up to configure which headers to use to determine the client's IP address; otherwise logging the Docker network address when CF-Connecting-IP doesn't exist.
**Tip:** If you see 127.0.0.1 as the IP address of failed logins in vaultwarden.log, then you're probably using a reverse proxy and fail2ban won't work correctly: