mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-05-23 08:32:45 -05:00
[GH-ISSUE #1924] windows exe client 1.28.0 cannot sync with self host server. #13897
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/vaultwarden#13897
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 @Jecvay on GitHub (Aug 20, 2021).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1924
but if I use exe client of version 1.27.1, everything is ok.
server info:
docker image: vaultwarden/server:latest
@BlackDex commented on GitHub (Aug 20, 2021):
Confirmed, also have found the sollution
@praetorxyn commented on GitHub (Aug 20, 2021):
I can confirm, and it's not just Windows.
I was using bitwardenrs/server-mysql, and I saw that the project had been renamed to vaultwarden, so I thought maybe I was just super out of date or something. So I copied my bitwarden database to vaultwarden, made a new vaultwarden user and gave it the appropriate permissions, commented out my bitwarden configuration YAML, and created a new vaultwarden config YAML and spun up the container using the new image, but I'm still seeing the issue.
This is what I am seeing in regards to a manual sync:
Web vault: Works fine
Brave extension 1.52.0: Works fine
Firefox extension 1.51.1: Works fine
Android app 2.11.3: Works fine
iOS app 2.11.1: Works fine
Windows client 1.28.0: Sync failed
macOS client 1.28.0: Sync failed
Linux client 1.28.0: Sync failed
@praetorxyn commented on GitHub (Aug 21, 2021):
I did receive a Windows client update that seems to have fixed the issue for now at least.
@BlackDex commented on GitHub (Aug 21, 2021):
I guess it would. Since bitwarden self hosted also doesn't provide the keys the client breaks on.