In order to expose Vaultwarden behind a subpath the DOMAIN variable must be updated to match the new path. Exposing this option would allow those behind proxies to setup Vaultwarden on a single domain name.
Expected behavior
It is expected to be able to host Vaultwarden behind a subpath through reverse proxies (see Vaultwarden's Proxy examples).
Actual behavior
There is no variable to change the base URL, so the configuration can never be setup to properly test.
Steps to reproduce
Attempt to route your Vaultwarden traffic to a subpath on a Tailscale funnel domain name through the Nginx Proxy Manager add-on.
Proposed changes
Provide an option to either set DOMAIN manually, or add an optional subpath to DOMAIN, in the configuration options.
I just want to end this by saying thanks a ton for all the hard work!
Problem/Motivation
In order to expose Vaultwarden behind a subpath the
DOMAIN
variable must be updated to match the new path. Exposing this option would allow those behind proxies to setup Vaultwarden on a single domain name.Expected behavior
It is expected to be able to host Vaultwarden behind a subpath through reverse proxies (see Vaultwarden's Proxy examples).
Actual behavior
There is no variable to change the base URL, so the configuration can never be setup to properly test.
Steps to reproduce
Attempt to route your Vaultwarden traffic to a subpath on a Tailscale funnel domain name through the Nginx Proxy Manager add-on.
Proposed changes
Provide an option to either set
DOMAIN
manually, or add an optional subpath toDOMAIN
, in the configuration options.I just want to end this by saying thanks a ton for all the hard work!