4
votes
2FA not working?
tildes.net isn't accepting my 2FA codes on login. I used a recovery key and disabled 2FA, but now I can't re-enable it for the same reason (I generate a code with the new secret key given but it gets rejected). I've checked on other sites and it doesn't seem to be a problem with generated 2FA codes on my end, leading me to believe something may be misconfigured on the server (maybe the tildes.net system clock is off or something?).
Anyone else experiencing this?
Edit: Still not really sure why I couldn't get it to work initially, but after giving it some time the problem went away.
Not exactly, but Tildes is persnickety with OTP. I don’t think the site checks for adjacent codes, so if you use a code right as it expires it gets rejected. Usually servers will accept the code immediately before and after the “current” code.
I don't think that was it, I was giving it plenty of space on either end when trying the codes (I've run into that problem before though).
In any case I just tried again and it's working as expected now. Maybe it was just a weird blip or user error on my end.
There’s definitely room for improvement on flexibility
Works for me. My first thought was the time was off on your device, but if everything else is working, that likely rules it out. Did you try regenerating the OTP seed/QR code from a different device?
The Bitwarden desktop app on my PC and mobile app on my phone were both generating the same codes, so I don't think it could have been time related on my end. At any rate I gave it about half an hour and tried again and it worked for me right away. The seed it was giving me on the enable-2fa page didn't even change from before, so whatever the problem was it either fixed itself or I managed to avoid whatever user error was causing it to fail the first time around.
I too run into this issue occasionally, but it never persisted long enough that I felt the need to disable 2FA. I simply wait until the code expires and then use the new one.
I can't comment on why this is the case. My first thought was the same as @teaearlgraycold but I ran into this issue even when the code I was entering had more than 10 seconds to expire, so it beats me.
The server's clock could just be many seconds out of sync with your computer's.