mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-05-07 12:34:03 -05:00
[GH-ISSUE #6561] Editing issue in clients with 2025.12.0 #11280
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 @ashoktvm on GitHub (Dec 16, 2025).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6561
Prerequisites
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Config:
Vaultwarden Build Version
1.34.3
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
pangolin 1.12.2
Host/Server Operating System
Linux
Operating System Version
No response
Clients
Desktop, Browser Extension
Client Version
2025.12.0
Steps To Reproduce
Steps To Reproduce
Login in bitwarden
Press edit into a login
Edit something (for example add a site)
Press Save
Get the error "An error has occurred"
Press Cancel
Check that the change was still made
Expected Result
The expectations is to get a success and that wasn't need to press the cancel.
Actual Result
An error has occurred, but with the change made.
Screenshots or Videos
No response
Additional Context
This issues only happens in version 2025.12, I test the 2025.11.2 and this don't happen.
Operating System
Windows
Operating System Version
Windows 11 Pro 25H2
Web Browser
Edge
Browser Version
Last stable available
Environment Versions
Version 2025.12.0
SDK 'main (0107af7)'
Shell 37.7.0
Renderer 138.0.7204.251
Node 22.20.0
Architecture x64
Expected Result
It should say item saved
Actual Result
It now says an error has occured
Logs
Screenshots or Videos
No response
Additional Context
No response
@mxsrm commented on GitHub (Dec 16, 2025):
Use
:testingtag until the new stable release is out.@luisbandalap commented on GitHub (Dec 17, 2025):
Be aware upgrading to :testing tag may logout all clients (mobile/desktop/browser).
In the case of the android app i had to clear all app data and login again, not clearing app data makes the app throw
Unexpected push token received from bitwarden server: error decoding response bodyerror,With browser and desktop i had to login without clearing app data.
@ashoktvm commented on GitHub (Dec 17, 2025):
it just logged me out. No error other than that
@pvfpinto commented on GitHub (Dec 17, 2025):
Hi,
When will go to stable?
Thanks.
@krombel commented on GitHub (Dec 18, 2025):
The main change to fix this issue is implemented by https://github.com/dani-garcia/vaultwarden/pull/6557
=> I added this to my nginx configuration to fix this issue until stable is released:
@Misterbabou commented on GitHub (Dec 18, 2025):
=> Until stable is released, I added for Apache RP :
@sammyke007 commented on GitHub (Dec 19, 2025):
Damn, I was going crazy and checking my config 10 times because of this. Glad to see it's not me 👍🏻
@deajan commented on GitHub (Dec 19, 2025):
For completenees, here's what I use with Haproxy.
Of course one could add another acl to limit this fix to a certain host.
@jpagh commented on GitHub (Dec 19, 2025):
Caddy
@manelrodero commented on GitHub (Dec 19, 2025):
I've tried to figure out how to do this with Traefik. But it's a pure proxy and can't return content.
I should do something like this:
And then use a service with a simple nginx:alpine or similar to return empty JSON:
I'll wait for the official solution ;-)
@dwarf-king-hreidmar commented on GitHub (Dec 20, 2025):
I ran into this issue (errors when saving passwords with the bitwarden plugin). I pulled the latest image (testing) and issues appear to have resolved. Thanks @dani-garcia and everyone else for the insanely quick fix.
@BlackDex commented on GitHub (Dec 20, 2025):
This issue has been fixed already in
testingvia #6557, also some other PR's have been merged which solve some possible issues with the v2025.12 clients via #6574 and #6572.Therefor I'm going to close this issues as it's already resolved.
We will try to release a new stable a.s.a.p.
@vincentization commented on GitHub (Feb 2, 2026):
FYI I am still running into the Edit issue with the latest Chrome Browser Extension (Version 2025.12.1.)
iOS app seems to be not affected by this, however I can still not login there using the credentials (I guess this is unrelated, already reported in #6610 )
@BlackDex commented on GitHub (Feb 2, 2026):
That is a bit vague, what kind of issues, the same as the OP?
Did you checked you are on the latest Vaultwarden version?
A bit more details would be better, but first check the diagnostics.
That issue is also already resolved by using an updated version of Vaultwarden, so too me, that most likely says you are using an outdated version, but unable to say for sure, as you didn't posted those details.
@vincentization commented on GitHub (Feb 2, 2026):
sorry for being vague, I am referring to the initial reported issue by OP. To me it sounded like only certain client versions were affected thats why I reported just that. However if you saying this issue is caused by an outdated server version, then I can ask our admin to perform an update and check if it fixes that. The current server version seems to be 2025.6.0.
in Regards to the iOS App issue:
I can rule out an outdated client version, It was updated to 2026.1.0 before reporting. If this issue is also caused by server instead of client I will report back after the next update
@stefan0xC commented on GitHub (Feb 2, 2026):
It's definitely outdated if it still reports 2025.6.0 because the newest version has been updated to report itself as 2025.12.0 already
feecfb20da/src/api/core/mod.rs (L221)@vincentization commented on GitHub (Feb 2, 2026):
the server update was just done (2025.12.0) and both issues are gone now. sorry for the misunderstanding and thanks a lot for your efforts in this project