rocket-worker-thread' panicked, Unable to log into vault. #1664

New Issue

MrUnknownDE · 2026-04-06T02:10:57+02:00

MrUnknownDE commented

2026-04-06 02:10:57 +02:00

Originally created by @sebasdt on 4/1/2023

Subject of the issue

Rocket giving a 404 after trying to connect to it.
accessing the container directly also gives the same error look below here:

Deployment environment

Im using a vm within that a docker enviorment.

vaultwarden version:
1.28.0 or the latest tag for docker

Install method:
on Docker via portainer.
Clients used:
Windows and android basicly every option and no ios or linux clients.
Reverse proxy and version:
Cloudflare ---> nginx Rproxy ---> container
MySQL/MariaDB or PostgreSQL version:
Other relevant details:
I think this happend because Im experimenting with cloudflare tunnels. dont really think it has to do with cloudflare.

Steps to reproduce

I updated to the latest release and restarted the container. I am at version 1.28.0
as you can see in my log file you can see what parameters/env settings in using.

Expected behaviour

Im able to access the container and not get a rocket 404.
even when I try to access the container locally/directly the same error appears.

Actual behaviour

Im not able to do anything with vaultwarden

Troubleshooting data

LOGS:
https://pastebin.com/VNwLKb8n

*Originally created by @sebasdt on 4/1/2023*   ### Subject of the issue Rocket giving a 404 after trying to connect to it. accessing the container directly also gives the same error look below here: ![image](https://user-images.githubusercontent.com/67417070/229303916-bfdb4fe8-58f8-4df7-b6c1-0370ad06b0f1.png) ### Deployment environment Im using a vm within that a docker enviorment.     * vaultwarden version: 1.28.0 or the latest tag for docker  * Install method: on Docker via portainer. * Clients used:  Windows and android basicly every option and no ios or linux clients. * Reverse proxy and version:  Cloudflare ---> nginx Rproxy ---> container * MySQL/MariaDB or PostgreSQL version:  -- * Other relevant details: I think this happend because Im experimenting with cloudflare tunnels. dont really think it has to do with cloudflare. ### Steps to reproduce  I updated to the latest release and restarted the container. I am at version 1.28.0 as you can see in my log file you can see what parameters/env settings in using. ### Expected behaviour  Im able to access the container and not get a rocket 404. even when I try to access the container locally/directly the same error appears. ### Actual behaviour  Im not able to do anything with vaultwarden ### Troubleshooting data  ![image](https://user-images.githubusercontent.com/67417070/229303549-714cdd81-9d54-4e9f-98a4-ff96aab02176.png) LOGS: https://pastebin.com/VNwLKb8n ![image](https://user-images.githubusercontent.com/67417070/229304354-a69e7150-da38-48dd-841e-999593c82be1.png)

MrUnknownDE closed this issue

2026-04-06 02:10:57 +02:00

Sign in to join this conversation.

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/vaultwarden#1664