[GH-ISSUE #4294] After upgrading to version 1.30.2, the container does not start - unhealthy #1842

New issue

Closed

opened 2026-03-03 02:12:40 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 02:12:40 +03:00

Owner

Originally created by @fullcavediver on GitHub (Jan 31, 2024).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/4294

Hi,

my Vaultwarden runs behind Trafik 2.24.1 and is updated daily using wathtower. Unfortunately the upgrade didn't work today. Luckily I was able to switch back to version 1.30.1 and everything worked again.

What has changed so massively in the two versions?

I was able to find the following entries in the log file:

[2024-01-31 00:08:46.331][vaultwarden::api::web::_][WARN] Parameter guard `p: PathBuf` is forwarding: BadStart('.').
[2024-01-31 00:09:06.304][vaultwarden::api::web::_][WARN] Parameter guard `p: PathBuf` is forwarding: BadStart('.').
[2024-01-31 00:09:37.162][vaultwarden::api::web::_][WARN] Parameter guard `p: PathBuf` is forwarding: BadStart('.').
[2024-01-31 00:10:13.913][request][INFO] GET /admin/.env
[2024-01-31 00:10:13.913][vaultwarden::api::web::_][WARN] Parameter guard `p: PathBuf` is forwarding: BadStart('.').
[2024-01-31 00:10:13.914][response][INFO] (web_files) GET /<p..> [10] => 422 Unprocessable Entity
[2024-01-31 00:10:38.698][vaultwarden::api::web::_][WARN] Parameter guard `p: PathBuf` is forwarding: BadStart('.').
[2024-01-31 04:11:01.664][rocket::server][WARN] Received SIGTERM. Requesting shutdown.
[2024-01-31 04:11:01.669][vaultwarden][INFO] Vaultwarden process exited!
[2024-01-31 04:11:05.442][start][INFO] Rocket has launched from http://0.0.0.0:80

The compose file is also very simple:

version: '3'

services:
  vaultwarden:
    image: vaultwarden/server:1.30.1
    container_name: vaultwarden
    hostname: vaultwarden
    restart: unless-stopped
    volumes:
      - /vaultwarden:/data
      - /vaultwarden/.env:/.env
    environment:
      - LOG_FILE=/data/bitwarden.log
      - LOG_LEVEL=info
      - EXTENDED_LOGGING=true
    labels:
      - "traefik.enable=true"
      - "traefik.http.middlewares.vaultwarden-https.redirectscheme.scheme=https"
      - "traefik.http.routers.vaultwarden-http.entrypoints=web"
      - "traefik.http.routers.vaultwarden-http.rule=Host(`domain-1`) || Host(`domain-2`)"
      - "traefik.http.routers.vaultwarden-http.middlewares=vaultwarden-https@docker"
      - "traefik.http.routers.vaultwarden.entrypoints=web-secure"
      - "traefik.http.routers.vaultwarden.rule=Host(`domain-1`) || Host(`domain-2`)"
      - "traefik.http.routers.vaultwarden.tls=true"
      - "traefik.http.routers.vaultwarden.tls.certresolver=default"
      - "traefik.http.routers.vaultwarden.middlewares=secHeaders@file"
      - "traefik.http.services.vaultwarden.loadbalancer.server.port=80"
    networks:
      - traefik_proxy
      - default
networks:
  traefik_proxy:
    name: traefik_proxy
    external: true
  default:
    driver: bridge

Please help me find the error. Thank you very much!

Originally created by @fullcavediver on GitHub (Jan 31, 2024). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/4294 Hi, my Vaultwarden runs behind Trafik 2.24.1 and is updated daily using wathtower. Unfortunately the upgrade didn't work today. Luckily I was able to switch back to version 1.30.1 and everything worked again. What has changed so massively in the two versions? I was able to find the following entries in the log file: ``` [2024-01-31 00:08:46.331][vaultwarden::api::web::_][WARN] Parameter guard `p: PathBuf` is forwarding: BadStart('.'). [2024-01-31 00:09:06.304][vaultwarden::api::web::_][WARN] Parameter guard `p: PathBuf` is forwarding: BadStart('.'). [2024-01-31 00:09:37.162][vaultwarden::api::web::_][WARN] Parameter guard `p: PathBuf` is forwarding: BadStart('.'). [2024-01-31 00:10:13.913][request][INFO] GET /admin/.env [2024-01-31 00:10:13.913][vaultwarden::api::web::_][WARN] Parameter guard `p: PathBuf` is forwarding: BadStart('.'). [2024-01-31 00:10:13.914][response][INFO] (web_files) GET /<p..> [10] => 422 Unprocessable Entity [2024-01-31 00:10:38.698][vaultwarden::api::web::_][WARN] Parameter guard `p: PathBuf` is forwarding: BadStart('.'). [2024-01-31 04:11:01.664][rocket::server][WARN] Received SIGTERM. Requesting shutdown. [2024-01-31 04:11:01.669][vaultwarden][INFO] Vaultwarden process exited! [2024-01-31 04:11:05.442][start][INFO] Rocket has launched from http://0.0.0.0:80 ``` The compose file is also very simple: ``` version: '3' services: vaultwarden: image: vaultwarden/server:1.30.1 container_name: vaultwarden hostname: vaultwarden restart: unless-stopped volumes: - /vaultwarden:/data - /vaultwarden/.env:/.env environment: - LOG_FILE=/data/bitwarden.log - LOG_LEVEL=info - EXTENDED_LOGGING=true labels: - "traefik.enable=true" - "traefik.http.middlewares.vaultwarden-https.redirectscheme.scheme=https" - "traefik.http.routers.vaultwarden-http.entrypoints=web" - "traefik.http.routers.vaultwarden-http.rule=Host(`domain-1`) || Host(`domain-2`)" - "traefik.http.routers.vaultwarden-http.middlewares=vaultwarden-https@docker" - "traefik.http.routers.vaultwarden.entrypoints=web-secure" - "traefik.http.routers.vaultwarden.rule=Host(`domain-1`) || Host(`domain-2`)" - "traefik.http.routers.vaultwarden.tls=true" - "traefik.http.routers.vaultwarden.tls.certresolver=default" - "traefik.http.routers.vaultwarden.middlewares=secHeaders@file" - "traefik.http.services.vaultwarden.loadbalancer.server.port=80" networks: - traefik_proxy - default networks: traefik_proxy: name: traefik_proxy external: true default: driver: bridge ``` Please help me find the error. Thank you very much!