From cd9239862a0e1bbd270c95d94fc7a1906272aa16 Mon Sep 17 00:00:00 2001 From: Mathijs van Veluw Date: Mon, 21 Jun 2021 21:10:01 +0200 Subject: [PATCH] Updated FAQs (markdown) --- FAQs.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/FAQs.md b/FAQs.md index 0e1a123..d9a6483 100644 --- a/FAQs.md +++ b/FAQs.md @@ -50,6 +50,12 @@ If that does work, there could also be a firewall or Outgoing Internet Proxy whi

+## Websocket connections show wrong IP address +This is not something we can fix on our side. The library we use doesn't support any form of `X-Forwarded-For` or `Forward` headers. +It will always show the IP of the reverse proxy used unless you run vaultwarden directly without any proxy, or run a transparent proxy, that could cause it to do show the correct IP. It is not an important part to log, and if you use a reverse proxy you can probably also see this request in its logs which will have the correct IP. +
+
+ ## Can i run Vaultwarden as an Azure WebApp Unfortunately Azure WebApp's uses CIFS/Samba as there volume storage which does not support locking. This causes issues with the SQLite database file. There are two ways to solve this.