9 people reported
All time, since Mar 11.
MFA prompt never enrolled
“After the GitHub step I land on supabase.com/dashboard/sign-in-mfa (method=github), asking for a 6-digit TOTP code.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/supabase/issues/8770/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Dashboard demands TOTP code for MFA never enabled. After the GitHub OAuth step, sign-in lands on a 6-digit TOTP screen with no backup-code option, persisting across browsers and incognito.
Is this your bug?
File my report- Where
- dashboard sign-in
- Error text
Insufficient AAL: MFA required- Platforms
- Web
- How bad
- Stops work: a core feature can't be used. Most reports say it blocks them completely.
Not quite your bug?
- GitHub login opens empty account5 people
Original reports9, newest first
- Supbase login issue due to MFA code#51254
- Pro account locked out 3 weeks — MFA required but never configured (Ticket SU-445308)#49759
- Locked out of Supabase dashboard — MFA prompt but never enrolled#48980
- Locked out: account requires TOTP MFA that was never enabled (ticket SU-431238)#48326
- Sign in using GitHub requesting a 2FA code that was never set up? Unable to log in.#48088
- Locked out of Pro account — spurious 6-digit TOTP/2FA prompt after GitHub SSO that I never enabled (ticket SU-404571)#47459
- Locked out of Pro account — 2FA/TOTP requested after GitHub SSO that I never enabled (ticket SU-382915)#46339
- TOTP MFA code that I never enrolled#46133
- Cannot access account – 2FA requested but never configured#43679