[GH-ISSUE #2364] Session expiring immediately on login #1235

New issue

Closed

opened 2026-03-03 02:07:21 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 02:07:21 +03:00

Owner

Originally created by @jacklenox on GitHub (Mar 10, 2022).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2364

Subject of the issue

I am having the exact issue described in #1177. I'm definitely running the latest version of Vaultwarden and have just migrated my data. As far as I can see, the Docker container is running on the same timezone as my computer, and they're both in sync.

Deployment environment

It's not clear to me how I access the Diagnostics tab without being able to log in. I see a lot of discussion of accessing: /admin/diagnostics, I can't seem to access this. I'm trying to reach it via: http://localhost:8008/#/admin/diagnostics

I'm clearly misunderstanding something here.

vaultwarden version: 1.24.0

Install method: sudo docker run -d --name vaultwarden -v ~/.vw-data:/data/ -p 8008:80 vaultwarden/server:latest
Clients used: web vault
Reverse proxy and version:
MySQL/MariaDB or PostgreSQL version:
Other relevant details:

Steps to reproduce

Try logging in once server is running.

Expected behaviour

Successful login.

Actual behaviour

"Logged out. Your login session has expired."

Troubleshooting data

[2022-03-10 10:58:58.696][request][INFO] POST /api/accounts/prelogin
[2022-03-10 10:58:58.697][response][INFO] POST /api/accounts/prelogin (prelogin) => 200 OK
[2022-03-10 10:58:58.707][request][INFO] POST /identity/connect/token
[2022-03-10 10:58:58.752][vaultwarden::api::identity][INFO] User jacklenox@fastmail.com logged in successfully. IP: 172.17.0.1
[2022-03-10 10:58:58.752][response][INFO] POST /identity/connect/token (login) => 200 OK
[2022-03-10 10:58:58.817][request][INFO] POST /identity/connect/token
[2022-03-10 10:58:58.822][response][INFO] POST /identity/connect/token (login) => 200 OK
[2022-03-10 10:58:58.834][request][INFO] GET /api/sync?excludeDomains=true
[2022-03-10 10:58:58.835][auth][ERROR] Unauthorized Error: Invalid claim
[2022-03-10 10:58:58.835][response][INFO] GET /api/sync?<data..> (sync) => 401 Unauthorized

Originally created by @jacklenox on GitHub (Mar 10, 2022). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2364   ### Subject of the issue I am having the exact issue described in #1177. I'm definitely running the latest version of Vaultwarden and have just migrated my data. As far as I can see, the Docker container is running on the same timezone as my computer, and they're both in sync. ### Deployment environment  It's not clear to me how I access the Diagnostics tab without being able to log in. I see a lot of discussion of accessing: `/admin/diagnostics`, I can't seem to access this. I'm trying to reach it via: http://localhost:8008/#/admin/diagnostics I'm clearly misunderstanding something here.    * vaultwarden version: 1.24.0  * Install method: `sudo docker run -d --name vaultwarden -v ~/.vw-data:/data/ -p 8008:80 vaultwarden/server:latest` * Clients used:  web vault * Reverse proxy and version:  * MySQL/MariaDB or PostgreSQL version:  * Other relevant details: ### Steps to reproduce  Try logging in once server is running. ### Expected behaviour  Successful login. ### Actual behaviour  "Logged out. Your login session has expired." ### Troubleshooting data  ``` [2022-03-10 10:58:58.696][request][INFO] POST /api/accounts/prelogin [2022-03-10 10:58:58.697][response][INFO] POST /api/accounts/prelogin (prelogin) => 200 OK [2022-03-10 10:58:58.707][request][INFO] POST /identity/connect/token [2022-03-10 10:58:58.752][vaultwarden::api::identity][INFO] User jacklenox@fastmail.com logged in successfully. IP: 172.17.0.1 [2022-03-10 10:58:58.752][response][INFO] POST /identity/connect/token (login) => 200 OK [2022-03-10 10:58:58.817][request][INFO] POST /identity/connect/token [2022-03-10 10:58:58.822][response][INFO] POST /identity/connect/token (login) => 200 OK [2022-03-10 10:58:58.834][request][INFO] GET /api/sync?excludeDomains=true [2022-03-10 10:58:58.835][auth][ERROR] Unauthorized Error: Invalid claim [2022-03-10 10:58:58.835][response][INFO] GET /api/sync?<data..> (sync) => 401 Unauthorized ```

kerem closed this issue

2026-03-03 02:07:22 +03:00

kerem commented

2026-03-03 02:07:22 +03:00

Author

Owner

@BlackDex commented on GitHub (Mar 10, 2022):

You should go to http://localhost:8080/admin/diagnostics, so without the /#/ part, because that is used by the web-vault it self.
Also, I'm not sure how and what you exactly migrated, but if you generated new rsa files which are used for the generation of the JWT, then it probably is an issue with that.

But first try to get the support string.

@BlackDex commented on GitHub (Mar 10, 2022): You should go to http://localhost:8080/admin/diagnostics, so without the `/#/` part, because that is used by the web-vault it self. Also, I'm not sure how and what you exactly migrated, but if you generated new rsa files which are used for the generation of the JWT, then it probably is an issue with that. But first try to get the support string.

kerem referenced this issue

2026-03-03 09:08:57 +03:00

[PR #1235] [CLOSED] Allow setting SMTP auth password from file via SMTP_PASSWORD_FILE #2922

kerem referenced this issue

2026-03-03 09:08:58 +03:00

[PR #1244] [MERGED] Read config vars from files #2924