# \[SOLVED\] New bitwarden firefox addon breaks vaultwarden? **URL:** \ **Category:** Help\ **Created:** [July 24, 2026, 2:09pm UTC](https://vaultwarden.discourse.group/t/solved-new-bitwarden-firefox-addon-breaks-vaultwarden/5067 "2026-07-24T14:09:16Z")\ **Posts on this page:** 17\ **Page:** 1
**Author:** ![Partridge2562](https://avatars.discourse-cdn.com/v4/letter/p/13edae/32.png) [@Partridge2562](https://vaultwarden.discourse.group/u/Partridge2562)\ **Post date:** [July 24, 2026, 2:09pm UTC](https://vaultwarden.discourse.group/t/solved-new-bitwarden-firefox-addon-breaks-vaultwarden/5067/1 "2026-07-24T14:09:16Z")
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. ---
**Author:** ![jerdenn](https://avatars.discourse-cdn.com/v4/letter/j/3d9bf3/32.png) [@jerdenn](https://vaultwarden.discourse.group/u/jerdenn)\ **Post date:** [July 24, 2026, 4:51pm UTC](https://vaultwarden.discourse.group/t/solved-new-bitwarden-firefox-addon-breaks-vaultwarden/5067/2 "2026-07-24T16:51:50Z")
Same here, after that 7.0 update. Can someone help us with this issue? ---
**Author:** ![cyanide77](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/cyanide77/32/917_2.png) [@cyanide77](https://vaultwarden.discourse.group/u/cyanide77)\ **Post date:** [July 24, 2026, 7:02pm UTC](https://vaultwarden.discourse.group/t/solved-new-bitwarden-firefox-addon-breaks-vaultwarden/5067/3 "2026-07-24T19:02:05Z")
seems you maybe running old version still? have you updated your VW to latest 1.37?? ---
**Author:** ![Partridge2562](https://avatars.discourse-cdn.com/v4/letter/p/13edae/32.png) [@Partridge2562](https://vaultwarden.discourse.group/u/Partridge2562)\ **Post date:** [July 24, 2026, 7:49pm UTC](https://vaultwarden.discourse.group/t/solved-new-bitwarden-firefox-addon-breaks-vaultwarden/5067/4 "2026-07-24T19:49:17Z")
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+](https://github.com/dani-garcia/vaultwarden/releases) ---
**Author:** ![pauldab](https://avatars.discourse-cdn.com/v4/letter/p/8797f3/32.png) [@pauldab](https://vaultwarden.discourse.group/u/pauldab)\ **Post date:** [July 25, 2026, 5:16am UTC](https://vaultwarden.discourse.group/t/solved-new-bitwarden-firefox-addon-breaks-vaultwarden/5067/5 "2026-07-25T05:16:00Z")
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. ---
**Author:** ![Partridge2562](https://avatars.discourse-cdn.com/v4/letter/p/13edae/32.png) [@Partridge2562](https://vaultwarden.discourse.group/u/Partridge2562)\ **Post date:** [July 25, 2026, 1:04pm UTC](https://vaultwarden.discourse.group/t/solved-new-bitwarden-firefox-addon-breaks-vaultwarden/5067/6 "2026-07-25T13:04:36Z")
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. ---
**Author:** ![pauldab](https://avatars.discourse-cdn.com/v4/letter/p/8797f3/32.png) [@pauldab](https://vaultwarden.discourse.group/u/pauldab)\ **Post date:** [July 25, 2026, 11:24pm UTC](https://vaultwarden.discourse.group/t/solved-new-bitwarden-firefox-addon-breaks-vaultwarden/5067/7 "2026-07-25T23:24:36Z")
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. ---
**Author:** ![Partridge2562](https://avatars.discourse-cdn.com/v4/letter/p/13edae/32.png) [@Partridge2562](https://vaultwarden.discourse.group/u/Partridge2562)\ **Post date:** [July 26, 2026, 1:08pm UTC](https://vaultwarden.discourse.group/t/solved-new-bitwarden-firefox-addon-breaks-vaultwarden/5067/8 "2026-07-26T13:08:49Z")
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. ---
**Author:** ![oktay454](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/oktay454/32/1295_2.png) [@oktay454](https://vaultwarden.discourse.group/u/oktay454)\ **Post date:** [July 27, 2026, 11:15pm UTC](https://vaultwarden.discourse.group/t/solved-new-bitwarden-firefox-addon-breaks-vaultwarden/5067/9 "2026-07-27T23:15:28Z")
I had a same problem. I updated Vaultwarden, it fix. ---
**Author:** ![jhaar](https://avatars.discourse-cdn.com/v4/letter/j/8c91f0/32.png) [@jhaar](https://vaultwarden.discourse.group/u/jhaar)\ **Post date:** [August 4, 2026, 9:14am UTC](https://vaultwarden.discourse.group/t/solved-new-bitwarden-firefox-addon-breaks-vaultwarden/5067/10 "2026-08-04T09:14:51Z")
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)](https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/versions/) , restarted Firefox for luck - and the add-on works fine. ---
**Author:** ![pizzaplaza](https://avatars.discourse-cdn.com/v4/letter/p/bbce88/32.png) [@pizzaplaza](https://vaultwarden.discourse.group/u/pizzaplaza)\ **Post date:** [August 5, 2026, 12:30pm UTC](https://vaultwarden.discourse.group/t/solved-new-bitwarden-firefox-addon-breaks-vaultwarden/5067/11 "2026-08-05T12:30:33Z")
Thanks alot, this solved my issue also. ---
**Author:** ![itAdmin](https://avatars.discourse-cdn.com/v4/letter/i/97f17d/32.png) [@itAdmin](https://vaultwarden.discourse.group/u/itAdmin)\ **Post date:** [August 22, 2026, 2:57am UTC](https://vaultwarden.discourse.group/t/solved-new-bitwarden-firefox-addon-breaks-vaultwarden/5067/12 "2026-08-22T02:57:27Z")
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. ---
**Author:** ![BrainStone](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/brainstone/32/1872_2.png) [@BrainStone](https://vaultwarden.discourse.group/u/BrainStone)\ **Post date:** [August 22, 2026, 9:38am UTC](https://vaultwarden.discourse.group/t/solved-new-bitwarden-firefox-addon-breaks-vaultwarden/5067/13 "2026-08-22T09:38:40Z")
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](https://github.com/bitwarden/clients/issues/22591) ---
**Author:** ![Partridge2562](https://avatars.discourse-cdn.com/v4/letter/p/13edae/32.png) [@Partridge2562](https://vaultwarden.discourse.group/u/Partridge2562)\ **Post date:** [August 23, 2026, 12:25pm UTC](https://vaultwarden.discourse.group/t/solved-new-bitwarden-firefox-addon-breaks-vaultwarden/5067/14 "2026-08-23T12:25:24Z")
Version [1.37.2](https://github.com/dani-garcia/vaultwarden/releases/tag/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.” ---
**Author:** ![BrainStone](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/brainstone/32/1872_2.png) [@BrainStone](https://vaultwarden.discourse.group/u/BrainStone)\ **Post date:** [August 24, 2026, 7:16am UTC](https://vaultwarden.discourse.group/t/solved-new-bitwarden-firefox-addon-breaks-vaultwarden/5067/15 "2026-08-24T07:16:49Z")
~~Unfortunately things are still just as broken.~~ ~~After unlocking the vault I get a blank window with 2 horizontal lines. Closing and reopening the window shows a working interface but no password entries. Autofill consequently also doesn’t work. Funnily enough my other instance has been working completely fine without any issues.~~ ~~The only difference that comes to mind between the two is that the working one doesn’t have an organization and the not working one does have one (or at least that my account is part of one).~~ ~~Desktop client and Chrome plugin work without a hitch.~~ ~~Any debugging info I can provide?~~ Edit: I had to reinstall the plugin (uninstall → restart browser → reinstall). Started working fine after that. ---
**Author:** ![stefan0xC](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/stefan0xc/32/1765_2.png) [@stefan0xC](https://vaultwarden.discourse.group/u/stefan0xC)\ **Post date:** [August 24, 2026, 7:17am UTC](https://vaultwarden.discourse.group/t/solved-new-bitwarden-firefox-addon-breaks-vaultwarden/5067/16 "2026-08-24T07:17:07Z")
Also you might need to do some additional troubleshooting steps. > **[/admin/diagnostics - v1.37.2 (Upgrade to this version when using clients...](https://github.com/dani-garcia/vaultwarden/discussions/7615#discussioncomment-18115531)** > > Note This update is required for support with clients with version 2026.8.0+, please update before reporting any issues with them. What's Changed Fix Debian cross-linking with xx-cargo by @alexlilu... ---
**Author:** ![itAdmin](https://avatars.discourse-cdn.com/v4/letter/i/97f17d/32.png) [@itAdmin](https://vaultwarden.discourse.group/u/itAdmin)\ **Post date:** [August 29, 2026, 3:49am UTC](https://vaultwarden.discourse.group/t/solved-new-bitwarden-firefox-addon-breaks-vaultwarden/5067/17 "2026-08-29T03:49:49Z")
Update 29/8: Updated image to latest 137.2 and all works again. It did require some fiddling per the thread linked by @stefan0xC above. But it works again. Thanks to the devs/maintainers.