Invalid TOTP Code in Browser Extension and Web

Odd behavior all of a sudden. I have a TOTP code generated for a site in my TOTP app on my phone and in the Bitwarden entry, both produce different numbers. The secret key is the same for both, and the clock on both devices shows the same time. The phone produces the correct TOTP, the Bitwarden extension and the entry on the web both produce the wrong TOTP. Running the latest Bitwarden self-hosted image as well as the latest extension in Firefox. I deleted the TOTP entry and generated a new one and the still both produce a different TOTP. Any ideas?

If you open https://time.is on your computer with the BW extension, how much is your clock off? – For comparison, I see this:

OK, that’s very strange. It says it’s WAY off, but the time on my computer (Windows 11) is the exact actual local time here… It also says my clock hasn’t been updated in Windows for 4 months, even though it’s showing the exact local time.

{8840BA58-14A9-46C1-8A76-57BFB078FAC9}

If you hadn’t written that, I would have guessed you had the wrong time zone – or depending on where you live that it would be a one hour winter/summer time difference thing…

I guess time.is correctly identified your region?

PS: Obvious, but anyway: whatever is happening on your computer… that should at least explain the wrong TOTP codes…

Yeah, very strange, the site is correctly identifying my location and saying my time is an hour off. The actual time on my computer isn’t off, at least not in any clock I can see related to the OS. Strange thing is I tried to force an update and it won’t successfully connect to a single NTP server. All other devices on my network are happily connecting for NTP updates, just not this one computer. You figured out what’s wrong, now I guess I’ll have to figure out how to fix it. I wonder what that site is comparing it’s calculated time with, it’s certainly not the time in the OS, since they are the same.

Well, while tinkering with the time settings in Windows 11, it suddenly said it updated, and while the time on the computer didn’t actually change even by a single minute, the site shows the following. Thanks for your help @Nail1684

{CB122D53-24EA-4FAE-B509-A1AC194B1BE0}

Glad, you figured it out now. – And does BW now produce the correct TOTP codes again?

Well, to be fair, YOU figured it out. I didn’t think to check the time since the time was correct. Yes, TOTP codes once again match between the browser extension and my phone TOTP app! Thanks again!