Bitwarden Chrome Extension 2026.8.0 fails cant login or see entries

[kearzh]

Prerequisites

• I have searched the existing Closed AND Open Issues AND Discussions
• I have searched and read the documentation

Vaultwarden Support String

Hello Vaultwarden Team,

i use the docker image tag vaultwarden/server:1.37.2 and run vaultwarden as docker container but it doesnt fix the Problem.

On Firefox we had a workaround that we delete the extension via Explorer and it will be pulled the extension with the newest version and it works normally after browser restart

The Path:
C:\Users\xxx\AppData\Roaming\Mozilla\Firefox\Profiles\n367s27u.default-release-1758630259565\storage\default\moz-extension++++Bitwarden-id-name User Context

ID can u check with about:debugging#/runtime/this-firefox

On Chrome we had a workaround to delete the extension and the CRX-Cache via the Explorer Path
In the crx Cache you should see a File called "metadata.json" with assigning hash of the plugin.
This Hash-File was deleted, but both steps doesnt fix the problem.

The Path of the extension: C:\Users\User\AppData\Local\Google\Chrome\User Data\Profile 1\Extensions\nngceckbapebfimnlniiiahkandclblb

The Extension-CRX-Cache: C:\Users\User\AppData\Local\Google\Chrome\User Data\extensions_crx_cache

Will there be a fix for the docker image?

Kind regards

Keanu

Vaultwarden Build Version

v1.37.2 Docker Image

Deployment method

Official Container Image

Custom deployment method

No response

Reverse Proxy

nginx/1.30.4

Host/Server Operating System

Linux

Operating System Version

Rocky 9 Linux

Clients

Browser Extension

Client Version

No response

Steps To Reproduce

See above

Expected Result

See above

Actual Result

See above

Logs

Screenshots or Videos

No response

Additional Context

No response

[MonYvel]

Similar issue here. But on Windows 11 with Vivaldi (Chromium browser.). Running latest version of VaultWarden.

Can't login to Vaultwarden with official Bitwarden extention 2026.08

VaultWarden error: [error][ERROR] 2FA token not provided

Windows standalone app works fine.

Thanks for the help!

[Luka0103]

Can confirm this also for Firefox, Edge and Chrome.

Bitwarden extention 2026.08 does not work at all.

[opiao]

Hello,

+1

Bitwarden chrome extention 2026.08 does not work

[mr687]

+1

[Jaeensson]

+1
Same issue on the Firefox extension

[BlackDex]

See #7615 (comment)

[EstrianTech]

+1
Can confirm this is also happening on firefox extension.
Had to downgrade to 2026.7.0 to allow normal function.

[brentfamily51]

I'm having issues with the android app and chrome extension. I can log in but can't see any passwords. Fully updated

[kxnstantinos]

What seems to have fixed it for me was swapping the self hosted instance, I entered some random url and was able to trigger a network error this way when I tried to log in which even more randon login credentials. Which makes sense as the random url doesn't exist. Afterwards I was able to enter the correct instance url and could log in again. Hope this limbo helps anybody.

[azalin1975]

I have tried this solution but it did not work for me. What did work was downgrading the browser extension. I am on Firefox by the way and downgrading to 2026.7.0 enabled me to enter a 2FA code which was accepted. With 2026.8.0 the 2FA code would get rejected with a message saying the code was invalid.

[BlackDex]

Probably if you now force a sync, and update the extension again, it will still work.

[azalin1975]

And it then will fail after 30 days again when the 2FA expires.

[BlackDex]

No, probably not, why do you think that? I tested 2FA using FireFox and 2026.8.0 extension, and it works just fine.
It probably doesn't work for you because it had outdated cached data locally, which causes newer clients to fail.

If you are 100% sure you have Vaultwarden v1.37.2 installed, it should just work fine.

[azalin1975]

I am 100% sure that I am on 1.37.2 but... what I had not done was completely remove the extension and reinstall it. Which is basically what happened when I installed the 2026.7.0 version because I had removed the 2026.8.0 first, then installed 2026.7.0 and this allowed me to login to my vault again. Now I have upgraded the extension again and it seems to work fine. So I guess any left over cache was causing problems for me...

[kulisz]

What helped me with self-hosted was updating to the image from August 22, 2026 (1.37.2, before I had 1.37.1), then removing the plugin from browser (so that the entire cache would be deleted) and reinstalling it.

[BlackDex]

It's indeed needed to have the latest version installed, else clients since v2026.8.0 will fail.