[GH-ISSUE #6706] Rocket cannot find SSL file, even if it exist #2516

New issue

Closed

opened 2026-03-03 02:19:08 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 02:19:08 +03:00

Owner

Originally created by @Guarmanda on GitHub (Jan 13, 2026).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6706

Prerequisites

I have searched the existing Closed AND Open Issues AND Discussions
I have searched and read the documentation

Vaultwarden Support String

I cannot launch vaultwarden because of this, so I cannot generate support string for now.

Vaultwarden Build Version

1.35.2

Deployment method

Official Container Image

Reverse Proxy

nginx, but not working for now due to this issue

Host/Server Operating System, Operating System Version

Linux, Debian 13

Steps To Reproduce

Here is my docker composer file:


services:
  vaultwarden:
    image: vaultwarden/server:latest
    container_name: vaultwarden
    restart: always
    environment:
      # DOMAIN: "https://vaultwarden.example.com"  # required when using a reverse proxy; your domain; vaultwarden needs to know it's https to work properly >
      SIGNUPS_ALLOWED: "true" # Deactivate this with "false" after you have created your account so that no strangers can register
      PUSH_ENABLED: "true"
      PUSH_INSTALLATION_ID: "well..."
      PUSH_INSTALLATION_KEY: "well..."
      ADMIN_TOKEN: "well..."
      ROCKET_ADDRESS: "0.0.0.0"
      ROCKET_TLS: '{certs="/ssl/fullchain.pem",key="/ssl/privkey.pem"}'
      ROCKET_PORT: "443"
      LOG_FILE: "/data/log.txt"
    volumes:
      - /opt/bitwarden/vaultwarden-data:/data # the path before the : can be changed
      - /etc/letsencrypt/live/monptitserveur.uk:/ssl
    ports:
      - 317:443# you can replace the 11001 with your preferred port
    extra_hosts:
      - "host.docker.internal:host-gateway"

So, the certificates are both located here:

and here

Expected Result

SSL certs files should be correctly detected by rocket, and no error logs are showing

Actual Result

whatever how I configure cert path, I got this:

vaultwarden  | Error: Rocket.
vaultwarden  | [CAUSE] Io(
vaultwarden  |     Custom {
vaultwarden  |         kind: NotFound,
vaultwarden  |         error: "error reading TLS file `ssl/fullchain.pem`: No such file or directory (os error 2)",
vaultwarden  |     },
vaultwarden  | )

or this (I tried path outside docker just to see if it was the issue)


vaultwarden  | Error: Rocket.
vaultwarden  | [CAUSE] Io(
vaultwarden  |     Custom {
vaultwarden  |         kind: NotFound,
vaultwarden  |         error: "error reading TLS file `etc/letsencrypt/live/monptitserveur.uk/fullchain.pem`: No such file or directory (os error 2)",
vaultwarden  |     },
vaultwarden  | )

Rocket cannot detect my cert files but the log file is correctly created (but it stays empty)

Logs

Log file is created but stays empty. Some logs from console are shown above.

Screenshots or Videos

No response

Additional Context

No response

Originally created by @Guarmanda on GitHub (Jan 13, 2026). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6706 ### Prerequisites - [x] I have searched the existing **Closed _AND_ Open** [Issues](https://github.com/dani-garcia/vaultwarden/issues?q=is%3Aissue%20) **_AND_** [Discussions](https://github.com/dani-garcia/vaultwarden/discussions?discussions_q=) - [x] I have searched and read the [documentation](https://github.com/dani-garcia/vaultwarden/wiki/) ### Vaultwarden Support String I cannot launch vaultwarden because of this, so I cannot generate support string for now. ### Vaultwarden Build Version 1.35.2 ### Deployment method Official Container Image ### Reverse Proxy nginx, but not working for now due to this issue ### Host/Server Operating System, Operating System Version Linux, Debian 13 ### Steps To Reproduce Here is my docker composer file: ```YAML services: vaultwarden: image: vaultwarden/server:latest container_name: vaultwarden restart: always environment: # DOMAIN: "https://vaultwarden.example.com" # required when using a reverse proxy; your domain; vaultwarden needs to know it's https to work properly > SIGNUPS_ALLOWED: "true" # Deactivate this with "false" after you have created your account so that no strangers can register PUSH_ENABLED: "true" PUSH_INSTALLATION_ID: "well..." PUSH_INSTALLATION_KEY: "well..." ADMIN_TOKEN: "well..." ROCKET_ADDRESS: "0.0.0.0" ROCKET_TLS: '{certs="/ssl/fullchain.pem",key="/ssl/privkey.pem"}' ROCKET_PORT: "443" LOG_FILE: "/data/log.txt" volumes: - /opt/bitwarden/vaultwarden-data:/data # the path before the : can be changed - /etc/letsencrypt/live/monptitserveur.uk:/ssl ports: - 317:443# you can replace the 11001 with your preferred port extra_hosts: - "host.docker.internal:host-gateway" ``` So, the certificates are both located here: <img width="987" height="53" alt="Image" src="https://github.com/user-attachments/assets/e7cfd805-7597-46c1-96f7-b1cf2d61c952" /> and here <img width="666" height="50" alt="Image" src="https://github.com/user-attachments/assets/78202606-d9b6-4cfa-a5c7-9bc3f5a4d222" /> ### Expected Result SSL certs files should be correctly detected by rocket, and no error logs are showing ### Actual Result whatever how I configure cert path, I got this: ``` vaultwarden | Error: Rocket. vaultwarden | [CAUSE] Io( vaultwarden | Custom { vaultwarden | kind: NotFound, vaultwarden | error: "error reading TLS file `ssl/fullchain.pem`: No such file or directory (os error 2)", vaultwarden | }, vaultwarden | ) ``` or this (I tried path outside docker just to see if it was the issue) ``` vaultwarden | Error: Rocket. vaultwarden | [CAUSE] Io( vaultwarden | Custom { vaultwarden | kind: NotFound, vaultwarden | error: "error reading TLS file `etc/letsencrypt/live/monptitserveur.uk/fullchain.pem`: No such file or directory (os error 2)", vaultwarden | }, vaultwarden | ) ``` Rocket cannot detect my cert files but the log file is correctly created (but it stays empty) ### Logs ```text Log file is created but stays empty. Some logs from console are shown above. ``` ### Screenshots or Videos _No response_ ### Additional Context _No response_