An error has occurred when editing

[pvfpinto]

Hi,

I'm having an issue since Bitwarden Windows Desktop cliente 2025.12 (this don't happen with 2025.11.2.

Steps To Reproduce

1. Login in bitwarden
2. Press edit into a login
3. Edit something (for example add a site)
4. Press Save
5. Get the error "An error has occurred"
6. Press Cancel
7. The change was still made even with the error

Expected Result
The expectations is to get a success and that wasn't need to press the cancel.

Additional Context
This issues only happens in version 2025.12, I test the 2025.11.2 and this don't happen.
Self hosted Vaultwarden with docker with the last version

Operating System Version
Windows 11 Pro 25H2

Environment Versions
Version 2025.12.0
SDK 'main (0107af7)'
Shell 37.7.0
Renderer 138.0.7204.251
Node 22.20.0
Architecture x64

[Michi1983]

Hi

I have exactly the same problem and unfortunately haven't found a solution yet.

[pquantin]

Hi,

As discussed in #6550, you need to use the testing image as the fix is not published in latest tag yet.

Best regards.

[pvfpinto]

Hi,

As discussed in #6550, you need to use the testing image as the fix is not published in latest tag yet.

Best regards.

Testing image for the vaultwarden docker?

[pquantin]

Yes.

[Gerardv514]

Hi,

As discussed in #6550, you need to use the testing image as the fix is not published in latest tag yet.

Best regards.

Testing image for the vaultwarden docker?

You think it's ok to run testing image in a production environment?

[Cyber5imon]

Hi,

As discussed in #6550, you need to use the testing image as the fix is not published in latest tag yet.

Best regards.

Can you direct me to the part of #6550 that discusses using the testing image? I searched for it and have been unable to find it.

And for those that are interested in running the testing image it is available by executing: docker pull vaultwarden/server:testing

[stefan0xC]

I mentioned it here #6550 (reply in thread)

[mxsrm]

Using testing works fine, but shouldn't this bug in combination with the released official clients trigger a really timely update of the official stable version of vaultwarden now?

[stefan0xC]

Well, at least not automatically. But I agree that this breaking change is probably warranting a new release as stated in the wiki.

[mxsrm]

Yes I understand you have to check a little more thorough before releasing a new stable version. As you said, breaking change and the latest stable release is from july.

[Gerardv514]

Using testing works fine, but shouldn't this bug in combination with the released official clients trigger a really timely update of the official stable version of vaultwarden now?

I too am dead in the water, but will never run testing in a production environment.

[stefan0xC]

You can also downgrade your clients if you don't want to use testing.

[BlackDex]

We might need to check for other changes before releasing a new version though

[stefan0xC]

I can probably push and create a PR for web-v2025.12.0 later tonight (as I'm more or less done with updating the patch set)... I was initially going to wait for the next release of the web-vault in the hopes that upstream fixes their changes to the policy component (which is probably the one thing we would have to test extensively because I think upstream added further policies) - so a fix like stefan0xC/bitwarden_clients@1d55c6d would not be needed. (Or alternatively we could also return nothing for that specific endpoint as well...)

[fireheadman]

any updates on this?

getting this also…. (1st save attempt)

then 2nd save attempt

I signed out and back in… still get this.
yet when I review the entry, it does actually save the new password

[stefan0xC]

What is your Vaultwarden version? Can you make sure you are using v1.35.0 or higher?

[fireheadman]

I see I am one behind, thanks for the reminder on the new release. updating and will see how it goes in a bit

[fireheadman]

bitwarden guys want no part of this... kinda understandable since they do not support vaultwarden

[r-woolley]

Hi i also had this problem
Updated vaultwarden this morning and no longer have the problem