Seems like password update operation fails silently #5392
-
Vaultwarden Support StringGenerate support string does nothing... =( Vaultwarden Build VersionVaultwarden 1.32.7 Deployment methodOther method Custom deployment methodCloudron image. Reverse ProxyApache/2.4.52 (Ubuntu) Host/Server Operating SystemLinux Operating System VersionUbuntu 22.04.3 LTS ClientsWeb Vault, Desktop Client VersionNo response Steps To ReproduceWhen I update the password via official BitWarden desktop, the app shows password as updated, but as a matter of fact it doesn't and needs manual refresh. Expected ResultOnce I regenerate the password and app 'blinks' / refresh, I expect it to have latest password. Server responds all 200 codes, so it feels like the server says 'Ok, updated - here is a new one', while it send an old password. Actual ResultPassword update to actually update password. LogsNo response Screenshots or VideosNo response Additional ContextIt seems like started to occur only recently (regenerated password got lost). |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
If Vaultwarden returns a 200 when saving the object, then that is what is saved. If the client somehow does not work, then either the client is broken in some way, or something else goes wrong. Since you already reported an issue at the clients repo of Bitwarden, there is nothing more to do then wait for them to answer. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for such a prompt and detailed answer! Appreciate it 🙏🏻 |
Beta Was this translation helpful? Give feedback.
If Vaultwarden returns a 200 when saving the object, then that is what is saved.
Vaultwarden does not return a single item it self, but if needed the client will send a sync request which will return all items.
If the client somehow does not work, then either the client is broken in some way, or something else goes wrong.
I tested this my self with Vaultwarden and Bitwarden Cloud, both act the same, and thus the issue probably in the client.
Since you already reported an issue at the clients repo of Bitwarden, there is nothing more to do then wait for them to answer.