Installing self-hosted Bitwarden on server with existing nginx

I want to install Bitwarden on a server that already has a few services running, like Gitea, NextCloud, and a few other services for which I already have running. Also, certbot is already running and issuing LetsEncrypt certs regularly as well.

My question is this: Running the scripts to follow simple Docker install at Install and Deploy | Bitwarden Help & Support , will that interfere with anything, or is there anything I should be looking out for. I don’t want to damage any of the services I already have running.

From what I can see in the instructions, To avoid any conflicts with the ports that Nginx is listening on, I may need to adjust the port numbers as per these instructions at the link above:

Some installation scenarios (e.g. installations behind a proxy with alternate ports) may require adjustments to config.yml that were not provided during standard installation.

Is this correct? Are there instructions for using my existing Nginx daemon using 443 (setting up a Server block to proxy requests to the dockerized Bitwarden services) to service the Bitwarden services?

If all of my existing services, along with Bitwarden, are being handled by Nginx over TCP 443, I won’t need to make any changes to the firewall in front of the server, and certbot can just add the new site in the server block as usual for LetsEncrypt (that’s my thinking, anyway) What are the best practices for what I’m looking to do here?

Hi @tallship did you manage to sort this out?

I am in the same situation… I am changing self-hosted servers at AWS and have moved my Bitwarden first but now need the standalone system wide NginX to be able to host my web sites!

I think you can change the port that Bitwarden will run on - like 8443 - and then I would change the config in my various apps and web browser extensions…

e.g.

https://vault.mydomain.com:8443

Any ideas?