Hello!
I am running Bitwarden on-prem version 2.14.0 and I would like to update to the latest version. After running the update script, I received an error that container nginx cannot start because port 443 is already in use.
Creating bitwarden-nginx ... error
ERROR: for bitwarden-nginx Cannot start service nginx: driver failed programming external connectivity on endpoint bitwarden-nginx (5042f60e9657bead12a493377c2f1800ef0927f7b45db8764c33a27814bea74d): Error starting userland proxy: listen tcp 0.0.0.0:443: bind: address already in use
ERROR: for nginx Cannot start service nginx: driver failed programming external connectivity on endpoint bitwarden-nginx (5042f60e9657bead12a493377c2f1800ef0927f7b45db8764c33a27814bea74d): Error starting userland proxy: listen tcp 0.0.0.0:443: bind: address already in use
ERROR: Encountered errors while bringing up the project.
This Ubuntu 18.04 server only has Bitwarden running on it so after stopping the Bitwarden container and confirming no containers are running using “sudo docker ps”, it seems that Bitwarden is still running somehow.
I know this because I run sudo ./bitwarden.sh stop which reports that Bitwarden is not running but I can still access the Bitwardens login page.
How can Bitwarden be running when the docker containers stop? Running ps aux | grep bitwarden, I received two results but unable to determine how Bitwarden is running:
ps aux | grep bitwarden
nobody 1796 0.3 1.0 16844820 55548 ? SLsl 13:51 0:01 dotnet /bitwarden_server/Server.dll /contentRoot=/app /webRoot=. /serveUnknown=false /webVault=true
nobody 2108 0.2 1.0 16910372 52640 ? SLsl 13:51 0:00 dotnet /bitwarden_server/Server.dll /contentRoot=/etc/bitwarden/core/attachments /webRoot=. /serveUnknow
Does anyone have any ideas?
Thanks
)