Suddenly getting invalid TOTP message - can't login #1773

New Issue

MrUnknownDE · 2026-04-06T02:22:35+02:00

MrUnknownDE commented

2026-04-06 02:22:35 +02:00

Originally created by @burntoc on 1/28/2023

After having used the bitwarden.rs and now vaultwarden container on Unraid for a couple of years, I am suddenly getting an invalid TOTP message and the timestamp shows the UTC time, which is 8 hours ahead of myy timezone. I don't know why this is happening or how to fix it. This is what I've tried so far:
Check server time via settings and via "date" command in console - shows correct local time
Check container time via "date" command in console - shows correct local time
Restart container - issue persists
Restart client - issue persists
set TZ variable (never needed before) - issue persists
Tried other clients (that have also worked for a long time) - same issue

UPDATE - Unfortunately, I must have cleared my cookies so now I can't log in to BW at all. (though the extensions that have already worked continue to do so with their cached biometric auth).

I could definitely use help understantding how to fix this issue, which would be best. Worst case, since I have physical access to my host server and if I can't find my recovery phrase, is there something I can edit in the appdata folder that will allow me to disable TOTP and just login with the master accound and password so I can then disable 2FA until we figure out what the heck is suddently going on? Thanks.

*Originally created by @burntoc on 1/28/2023* After having used the bitwarden.rs and now vaultwarden container on Unraid for a couple of years, I am suddenly getting an invalid TOTP message and the timestamp shows the UTC time, which is 8 hours ahead of myy timezone. I don't know why this is happening or how to fix it. This is what I've tried so far: Check server time via settings and via "date" command in console - shows correct local time Check container time via "date" command in console - shows correct local time Restart container - issue persists Restart client - issue persists set TZ variable (never needed before) - issue persists Tried other clients (that have also worked for a long time) - same issue UPDATE - Unfortunately, I must have cleared my cookies so now I can't log in to BW at all. (though the extensions that have already worked continue to do so with their cached biometric auth). I could definitely use help understantding how to fix this issue, which would be best. Worst case, since I have physical access to my host server and if I can't find my recovery phrase, is there something I can edit in the appdata folder that will allow me to disable TOTP and just login with the master accound and password so I can then disable 2FA until we figure out what the heck is suddently going on? Thanks.

MrUnknownDE closed this issue

2026-04-06 02:22:35 +02:00

Sign in to join this conversation.

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/vaultwarden#1773