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

New Issue

Closed

opened 2026-07-17 10:33:54 -05:00 by GiteaMirror · 0 comments

GiteaMirror commented 2026-07-17 10:33:54 -05:00

Owner

Copy Link

Copy Source

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!

GiteaMirror closed this issue 2026-07-17 10:34:00 -05:00

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

v2-registration

revert-7033-patch-1

cached-config-operations

test_dylint

1.37.2

1.37.1

1.37.0

1.36.0

1.35.8

1.35.7

1.35.6

1.35.5

1.35.4

1.35.3

1.35.2

1.35.1

1.35.0

1.34.3

1.34.2

1.34.1

1.34.0

1.33.2

1.33.1

1.33.0

1.32.7

1.32.6

1.32.5

1.32.4

1.32.3

1.32.2

1.32.1

1.32.0

1.31.0

1.30.5

1.30.4

1.30.3

1.30.2

1.30.1

1.30.0

1.29.2

1.29.1

1.29.0

1.28.1

1.28.0

1.27.0

1.26.0

1.25.2

1.25.1

1.25.0

1.24.0

1.23.1

1.23.0

1.22.2

1.22.1

1.22.0

1.21.0

1.20.0

1.19.0

1.18.0

1.17.0

1.16.3

1.16.2

1.16.1

1.16.0

1.15.1

1.15.0

1.14.2

1.14.1

1.14

1.13.1

1.13.0

1.12.0

1.11.0

1.10.0

1.9.1

1.9.0

1.8.0

1.7.0

1.6.1

1.6.0

1.5.0

1.4.0

1.3.0

1.2.0

1.1.0

1.0.0

0.13.0

0.12.0

0.11.0

0.10.0

0.9.0

Labels

Clear labels

better for forum

bug

documentation

duplicate

enhancement

future Vault

good first issue

help wanted

low priority

notes

pull-request

Mirrored from GitHub Pull Request

question

SSO

Third party

troubleshooting

wontfix

No labels

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

GiteaMirror ninjasurge (Kaehlen Rog)

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#39083