ROCKET_TLS={certs....could not be parsed #1124

Closed
opened 2026-02-04 23:58:17 +03:00 by OVERLORD · 4 comments
Owner

Originally created by @M4st3rITA on GitHub (Oct 2, 2021).

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). <!-- # ### NOTE: Please update to the latest version of vaultwarden before reporting an issue! This saves you and us a lot of time and troubleshooting. See: * https://github.com/dani-garcia/vaultwarden/issues/1180 * https://github.com/dani-garcia/vaultwarden/wiki/Updating-the-vaultwarden-image # ### --> <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them. Remember to hide/redact personal or confidential information, such as passwords, IP addresses, and DNS names as appropriate. --> ### Subject of the issue <!-- Describe your issue here. --> 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 <!-- ========================================================================================= Preferably, use the `Generate Support String` button on the admin page's Diagnostics tab. That will auto-generate most of the info requested in this section. ========================================================================================= --> <!-- The version number, obtained from the logs (at startup) or the admin diagnostics page --> <!-- This is NOT the version number shown on the web vault, which is versioned separately from vaultwarden --> <!-- Remember to check if your issue exists on the latest version first! --> * vaultwarden version: 1.22.2 <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Install method: * Clients used: <!-- web vault, desktop, Android, iOS, etc. (if applicable) --> * Reverse proxy and version: <!-- if applicable --> NGINX Proxy Manager v2.9.9 * MySQL/MariaDB or PostgreSQL version: <!-- if applicable --> * Other relevant details: ### Steps to reproduce <!-- Tell us how to reproduce this issue. What parameters did you set (differently from the defaults) and how did you start vaultwarden? --> 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 <!-- Tell us what you expected to happen --> ### Actual behaviour <!-- Tell us what actually happened --> ### Troubleshooting data <!-- Share any log files, screenshots, or other relevant troubleshooting data -->
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.
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
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
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.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#1124