login with new bitwarden desktop client #1218

New Issue

MrUnknownDE · 2026-04-06T01:41:31+02:00

MrUnknownDE commented

2026-04-06 01:41:31 +02:00

Originally created by @extremMiSt on 2/21/2024

Subject of the issue

when trying to log into a vaultwarden instance using the latest (2024.2.0) bitwarden desktop client.
it does a lot of weird stuff and then goes back to the login screen.

login works with the firefox addon, webclient, andoird client, and and older version of the desktop client (I tried 2024.1.0 appimage, only works once, cause it auto updates).

vaultwarden version: Version 1.30.3 (pulled the fresh docker image today before reporting)
Install method: docker
Clients used:
see above, problem only occurs with desktop client.
Reverse proxy and version: nginx
Other relevant details:
I am on linux mint with the client.

Steps to reproduce

try to login with username+password

Expected behaviour

I get logged in and can use the passwordmanager

Actual behaviour

see attached video. it shows what happens after I tried to log in.
(email is censored, cause cause).

https://github.com/dani-garcia/vaultwarden/assets/1934286/f6adf5aa-057f-4c5c-8d4c-bbcb87aefa6a

Troubleshooting data

On the server during this failed login attempt I get the following output:
[2024-02-21 18:59:49.356][request][INFO] GET /api/config
[2024-02-21 18:59:49.356][response][INFO] (config) GET /api/config => 200 OK
[2024-02-21 18:59:49.356][request][INFO] GET /api/devices/knowndevice
[2024-02-21 18:59:49.359][response][INFO] (get_known_device) GET /api/devices/knowndevice => 200 OK
[2024-02-21 18:59:51.188][request][INFO] GET /api/devices/knowndevice
[2024-02-21 18:59:51.189][response][INFO] (get_known_device) GET /api/devices/knowndevice => 200 OK
[2024-02-21 18:59:55.192][request][INFO] POST /identity/accounts/prelogin
[2024-02-21 18:59:55.194][response][INFO] (prelogin) POST /identity/accounts/prelogin => 200 OK
[2024-02-21 18:59:56.096][request][INFO] POST /identity/connect/token
[2024-02-21 18:59:56.784][vaultwarden::api::identity][INFO] User [redacted] logged in successfully. IP: 172.17.0.1
[2024-02-21 18:59:56.785][response][INFO] (login) POST /identity/connect/token => 200 OK
[2024-02-21 18:59:56.966][request][INFO] GET /api/config
[2024-02-21 18:59:56.967][response][INFO] (config) GET /api/config => 200 OK
[2024-02-21 18:59:57.173][request][INFO] GET /notifications/hub?access_token=[redacted]
[2024-02-21 18:59:57.174][vaultwarden::api::notifications][INFO] Accepting Rocket WS connection from 172.17.0.1
[2024-02-21 18:59:57.174][response][INFO] (websockets_hub) GET /notifications/hub?<data..> => 200 OK
[2024-02-21 18:59:57.175][request][INFO] POST /identity/connect/token
[2024-02-21 18:59:57.181][response][INFO] (login) POST /identity/connect/token => 200 OK
[2024-02-21 18:59:57.223][request][INFO] GET /api/sync?excludeDomains=true
[2024-02-21 18:59:57.223][auth][ERROR] Unauthorized Error: No access token provided
[2024-02-21 18:59:57.224][vaultwarden::api::core::ciphers::_][WARN] Request guard `Headers` failed: "No access token provided".
[2024-02-21 18:59:57.224][response][INFO] (sync) GET /api/sync?<data..> => 401 Unauthorized
[2024-02-21 18:59:57.446][vaultwarden::api::notifications][INFO] Closing WS connection from 172.17.0.1
[2024-02-21 18:59:57.469][request][INFO] GET /api/config
[2024-02-21 18:59:57.470][response][INFO] (config) GET /api/config => 200 OK
[2024-02-21 18:59:58.201][request][INFO] GET /api/config
[2024-02-21 18:59:58.201][response][INFO] (config) GET /api/config => 200 OK
[2024-02-21 18:59:58.202][request][INFO] GET /api/devices/knowndevice
[2024-02-21 18:59:58.203][response][INFO] (get_known_device) GET /api/devices/knowndevice => 200 OK

*Originally created by @extremMiSt on 2/21/2024* ### Subject of the issue when trying to log into a vaultwarden instance using the latest (2024.2.0) bitwarden desktop client. it does a lot of weird stuff and then goes back to the login screen. login works with the firefox addon, webclient, andoird client, and and older version of the desktop client (I tried 2024.1.0 appimage, only works once, cause it auto updates). * vaultwarden version: Version 1.30.3 (pulled the fresh docker image today before reporting) * Install method: docker * Clients used: see above, problem only occurs with desktop client. * Reverse proxy and version: nginx * Other relevant details: I am on linux mint with the client. ### Steps to reproduce try to login with username+password ### Expected behaviour I get logged in and can use the passwordmanager ### Actual behaviour see attached video. it shows what happens after I tried to log in. (email is censored, cause cause). https://github.com/dani-garcia/vaultwarden/assets/1934286/f6adf5aa-057f-4c5c-8d4c-bbcb87aefa6a ### Troubleshooting data On the server during this failed login attempt I get the following output: [2024-02-21 18:59:49.356][request][INFO] GET /api/config [2024-02-21 18:59:49.356][response][INFO] (config) GET /api/config => 200 OK [2024-02-21 18:59:49.356][request][INFO] GET /api/devices/knowndevice [2024-02-21 18:59:49.359][response][INFO] (get_known_device) GET /api/devices/knowndevice => 200 OK [2024-02-21 18:59:51.188][request][INFO] GET /api/devices/knowndevice [2024-02-21 18:59:51.189][response][INFO] (get_known_device) GET /api/devices/knowndevice => 200 OK [2024-02-21 18:59:55.192][request][INFO] POST /identity/accounts/prelogin [2024-02-21 18:59:55.194][response][INFO] (prelogin) POST /identity/accounts/prelogin => 200 OK [2024-02-21 18:59:56.096][request][INFO] POST /identity/connect/token [2024-02-21 18:59:56.784][vaultwarden::api::identity][INFO] User [redacted] logged in successfully. IP: 172.17.0.1 [2024-02-21 18:59:56.785][response][INFO] (login) POST /identity/connect/token => 200 OK [2024-02-21 18:59:56.966][request][INFO] GET /api/config [2024-02-21 18:59:56.967][response][INFO] (config) GET /api/config => 200 OK [2024-02-21 18:59:57.173][request][INFO] GET /notifications/hub?access_token=[redacted] [2024-02-21 18:59:57.174][vaultwarden::api::notifications][INFO] Accepting Rocket WS connection from 172.17.0.1 [2024-02-21 18:59:57.174][response][INFO] (websockets_hub) GET /notifications/hub?<data..> => 200 OK [2024-02-21 18:59:57.175][request][INFO] POST /identity/connect/token [2024-02-21 18:59:57.181][response][INFO] (login) POST /identity/connect/token => 200 OK [2024-02-21 18:59:57.223][request][INFO] GET /api/sync?excludeDomains=true [2024-02-21 18:59:57.223][auth][ERROR] Unauthorized Error: No access token provided [2024-02-21 18:59:57.224][vaultwarden::api::core::ciphers::_][WARN] Request guard \`Headers\` failed: "No access token provided". [2024-02-21 18:59:57.224][response][INFO] (sync) GET /api/sync?<data..> => 401 Unauthorized [2024-02-21 18:59:57.446][vaultwarden::api::notifications][INFO] Closing WS connection from 172.17.0.1 [2024-02-21 18:59:57.469][request][INFO] GET /api/config [2024-02-21 18:59:57.470][response][INFO] (config) GET /api/config => 200 OK [2024-02-21 18:59:58.201][request][INFO] GET /api/config [2024-02-21 18:59:58.201][response][INFO] (config) GET /api/config => 200 OK [2024-02-21 18:59:58.202][request][INFO] GET /api/devices/knowndevice [2024-02-21 18:59:58.203][response][INFO] (get_known_device) GET /api/devices/knowndevice => 200 OK

MrUnknownDE closed this issue

2026-04-06 01:41:31 +02:00

MrUnknownDE referenced this issue

2026-04-06 03:59:14 +02:00

Ensure that a user is actually in an org when applying policies #2725

Sign in to join this conversation.

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/vaultwarden#1218