[GH-ISSUE #101] Still Using Port 80 When HTTPS Enabled #55

New issue

Closed

opened 2026-03-03 01:24:18 +03:00 by kerem · 3 comments

kerem commented

2026-03-03 01:24:18 +03:00

Owner

Originally created by @adambriand on GitHub (Jul 22, 2018).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/101

First off great project, thank you.

After following the instructions on the "Enabling HTTPS" section on the main page, I noticed in the logs that it is still using port 80 and the "-p 443:443" option would not allow me to connect. When I changed the option to "-p 443:80" it worked fine and I was able to connect to it via port 443.

Originally created by @adambriand on GitHub (Jul 22, 2018). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/101 First off great project, thank you. After following the instructions on the "Enabling HTTPS" section on the main page, I noticed in the logs that it is still using port 80 and the "-p 443:443" option would not allow me to connect. When I changed the option to "-p 443:80" it worked fine and I was able to connect to it via port 443.

kerem

2026-03-03 01:24:18 +03:00

closed this issue
added the
enhancement

documentation
labels

kerem commented

2026-03-03 01:24:20 +03:00

Author

Owner

@mprasil commented on GitHub (Jul 23, 2018):

You can change the port by setting the ROCKET_PORT environment variable.

I'm not sure if we can actually change the port automatically. (can we differentiate between user defined configuration and default setting?) But we should at least document the behavior and suggest changing the port.

@mprasil commented on GitHub (Jul 23, 2018): You can change the port by setting the `ROCKET_PORT` environment variable. I'm not sure if we can actually change the port automatically. (can we differentiate between user defined configuration and default setting?) But we should at least document the behavior and suggest changing the port.

kerem commented

2026-03-03 01:24:20 +03:00

Author

Owner

@adambriand commented on GitHub (Jul 23, 2018):

Confirmed that everything works as expected after I added "-e ROCKET_PORT=443" to the run command in the documentation. Thank you.

@adambriand commented on GitHub (Jul 23, 2018): Confirmed that everything works as expected after I added "-e ROCKET_PORT=443" to the run command in the documentation. Thank you.

kerem commented

2026-03-03 01:24:20 +03:00

Author

Owner

@mannp commented on GitHub (Jul 24, 2018):

It initially confused me getting https working as there is no mention of ROCKET_PORT=443 in this section and so the config doesn't work as it is described.

It also works leaving the port as was 80:8080 (for non root user usage) and telling you proxy the ssl port is 8080.

Enabling HTTPS

docker run -d --name bitwarden
-e ROCKET_TLS={certs='"/ssl/certs.pem",key="/ssl/key.pem"}'
-v /ssl/keys/:/ssl/
-v /bw-data/:/data/
-v /icon_cache/
*-p 443:443 *
mprasil/bitwarden:latest

@mannp commented on GitHub (Jul 24, 2018): It initially confused me getting https working as there is no mention of ROCKET_PORT=443 in this section and so the config doesn't work as it is described. It also works leaving the port as was 80:8080 (for non root user usage) and telling you proxy the ssl port is 8080. > **Enabling HTTPS** > > docker run -d --name bitwarden \ > -e ROCKET_TLS={certs='"/ssl/certs.pem",key="/ssl/key.pem"}' \ > -v /ssl/keys/:/ssl/ \ > -v /bw-data/:/data/ \ > -v /icon_cache/ \ > **-p 443:443 \** > mprasil/bitwarden:latest

kerem referenced this issue

2026-03-03 02:19:56 +03:00

[PR #55] [MERGED] Remove some extra debug prints #2592