[SOLVED] New bitwarden firefox addon breaks vaultwarden?

Help
1

This morning my bitwarden firefox addon updated from 2026.6.1 to 2026.7.0.

Nothing works. I see no password entries at all after logging in.

The vaultwarden web interface is fine and I can copy paste from there to proceed.

Anyone else on the current stable docker vaultwarden failing to use bitwarden firefox addon 2026.7.0?

Vaultwarden 1.36.0
Web-Vault 2026.4.1

Edit:

Changed “Allow automatic updates” from Default to Off and manually installed 2026.6.1 and everything works.

1 Like
[SOLVED] Aborted attempt at passkey creation leaves VW unaccessible from FFX plugin
2

Same here, after that 7.0 update.

Can someone help us with this issue?

3

seems you maybe running old version still?

have you updated your VW to latest 1.37??

4

My post was three hours before 1.37 came out. Any comment from devs about whether the 2026.7.0 extension is fully supported?

Edit:

The release of 1.37 notes: This update is required for support with clients with version 2026.7.0+

5

Managed to get my server upgraded to 1.37 but still had the issue in the Firefox extension.

Rolled extension back to 2026.6.1 and it worked.

Just posting here to keep track if anyone has success.

1 Like
6

The link I posted above says 1.37 contains important security fixes so I installed it. “This release contains security fixes for the following advisories. We strongly advice to update as soon as possible.”

I’m still on the firefox extension version 2026.6.1 however. Hesitant to try 2026.7.0 again.

7

Just checked another PC on the same vault, it’s on 2026.7.0 and is ok so I manually upgraded the extension on my main device to 2026.7.0 and this is working now.

Just speculating here, but we may need to have 2026.6.1 or earlier running with server 1.37 for a migration step before it will work with a 2026.7.0+ extension.

8

Thanks @pauldab. I set “Allow automatic updates” back to Default. With the server at 1.37 before the extension upgrade, 2026.7.0 works now for me too. My initial failed auto-upgrade to 2026.7.0 happened before 1.37 even existed.

9

I had a same problem.
I updated Vaultwarden, it fix.

1 Like
10

I just want to “me too” this. Firefox auto-updated the Bitwarden add-on to 2026.07.01 and it stopped working with my older version of vaultwarden. I then upgrade vaultwarden (docker) to latest, and the add-on still couldn’t render anything in the vault. I then installed the previous version of the Bitwarden add-on via Bitwarden Password Manager version history - 25 versions – Add-ons for Firefox (en-US) , restarted Firefox for luck - and the add-on works fine.

1 Like
11

Thanks alot, this solved my issue also.

1 Like
12

Just to update this topic. Appears Bitwarden Firefox ext. 2026.8.0 breaks things again (Mac Tahoe). Mine apparently auto-updated yesterday 21/8.
I’m running vaultwarden/server Docker image last updated 29/7 v1.37.1

[EDIT:] I note in Docker, vaultwarden pushed a “Testing” labelled version yesterday. Might I ask a Mod pls., how’s that going? When do you expect to release that as stable? Will that fix the FF extension issues with latest versions?

Other than that, let me say thank you for your efforts. My fam’ and I (for some) are greatly appreciative.

1 Like
13

I have the same issue. Weirdly enough only one instance breaks completely. The other still somewhat works but stuff like autofilling forms doesn’t work anymore.

Also other people seem affected. Here’s a rejected bug report on the extension: Firefox extension 2026.8.0 fails to sync and shows an empty vault with Vaultwarden 1.37.1 · Issue #22591 · bitwarden/clients · GitHub

14

Version 1.37.2 stable is out now and states: “This update is required for support with clients with version 2026.8.0+, please update before reporting any issues with them.”