Chromium extension (using Vivaldi) not logging in

Ask the Community Password Manager
, , ,
1

Hi,

Every morning when I try to unlock the Bitwarden plugin in my Vivaldi browser, it just sits on the same screen that says ‘your vault is locked’ and ‘accessing Bitwarden’. Nothing seems to happen.

However, if I logout and then try to login it works fine. This started happening a week or two ago probably.

I didn’t find another post with this exact issue.

2

@chris909 Welcome to the forum!

Recently, I saw the same thing on my machine (also with Vivaldi, but on Win 11) – and it had to do with the “biometric unlock” setup.

If you every enabled biometric unlock: check if “Allow browser integration” is still enabled in the desktop app, and make sure that you start the desktop app before you open the browser.

Alternatively: deactivate biometric unlock on the browser extension, if you don’t need it.

3

thanks for the response, I actually saw your other post I think. I then disabled some settings in the desktop app before deciding just to remove it completely. But…I didn’t think about the setting in the browser extension so hopefully that’s it. Will report back if it looks good tomorrow.

4

Slight improvement today, I didn’t have to logout, it just took about 30 seconds before the master password form appeared when I tried to unlock. So it works but still not ideal and not as it used to where the request for the master password was immediate.

I now have no local desktop app and biometrics disabled in the browser extension. Will see how it goes over the next week.

5

Okay still the same issue and now I see the sidebar opening everytime the Bitwarden timeout expires the current login. I saw the sidebar issue was registered as a bug elsewhere. Maybe I’ll open this as a bug too.

6

Hm. Then it may have been something else. I would recommend to log out and toggle the extension on Vivaldi off/on. If that doesn’t help, I personally would try a full uninstall/reinstall of the browser extension. (and make sure that the local data was removed before reinstallation)

But, there are also still some open issues around similar reports – maybe the two most prominent one’s are:

So if you still experience this, you could add your report somewhere on GitHub…

Yep, that was reported here: