Solved by temporary disabling the totp and 2fa fro...
# infisical-help
c
Solved by temporary disabling the totp and 2fa from db for my user, and then I switched to passkeys.
✖️ 1
p
HI @Cosmin V. Miron (Cosmic Sound)! Glad passkeys got you back in. The lockout happens because once TOTP is your 2FA, Infisical only accepts a TOTP code, there's no email fallback, and GitHub login runs through the same check so same thing happens. Almost always the codes get rejected because of clock drift. They're only valid for about 30 seconds, so if your server or phone clock is a little off, every code fails. Could you please check time sync on both before turning TOTP back on. And be sure to save the 10 recovery codes it shows at setup, that's the built-in way back in if it happens again. Let me know. Thanks!
c
Hi Jake. Will give it a try. Thing is for months used to work without issues. Only on latest releases started to be with issues