[GH-ISSUE #2016] ROCKET_TLS={certs....could not be parsed #1128

New issue

Closed

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

kerem commented

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

Owner

Originally created by @M4st3rITA on GitHub (Oct 2, 2021).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2016

Subject of the issue

since yesterday, it is no longer possible to use externally created SSL certificates; the rest of the server is unaffected; I am using NGINX Proxy Manager

Deployment environment

vaultwarden version:
1.22.2

Install method:
Clients used:
Reverse proxy and version:
NGINX Proxy Manager v2.9.9
MySQL/MariaDB or PostgreSQL version:
Other relevant details:

Steps to reproduce

after starting up the docker, as usual, Vaultwarden is not reachable and a 502 bad gateway error is returned; the docker log reads as follows:
[2021-10-02 07:26:17.075][rocket::config::error][ERROR] environment variable ROCKET_TLS={certs="/ssl/npm-8/fullchain.pem",key="/ssl/npm-8/privkey.pem"} could not be parsed

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

Expected behaviour

Actual behaviour

Troubleshooting data

Originally created by @M4st3rITA on GitHub (Oct 2, 2021). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2016   ### Subject of the issue  since yesterday, it is no longer possible to use externally created SSL certificates; the rest of the server is unaffected; I am using NGINX Proxy Manager ### Deployment environment     * vaultwarden version: 1.22.2  * Install method: * Clients used:  * Reverse proxy and version:  NGINX Proxy Manager v2.9.9 * MySQL/MariaDB or PostgreSQL version:  * Other relevant details: ### Steps to reproduce  after starting up the docker, as usual, Vaultwarden is not reachable and a 502 bad gateway error is returned; the docker log reads as follows: [2021-10-02 07:26:17.075][rocket::config::error][ERROR] environment variable ROCKET_TLS={certs="/ssl/npm-8/fullchain.pem",key="/ssl/npm-8/privkey.pem"} could not be parsed Logger failed to initialize: attempted to set a logger after the logging system was already initialized ### Expected behaviour  ### Actual behaviour  ### Troubleshooting data

kerem closed this issue

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

kerem commented

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

Author

Owner

@M4st3rITA commented on GitHub (Oct 2, 2021):

Compared to the past few days, nothing has been changed, no settings, no variables.

@M4st3rITA commented on GitHub (Oct 2, 2021): Compared to the past few days, nothing has been changed, no settings, no variables.

kerem commented

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

Author

Owner

@BlackDex commented on GitHub (Oct 2, 2021):

Is this cert a Lets Encrypt cert?
If so, it could have something to do with this: https://letsencrypt.org/2021/10/01/cert-chaining-help.html

@BlackDex commented on GitHub (Oct 2, 2021): Is this cert a Lets Encrypt cert? If so, it could have something to do with this: https://letsencrypt.org/2021/10/01/cert-chaining-help.html

kerem commented

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

Author

Owner

@M4st3rITA commented on GitHub (Oct 2, 2021):

Yes, definitely...I'm using Let's Encrypt certs.
How can I resolve this...?
I already tried to use the HTTP version of Vaultwarden without success because of the security policy of the browser

@M4st3rITA commented on GitHub (Oct 2, 2021): Yes, definitely...I'm using Let's Encrypt certs. How can I resolve this...? I already tried to use the HTTP version of Vaultwarden without success because of the security policy of the browser

kerem commented

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

Author

Owner

@BlackDex commented on GitHub (Oct 2, 2021):

Well if you use a reverse proxy, you could just have the reverse pricy offload the ssl. That might work.

Else i think you are using the Alpine image, you might want to switch to the Debian image.

@BlackDex commented on GitHub (Oct 2, 2021): Well if you use a reverse proxy, you could just have the reverse pricy offload the ssl. That might work. Else i think you are using the Alpine image, you might want to switch to the Debian image.