mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-02-24 19:07:44 +03:00
Problem with sync new versions client (desktop, mobile) #2467
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 @maciejczarnecki on GitHub (Dec 19, 2025).
Prerequisites
Vaultwarden Support String
[h2::proto::connection][DEBUG] Connection::poll; connection error error=GoAway(b"", NO_ERROR, Library)
Vaultwarden Build Version
1.3.43
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
nginx
Host/Server Operating System
Linux
Operating System Version
No response
Clients
Desktop
Client Version
2025.12
Steps To Reproduce
Expected Result
[h2::proto::connection][DEBUG] Connection::poll; connection error error=GoAway(b"", NO_ERROR, Library)
Actual Result
[h2::proto::connection][DEBUG] Connection::poll; connection error error=GoAway(b"", NO_ERROR, Library)
Logs
Screenshots or Videos
No response
Additional Context
No response
@deajan commented on GitHub (Dec 19, 2025):
Can confirm that latest Bitwarden 2025.12 client cannot edit entries anymore in Vaultwarden server:
The client copy of this cipher is out of dateHere's the corresponding vaultwarden server log
@deajan commented on GitHub (Dec 19, 2025):
Related to https://github.com/dani-garcia/vaultwarden/issues/6561
@maciejczarnecki You should close this one and follow the issue above
@stefan0xC commented on GitHub (Dec 19, 2025):
@deajan If you look at other recent issues and in discussion that's a known and already fixed issue (#6557 is available in
testing). Not sure if that's related to the issue reported here. (But because OP did not provide the support string or steps to reproduce the issue I'm not sure if that is an bug.)@deajan commented on GitHub (Dec 19, 2025):
@stefan0xC Understood, already fixed on my side (I just posted the Haproxy config workaround in #6561).
@Frew777 commented on GitHub (Dec 20, 2025):
Same problem. Waiting for a stable release with a fix.
@stefan0xC commented on GitHub (Dec 20, 2025):
Same problem as OP? Because then can you provide more info? I.e. support string, steps to reproduce the issue, etc.?
@simonemargio commented on GitHub (Dec 20, 2025):
I don't know if this can be helpful, but I'm having the same problem and can provide some information.
The problem appears to be related to the desktop client and the browser extension.
Currently:
I tested on mobile, iOS 26.2 (23C55) - Bitwarden 2025.12.0 (2787), and everything works fine.
The steps to reproduce the problem are those already listed by @deajan previously. Starting from the desktop client or browser extension:
Please note, however, that despite the errors, the item is actually modified on the server and appears updated correctly.
Log similar to deajan's:
Below is the server info:
Config & Details (Generated via diagnostics page)
Config & Details
Failed HTTP Checks:
Config:
@stefan0xC commented on GitHub (Dec 20, 2025):
@simonemargio OP posted a specific error message
[h2::proto::connection][DEBUG] Connection::poll; connection error error=GoAway(b"", NO_ERROR, Library)without any further information to diagnose the cause or reproduce the issue.What you are describing seems to be a separate (already known) issue (https://github.com/dani-garcia/vaultwarden/issues/6561) that stems from an incompatibility with the current release
v1.34.3and newer clientsv2025.12.0(that btw should be fixed in the latesttestingimage)...