BW Unified always trying to generate a new SSL key pair / requiring a fixed name for private key

[accolon]

Steps To Reproduce

0. Provide the required certificate and private key file.
1. Set BW_ENABLE_SSL to "true" in settings.env.
2. Set BW_SSL_KEY to a name other than "ssl.key" (e.g. "private.key" following the BW documentation on "certificate options") in settings.env.
3. Start the server.

Expected Result

BW Unified uses provided cert and key.

Actual Result

BW Unified doesn't find "ssl.key" and tries to generate a key pair, overwriting the provided key file (or failing to do so). The nginx server doesn't start.

It seems that this part in the entrypoint.sh is the problem:

server/docker-unified/entrypoint.sh

Line 51 in 93afa93

if [ "$BW_ENABLE_SSL" == "true" -a ! -f /etc/bitwarden/ssl.key ]; then

It only checks if "ssl.key" doesn't exist, not respecting the BW_SSL_KEY setting.

Screenshots or Videos

No response

Additional Context

No response

Githash Version

n/a

Environment Details

No response

Database Image

No response

Issue-Link

#2480

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[accolon]

I just had some time to build a small dev environment for BW and make sure this can be fixed easily. I created a pull request, see above.

While I tried to follow your guidelines, please bear with me if I did something wrong. I don't use Github that often to contribute things.