bitwarden
Instructions unclear how to install bitwarden behind a existing reverse proxy
Describe the Bug
Instructions unclear how to install bitwarden behind a existing reverse proxy
Steps To Reproduce
Read manual install
Expected Result
it would be clear how to set up the bitwarden behind a reverse proxy
Actual Result
step 6 and 10 are unclear. These steps could be optional or elaborated.
Many users have their own reverse proxy such as nginx and just like to have a simple instance running under a specific port. The steps are rather unclear why they are done and what can be omitted behind a reverse proxy.
This seems to be a very common use case but there is no clear explanation how this can be achieved.
If you are running both, the reverse proxy as well as bitwarden on the same server, you can just disable TLS for Bitwarden and implement it on the reverse proxy.
Check your config.yml for https_port:, ssl: false, and ssl_managed_lets_encrypt: false.
@fschillingeriv - is this something our docs should cover in more detail, or is it out of scope?
I recently installed Bitwarden on a new server and have the process fresh in my head. It took me a while to figure out the best way to install with nginx as reverse proxy. Specifically, I think the documentation should include the 'correct' answers for the install script questions if you plan to set up nginx and manage your own certs via certbot after the BW set up is completed (so, no to TLS certificates, no to providing the path to certificates). I also ran into an issue where my URI had been set to http:// instead of https://, and I hadn't noticed, which caused problems until I figured it out, so maybe the default URI set in global.override.env should always be https:// or alternatively a message presented to the user during installation, in the same place where it shows the message that says BW will not work properly without TLS.
Moving this to our help repo as this primarily seems to be about documentation.