starred/vaultwarden

Fork 0

mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-04-26 01:35:54 +03:00

[GH-ISSUE #1002] SSL: Could not be Parsed #714

New issue

Closed

opened 2026-03-03 02:02:28 +03:00 by kerem · 5 comments

kerem commented

2026-03-03 02:02:28 +03:00

Owner

Originally created by @ASPI259 on GitHub (May 21, 2020).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1002

Hi,

i followed this guide: https://github.com/dani-garcia/bitwarden_rs/wiki/Private-CA-and-self-signed-certs-that-work-with-Chrome
and createt the Certificates in the Dictionary: /var/lib/docker/volumes/ssl
This i passed through to the Container but i cant start the container.
Log shows: .... could not be parsed...

any tips?

Originally created by @ASPI259 on GitHub (May 21, 2020). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1002 Hi, i followed this guide: https://github.com/dani-garcia/bitwarden_rs/wiki/Private-CA-and-self-signed-certs-that-work-with-Chrome and createt the Certificates in the Dictionary: /var/lib/docker/volumes/ssl This i passed through to the Container but i cant start the container. Log shows: .... could not be parsed... any tips?

kerem

2026-03-03 02:02:28 +03:00

closed this issue
added the
better for forum
label

kerem commented

2026-03-03 02:02:29 +03:00

Author

Owner

@ASPI259 commented on GitHub (May 21, 2020):

Exact Log:
Logger failed to initialize: attempted to set a logger after the logging system was already initialized

[2020-05-21 19:35:45][rocket::config::error][ERROR] environment variable ROCKET_TLS={certs="/ssl/bitwarden/bitwarden.crt",key="/ssl/bitwarden/bitwarden.key" could not be parsed

ROCKET_TLS='{certs="/ssl/bitwarden/bitwarden.crt",key="/ssl/bitwarden/bitwarden.key"}'

Volume:

/var/lib/docker/volumes/ssl:/ssl

@ASPI259 commented on GitHub (May 21, 2020): Exact Log: Logger failed to initialize: attempted to set a logger after the logging system was already initialized [2020-05-21 19:35:45][rocket::config::error][ERROR] environment variable ROCKET_TLS={certs="/ssl/bitwarden/bitwarden.crt",key="/ssl/bitwarden/bitwarden.key" could not be parsed ROCKET_TLS='{certs="/ssl/bitwarden/bitwarden.crt",key="/ssl/bitwarden/bitwarden.key"}' Volume: /var/lib/docker/volumes/ssl:/ssl

kerem commented

2026-03-03 02:02:29 +03:00

Author

Owner

@Link009 commented on GitHub (Jun 2, 2020):

Take a look here: https://lucians.dev/solve-bitwardenrs-this-subtle-is-null-error

Is bitwarden.crt formatted corectly ? Also, what are you trying to achieve ? Enable SSL or create a self signed certificate ?

The link I posted is for the first issue.

@Link009 commented on GitHub (Jun 2, 2020): Take a look here: https://lucians.dev/solve-bitwardenrs-this-subtle-is-null-error Is bitwarden.crt formatted corectly ? Also, what are you trying to achieve ? Enable SSL or create a self signed certificate ? The link I posted is for the first issue.

kerem commented

2026-03-03 02:02:29 +03:00

Author

Owner

@drkeni9ma commented on GitHub (Jul 2, 2020):

/var/lib/docker/volumes/ssl

Did you create it in your docker container? If so, I suggest you create your cert and key files in the host machine

host:container

@drkeni9ma commented on GitHub (Jul 2, 2020): > /var/lib/docker/volumes/ssl Did you create it in your docker container? If so, I suggest you create your cert and key files in the host machine <host:container>

kerem commented

2026-03-03 02:02:29 +03:00

Author

Owner

@BlackDex commented on GitHub (Nov 18, 2020):

Closing this ticket because of inactivity.
Feel free to continue this discussion on the forum: https://bitwardenrs.discourse.group/

We suggest to use a reverse-proxy for ssl-offloading, because reverse proxy are better in handling SSL.
Also checkout some of the updated/new wiki articles:
https://github.com/dani-garcia/bitwarden_rs/wiki/Enabling-HTTPS
https://github.com/dani-garcia/bitwarden_rs/wiki/Running-a-private-bitwarden_rs-instance-with-Let%27s-Encrypt-certs
https://github.com/dani-garcia/bitwarden_rs/wiki/Private-CA-and-self-signed-certs-that-work-with-Chrome

@BlackDex commented on GitHub (Nov 18, 2020): Closing this ticket because of inactivity. Feel free to continue this discussion on the forum: https://bitwardenrs.discourse.group/ We suggest to use a reverse-proxy for ssl-offloading, because reverse proxy are better in handling SSL. Also checkout some of the updated/new wiki articles: https://github.com/dani-garcia/bitwarden_rs/wiki/Enabling-HTTPS https://github.com/dani-garcia/bitwarden_rs/wiki/Running-a-private-bitwarden_rs-instance-with-Let%27s-Encrypt-certs https://github.com/dani-garcia/bitwarden_rs/wiki/Private-CA-and-self-signed-certs-that-work-with-Chrome

kerem commented

2026-03-03 02:02:30 +03:00

Author

Owner

@vszakats commented on GitHub (Dec 2, 2020):

Had this error when trying to use an ECC certificate. It's a misleading message as the setting was correctly formatted and the files were in their correct location. Replacing them with RSA keys made the error go away.

Ref: https://github.com/dani-garcia/bitwarden_rs/issues/1205 [Have a plan to support ECC certificates?]

@vszakats commented on GitHub (Dec 2, 2020): Had this error when trying to use an ECC certificate. It's a misleading message as the setting was correctly formatted and the files were in their correct location. Replacing them with RSA keys made the error go away. Ref: https://github.com/dani-garcia/bitwarden_rs/issues/1205 [Have a plan to support ECC certificates?]