Originally created by @maciejczarnecki on GitHub (Dec 19, 2025).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6571
### Prerequisites
- [x] I have searched the existing **Closed _AND_ Open** [Issues](https://github.com/dani-garcia/vaultwarden/issues?q=is%3Aissue%20) **_AND_** [Discussions](https://github.com/dani-garcia/vaultwarden/discussions?discussions_q=)
- [x] I have searched and read the [documentation](https://github.com/dani-garcia/vaultwarden/wiki/)
### 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
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. Click on '...'
5. Etc '...'
### 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
```text
```
### Screenshots or Videos
_No response_
### Additional Context
_No response_
GiteaMirror
added the bug label 2026-04-25 21:45:25 -05:00
Can confirm that latest Bitwarden 2025.12 client cannot edit entries anymore in Vaultwarden server:
Open Bitwarden Desktop 2025.12 on Windows-
select an entry
edit it by add something in notes
try to hit save button
client says The client copy of this cipher is out of date
sync client
try to edit again
client says "Unknown error"
Here's the corresponding vaultwarden server log
[2025-12-19 11:22:51.870][request][INFO] POST /events/collect
[2025-12-19 11:22:51.884][response][INFO] (post_events_collect) POST /events/collect application/json => 200 OK
[2025-12-19 11:22:56.277][request][INFO] POST /identity/connect/token
[2025-12-19 11:22:56.281][response][INFO] (login) POST /identity/connect/token => 200 OK
[2025-12-19 11:22:56.425][request][INFO] GET /api/sync?excludeDomains=true
[2025-12-19 11:22:56.584][response][INFO] (sync) GET /api/sync?<data..> => 200 OK
[2025-12-19 11:23:13.935][request][INFO] PUT /api/ciphers/REDACTED_UUID
[2025-12-19 11:23:13.939][response][INFO] (put_cipher) PUT /api/ciphers/<cipher_id> => 200 OK
[2025-12-19 11:23:14.449][request][INFO] GET /api/tasks
[2025-12-19 11:23:14.450][response][INFO] (web_files) GET /<p..> [10] => 404 Not Found
[2025-12-19 11:25:43.246][request][INFO] PUT /api/ciphers/REDACTED_UUID
[2025-12-19 11:25:43.247][vaultwarden::api::core::ciphers][ERROR] The client copy of this cipher is out of date. Resync the client and try again.
[2025-12-19 11:25:43.247][response][INFO] (put_cipher) PUT /api/ciphers/<cipher_id> => 400 Bad Request
[2025-12-19 11:26:33.929][request][INFO] PUT /api/ciphers/REDACTED_UUID
[2025-12-19 11:26:33.931][vaultwarden::api::core::ciphers][ERROR] The client copy of this cipher is out of date. Resync the client and try again.
[2025-12-19 11:26:33.931][response][INFO] (put_cipher) PUT /api/ciphers/<cipher_id> => 400 Bad Request
[2025-12-19 11:26:34.777][request][INFO] GET /notifications/hub?access_token=REDACTED_TOKEN
[2025-12-19 11:26:34.777][vaultwarden::api::notifications][INFO] Accepting Rocket WS connection from ::ffff:XX.XX.XX.XX
[2025-12-19 11:26:34.777][response][INFO] (websockets_hub) GET /notifications/hub?<data..> => 200 OK
[2025-12-19 11:27:00.230][request][INFO] POST /identity/connect/token
[2025-12-19 11:27:00.232][response][INFO] (login) POST /identity/connect/token => 200 OK
[2025-12-19 11:27:00.385][request][INFO] GET /api/sync?excludeDomains=true
[2025-12-19 11:27:00.495][response][INFO] (sync) GET /api/sync?<data..> => 200 OK
[2025-12-19 11:27:05.549][request][INFO] PUT /api/ciphers/REDACTED_UUID
[2025-12-19 11:27:05.551][response][INFO] (put_cipher) PUT /api/ciphers/<cipher_id> => 200 OK
[2025-12-19 11:27:06.047][request][INFO] GET /api/tasks
[2025-12-19 11:27:06.047][response][INFO] (web_files) GET /<p..> [10] => 404 Not Found
<!-- gh-comment-id:3674494837 -->
@deajan commented on GitHub (Dec 19, 2025):
Can confirm that latest Bitwarden 2025.12 client cannot edit entries anymore in Vaultwarden server:
- Open Bitwarden Desktop 2025.12 on Windows-
- select an entry
- edit it by add something in notes
- try to hit save button
- client says `The client copy of this cipher is out of date`
- sync client
- try to edit again
- client says "Unknown error"
Here's the corresponding vaultwarden server log
```
[2025-12-19 11:22:51.870][request][INFO] POST /events/collect
[2025-12-19 11:22:51.884][response][INFO] (post_events_collect) POST /events/collect application/json => 200 OK
[2025-12-19 11:22:56.277][request][INFO] POST /identity/connect/token
[2025-12-19 11:22:56.281][response][INFO] (login) POST /identity/connect/token => 200 OK
[2025-12-19 11:22:56.425][request][INFO] GET /api/sync?excludeDomains=true
[2025-12-19 11:22:56.584][response][INFO] (sync) GET /api/sync?<data..> => 200 OK
[2025-12-19 11:23:13.935][request][INFO] PUT /api/ciphers/REDACTED_UUID
[2025-12-19 11:23:13.939][response][INFO] (put_cipher) PUT /api/ciphers/<cipher_id> => 200 OK
[2025-12-19 11:23:14.449][request][INFO] GET /api/tasks
[2025-12-19 11:23:14.450][response][INFO] (web_files) GET /<p..> [10] => 404 Not Found
[2025-12-19 11:25:43.246][request][INFO] PUT /api/ciphers/REDACTED_UUID
[2025-12-19 11:25:43.247][vaultwarden::api::core::ciphers][ERROR] The client copy of this cipher is out of date. Resync the client and try again.
[2025-12-19 11:25:43.247][response][INFO] (put_cipher) PUT /api/ciphers/<cipher_id> => 400 Bad Request
[2025-12-19 11:26:33.929][request][INFO] PUT /api/ciphers/REDACTED_UUID
[2025-12-19 11:26:33.931][vaultwarden::api::core::ciphers][ERROR] The client copy of this cipher is out of date. Resync the client and try again.
[2025-12-19 11:26:33.931][response][INFO] (put_cipher) PUT /api/ciphers/<cipher_id> => 400 Bad Request
[2025-12-19 11:26:34.777][request][INFO] GET /notifications/hub?access_token=REDACTED_TOKEN
[2025-12-19 11:26:34.777][vaultwarden::api::notifications][INFO] Accepting Rocket WS connection from ::ffff:XX.XX.XX.XX
[2025-12-19 11:26:34.777][response][INFO] (websockets_hub) GET /notifications/hub?<data..> => 200 OK
[2025-12-19 11:27:00.230][request][INFO] POST /identity/connect/token
[2025-12-19 11:27:00.232][response][INFO] (login) POST /identity/connect/token => 200 OK
[2025-12-19 11:27:00.385][request][INFO] GET /api/sync?excludeDomains=true
[2025-12-19 11:27:00.495][response][INFO] (sync) GET /api/sync?<data..> => 200 OK
[2025-12-19 11:27:05.549][request][INFO] PUT /api/ciphers/REDACTED_UUID
[2025-12-19 11:27:05.551][response][INFO] (put_cipher) PUT /api/ciphers/<cipher_id> => 200 OK
[2025-12-19 11:27:06.047][request][INFO] GET /api/tasks
[2025-12-19 11:27:06.047][response][INFO] (web_files) GET /<p..> [10] => 404 Not Found
```
<!-- gh-comment-id:3674514726 -->
@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
@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.)
<!-- gh-comment-id:3674525181 -->
@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.)
@stefan0xC Understood, already fixed on my side (I just posted the Haproxy config workaround in #6561).
<!-- gh-comment-id:3674551714 -->
@deajan commented on GitHub (Dec 19, 2025):
@stefan0xC Understood, already fixed on my side (I just posted the Haproxy config workaround in #6561).
Same problem. Waiting for a stable release with a fix.
Same problem as OP? Because then can you provide more info? I.e. support string, steps to reproduce the issue, etc.?
<!-- gh-comment-id:3677739758 -->
@stefan0xC commented on GitHub (Dec 20, 2025):
> Same problem. Waiting for a stable release with a fix.
Same problem as OP? Because then can you provide more info? I.e. support string, steps to reproduce the issue, etc.?
Extension: Version 2025.12.0 - SDK 'main (0107af7)' - Server version (Third-party) 2025.6.0
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:
Select an item
Make a change (e.g., I change the item name by adding a character)
Save the change by clicking "Save"
The client displays "An error has occurred. An unexpected error has occurred."
I click the "Save" button again
The client displays "An error has occurred. The client copy of this file is out of date. Resync the client and try again."
Please note, however, that despite the errors, the item is actually modified on the server and appears updated correctly.
Log similar to deajan's:
[2025-12-20 12:40:00.362][request][INFO] GET /api/tasks
[2025-12-20 12:40:00.363][response][INFO] (web_files) GET /<p..> [10] => 404 Not Found
[2025-12-20 12:40:00.690][request][INFO] GET /api/ciphers/54c35458-17d2-4d02-9558-bebd15e381d6
[2025-12-20 12:40:00.694][response][INFO] (get_cipher) GET /api/ciphers/<cipher_id> => 200 OK
Below is the server info:
Vaultwarden version: v1.34.3
Web-vault version: v2025.7.0
OS/Arch: linux/aarch64
Running within a container: true (Base: Debian)
Database type: SQLite
Database version: 3.50.2
Uses config.json: false
Uses a reverse proxy: true
IP Header check: true (X-Forwarded-For)
Internet access: true
Internet access via a proxy: false
DNS Check: true
Browser/Server Time Check: true
Server/NTP Time Check: true
Domain Configuration Check: true
HTTPS Check: true
Websocket Check: true
HTTP Response Checks: false
Config & Details (Generated via diagnostics page)
Config & Details
Failed HTTP Checks:
API calls:Header:'content-security-policy'does not contain 'default-src 'none''
@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.3 and newer clients v2025.12.0 (that btw should be fixed in the latest testing image)...
<!-- gh-comment-id:3677818945 -->
@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.3` and newer clients `v2025.12.0` (that btw should be fixed in the latest `testing` image)...
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @maciejczarnecki on GitHub (Dec 19, 2025).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6571
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)...