Originally created by @Sleuth56 on GitHub (May 15, 2019).
I got bitwarden up and running without ssl but as soon as I try to enable ssl the container won't even start up.
This is the command I'm using. docker run -d --name bitwarden -e ROCKET_TLS='{certs="/ssl/certs.pem",key="/ssl/key.pem"}' -v /ssl/keys/:/ssl/ -v /bw-data/:/data/ -p 443:80 mprasil/bitwarden:raspberry
I generated the ssl key files and they are in /ssl/keys on the host file system. the files are named the same as in the command. If anyone has a fix I would greatly appreciate it.
Docker version 18.09.0, build 4d60db4
Originally created by @Sleuth56 on GitHub (May 15, 2019).
I got bitwarden up and running without ssl but as soon as I try to enable ssl the container won't even start up.
This is the command I'm using.
`docker run -d --name bitwarden -e ROCKET_TLS='{certs="/ssl/certs.pem",key="/ssl/key.pem"}' -v /ssl/keys/:/ssl/ -v /bw-data/:/data/ -p 443:80 mprasil/bitwarden:raspberry`
I generated the ssl key files and they are in /ssl/keys on the host file system. the files are named the same as in the command. If anyone has a fix I would greatly appreciate it.
`Docker version 18.09.0, build 4d60db4`
I don't know I've never used docker. The reason that I was trying this was I had locked my self out of my bitwarden account with 2fa but I was able to get back in. I will try this again when I have a spare pi again. If I have the same error I can post the logs here if you want? I've already wiped the sdcard that had the logs on it.
It was a really slick install and worked well other than I couldn't get SSL working. Was my command rite?
@Sleuth56 commented on GitHub (May 17, 2019):
I don't know I've never used docker. The reason that I was trying this was I had locked my self out of my bitwarden account with 2fa but I was able to get back in. I will try this again when I have a spare pi again. If I have the same error I can post the logs here if you want? I've already wiped the sdcard that had the logs on it.
It was a really slick install and worked well other than I couldn't get SSL working. Was my command rite?
Your command sounds correct. When you decide to give it another go, you can use docker logs to see log output.
@mprasil commented on GitHub (Jun 3, 2019):
Your command sounds correct. When you decide to give it another go, you can use `docker logs` to see log output.
I'm going to close this, hopefully @lerker100 managed to solve the problem as there's no response. Feel free to reopen if it's still not working.
@mprasil commented on GitHub (Jun 6, 2019):
I'm going to close this, hopefully @lerker100 managed to solve the problem as there's no response. Feel free to reopen if it's still not working.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Sleuth56 on GitHub (May 15, 2019).
I got bitwarden up and running without ssl but as soon as I try to enable ssl the container won't even start up.
This is the command I'm using.
docker run -d --name bitwarden -e ROCKET_TLS='{certs="/ssl/certs.pem",key="/ssl/key.pem"}' -v /ssl/keys/:/ssl/ -v /bw-data/:/data/ -p 443:80 mprasil/bitwarden:raspberryI generated the ssl key files and they are in /ssl/keys on the host file system. the files are named the same as in the command. If anyone has a fix I would greatly appreciate it.
Docker version 18.09.0, build 4d60db4@dani-garcia commented on GitHub (May 17, 2019):
Any errors on the logs?
@Sleuth56 commented on GitHub (May 17, 2019):
I don't know I've never used docker. The reason that I was trying this was I had locked my self out of my bitwarden account with 2fa but I was able to get back in. I will try this again when I have a spare pi again. If I have the same error I can post the logs here if you want? I've already wiped the sdcard that had the logs on it.
It was a really slick install and worked well other than I couldn't get SSL working. Was my command rite?
@mprasil commented on GitHub (Jun 3, 2019):
Your command sounds correct. When you decide to give it another go, you can use
docker logsto see log output.@mprasil commented on GitHub (Jun 6, 2019):
I'm going to close this, hopefully @lerker100 managed to solve the problem as there's no response. Feel free to reopen if it's still not working.