Vaultwarden's IP_HEADER env var is inconsistent

[asardaes]

Likely for historical reasons, the environment for Vaultwarden specifies a custom IP_HEADER env var:

bitwarden_gcloud/docker-compose.yml

Line 29 in 552257c

- IP_HEADER=X-Forwarded-For

However, this setup uses Caddy as the reverse proxy, and that's configured to set the real IP in X-Real-IP:

bitwarden_gcloud/caddy/Caddyfile

Line 35 in 395333e

header_up X-Real-IP {remote_host}

So the Compose YAML needs to be adjusted.

[dadatuputi]

Looks like vaultwarden changed that at some time, currently it is set to X-Real-IP (https://github.com/dani-garcia/vaultwarden/blob/efc6eb0073d9740a3bf2dc99e8fe5afd50a2e4e3/.env.template#L61)