mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-02-05 00:29:40 +03:00
Session expires immediately on login #825
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dmaes on GitHub (Oct 8, 2020).
Recently set-up a fresh Bitwarden_RS instance (compiled image myself, not docker), and when logging in, my session expires immediately. I get a 200 on /api/accounts/prelogin and /identity/connect/token, logs show a succesfull login for my user. Then I get a 401 on /api/sync?excludeDomains=true and logs show [auth][ERROR] Unauthorized Error: Invalid claim . This is with version 1.16.3 and webvault version 2.16.1 (webvault is the distributed release, not compiled myself) with postgresql backend. Host details: debian buster in a ProxmoxVE LXC Ct. I tried reverting to version 1.15.0, webvault 2.14.0 and sqlite backend, to mimic a working setup on a debian buster lxc on a raspberry pi 4, to no avail.
@BlackDex commented on GitHub (Oct 11, 2020):
Hello @dmaes, could you try this again with the very latest version 1.17.0 and report back again?
@dmaes commented on GitHub (Oct 11, 2020):
Didn't help, same problem persists
@BlackDex commented on GitHub (Oct 12, 2020):
Could you check the date and time if they are in sync?
This can be done via the /admin/diagnostics page for example.
Also, some more information like logs would be nice to that we maybe can see a bit more.
@dmaes commented on GitHub (Oct 13, 2020):
Server and browser time are the sime in /admin/diagnostics page. I noticed server wasn't in correct timezone, but should not have mattered (and indeed didn't fix it).
Logs since a restart (I did a login, with session expiring immediately and refreshed /admin/diagnostics):
I did not configure reverse proxy for /notifications websockets, but didn't on the working setup either, so that should also not be the problem
@JanHBade commented on GitHub (Feb 18, 2021):
same for me here...
running the docker container under a sub-url, the diag page proxy no but that wrong??
Docker-Compose:
Log:
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)