2FA no longer working, locked out from web/browser, can't disable it from my mobile session

Ask the Community Password Manager
,
1

I’m a paying bitwarden user.

A couple of months ago, I’ve setup Google Auth 2FA in place of email 2FA. I then logged in and things were working fine ever since.

Today, I noticed the browser extension started asking me for the 2FA code. I then went to my phone and got the code from Google Auth, but it didn’t recognize it, saying it was an invalid 2FA code.

I then gathered the recovery code and still, it’s saying the data is invalid. I don’t know why.

I still have a session in my mobile phone, luckily. However, I can’t disable 2FA from it because the 2FA feature is only implemented in the web app, so it goes to it and requires me to login, which I can’t.

I tried to contact support but never received the confirmation email. I’d like to know why this happened and how I can disable 2FA so that I can setup it again - specially considering I DO have a session in my mobile app. I don’t want to delete and recreate my account wth exported data.

Any ideas? Anyone ever stumbled upon a similar issue before? Anyone from Bitwarden support could please reach out to me?

2

Can you remember that the “Google Auth 2FA” (=TOTP?!) worked in the first place when you set it up? (because when this is not the case, then my coming tip won’t work either)

In the past I had once the issue, that my TOTP-Codes did not work. Turned out to be an “out of time-sync-problem”. Until then I didn’t realise, that TOTP - as I understand it now - requires all devices to have the more or less exact time.

So first idea from me would be: manually force all your (for this purpose used) devices (phone, PC / laptop / whatever, …) to sync to the same internet time resp. time server.

(if I remember correctly, in my case it was a Windows PC which didn’t automatically sync the time for a few months - for whatever reason - and was then “not in time-sync” with the phone which created my TOTP-codes… and then the TOTP-codes were invalid, just as you experience it now)

If that doesn’t work, hopefully someone else has another idea here.