Help installing bitwardenrs docker on Plesk

I am hitting a problem setting up bitwardenrs in a docker in my Plesk account. I have downloaded the latest bitwardenrs/server dicker image and hit the same issue when trying to install it using wither the Plesk GUI interface or from the command line.

The command line I am using is:

docker run -d --name bitwardenrs -v /bwdata:/data -p 49208:80 -p 49209:3012 bitwardenrs/server:latest

The bwdata directory gets populated with an icon_cache directory, plus the SQLite db file 2 .der and one .pem file, but the install seems to hang when I check the console. I’ve pasted the output below. Am I missing anything from the docker config?

/--------------------------------------------------------------------\
|                       Starting Bitwarden_RS                        |
|                           Version 1.19.0                           |
|--------------------------------------------------------------------|
| This is an *unofficial* Bitwarden implementation, DO NOT use the   |
| official channels to report bugs/features, regardless of client.   |
| Send usage/configuration questions or feature requests to:         |
|                           |
| Report suspected bugs/issues in the software itself at:            |
|         |
\--------------------------------------------------------------------/

[INFO] No .env file found.

[2021-02-16 20:16:37.837][bitwarden_rs][INFO] JWT keys don't exist, checking if OpenSSL is available...
OpenSSL 1.1.1d  10 Sep 2019
[2021-02-16 20:16:37.842][bitwarden_rs][INFO] OpenSSL detected, creating keys...
[2021-02-16 20:16:37.921][bitwarden_rs][INFO] Keys created correctly.
Running migration 20180114171611
Running migration 20180217205753
Running migration 20180427155151
Running migration 20180508161616
Running migration 20180525232323
Running migration 20180601112529
Running migration 20180711181453
Running migration 20180827172114
Running migration 20180910111213
Running migration 20180919144557
Running migration 20181127152651
Running migration 20190526216651
Running migration 20191010083032
Running migration 20191117011009
Running migration 20200313205045
Running migration 20200409235005
Running migration 20200701214531
Running migration 20200802025025
Running migration 20201130224000
Running migration 20201209173101
[2021-02-16 20:16:38.010][start][INFO] Rocket has launched from http://0.0.0.0:80
Generating RSA private key, 2048 bit long modulus (2 primes)
..............+++++
.............................+++++
e is 65537 (0x010001)
writing RSA key
writing RSA key

Same problem here…

Mine eventually started working when I added an extra parameter to define the location of a log file (which I did to try and work out why it was stalling!)

Where? Container configuration?

Yes, container config. I added an environment variable called “LOG_FILE” with a value of “/bwdata/bitwarden_rs.log”

1 Like

I also added a Docker Proxy Rule to the subdomain I created to access the BitWarden admin portal targeted at the port mapped to port 80 in the Docker config.

It works! Thank you very much for your help.

1 Like