Can't enable HTTPS (error while setting tls.certs) #70

New Issue

OVERLORD · 2026-02-04T16:41:05+03:00

OVERLORD commented

2026-02-04 16:41:05 +03:00

Originally created by @EnriqCG on GitHub (Aug 17, 2018).

Good day. I'm having some issues setting up HTTPS while testing bitwarden_rs on a VM.

I'm running

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

where the certificate + privkey are placed in /home/ubuntu/certs.

The container does not start correctly and when retrieving logs this is the error

Error: I/O error while setting tls.certs:
    => No such file or directory (os error 2)

I've tried several things, including permissions, relative and absolute paths, etc. I don't know what is causing this.

Thanks for your time.

Originally created by @EnriqCG on GitHub (Aug 17, 2018). Good day. I'm having some issues setting up HTTPS while testing bitwarden_rs on a VM. I'm running ``` docker run -d --name bitwarden -e ROCKET_TLS='{certs="/home/ubuntu/certs/certs.pem",key="/home/ubuntu/certs/key.pem"}' -v /home/ubuntu/bitwarden-rs/ssl/:/ssl/ -v /home/ubuntu/bitwarden-rs/bw-data/:/data/ -p 443:80 mprasil/bitwarden:latest ``` where the certificate + privkey are placed in `/home/ubuntu/certs`. The container does not start correctly and when retrieving logs this is the error ``` Error: I/O error while setting tls.certs: => No such file or directory (os error 2) ``` I've tried several things, including permissions, relative and absolute paths, etc. I don't know what is causing this. Thanks for your time.

OVERLORD added the question label 2026-02-04 16:41:05 +03:00

OVERLORD closed this issue

2026-02-04 16:41:09 +03:00

OVERLORD commented

2026-02-04 16:41:14 +03:00

@mprasil commented on GitHub (Aug 17, 2018):

Hi, when you run docker with this parameter:

-v /home/ubuntu/bitwarden-rs/ssl/:/ssl/

You're mapping /home/ubuntu/bitwarden-rs/ssl/ on your server to /ssl/ in the container. The ROCKET_TLS needs to point to the files inside your container, not where they are on the server. (bitwarden_rs obviously can't see files outside the container)

So most likely you just need to set the variable to something like this:

 -e ROCKET_TLS='{certs="/ssl/certs.pem",key="/ssl/key.pem"}'

And make sure the volume mapping is correct. From what you provided, it should be:

-v /home/ubuntu/certs/:/ssl/

(I'm assuming your certs are stored in /home/ubuntu/certs/ directory on your server.)

@mprasil commented on GitHub (Aug 17, 2018): Hi, when you run docker with this parameter: ``` -v /home/ubuntu/bitwarden-rs/ssl/:/ssl/ ``` You're mapping `/home/ubuntu/bitwarden-rs/ssl/` on your server to `/ssl/` in the container. The `ROCKET_TLS` needs to point to the files inside your container, not where they are on the server. (`bitwarden_rs` obviously can't see files outside the container) So most likely you just need to set the variable to something like this: ``` -e ROCKET_TLS='{certs="/ssl/certs.pem",key="/ssl/key.pem"}' ``` And make sure the volume mapping is correct. From what you provided, it should be: ``` -v /home/ubuntu/certs/:/ssl/ ``` (I'm assuming your certs are stored in `/home/ubuntu/certs/` directory on your server.)

OVERLORD commented

2026-02-04 16:41:20 +03:00

@mprasil commented on GitHub (Aug 17, 2018):

@EnriqCG I'm going to close this, feel free to re-open if you still have issues with getting it working.

@mprasil commented on GitHub (Aug 17, 2018): @EnriqCG I'm going to close this, feel free to re-open if you still have issues with getting it working.

OVERLORD referenced this issue

2026-02-05 04:48:33 +03:00

[PR #70] [MERGED] Enable user to change ROCKET_ENV for container #2572

Sign in to join this conversation.