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.
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.
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.
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.