Unable to access Supabase Dashboard via GitHub login - Error sending confirmation email

[kd066202-code]

Hello Team,

I am unable to access my Supabase Dashboard.

Issue:

After selecting "Continue with GitHub", the login process fails with:

"Error sending confirmation email"

In some login attempts I also received:

"OAuth state has expired"

Troubleshooting already performed:

Verified I am using the correct GitHub account.

• Re-authorized Supabase in GitHub.

• Tested Microsoft Edge.

• Tested Chrome Incognito.

-Tested direct project URLs.

• Cleared browser sessions and retried.

• Important observations:

• The project is still active.

• The application connected to this project is fully functional.

• User authentication works.

• Admin authentication works.

• Database reads and writes work.

• project creation works

• Only dashboard access is unavailable

Because dashboard access is unavailable, I'm currently unable to -

1. Access SQL editor
2. Run database migrations
3. Manage authentication settings
4. Manage project settings

Has anyone experienced a similar issue or knows how to recover dashboard access?

Thank you.

[k1ng-arthur]

I had a quick look in the discord to see if there were any similar issues and the one case that i have seen was because they had multiple emails in Github (notification/primary) and some of them was not verified?

[fluxforgeai]

The unverified-email reply is the likely cause, and there is a second one that produces exactly the same error: GitHub's "Keep my email addresses private" setting. With it on, GitHub hands Supabase a users.noreply.github.com address, and the confirmation email it tries to send to that address can't be delivered.

1. GitHub → Settings → Emails. Verify every address listed (resend the verification if any shows "unverified"), set the one you actually read as Primary, and for the duration of this fix untick "Keep my email addresses private". Save.
2. Sign out of supabase.com completely, clear the site's cookies or use a fresh private window, and retry "Continue with GitHub". The "OAuth state has expired" message is usually just the leftover of the earlier failed attempt.
3. If it still fails, open a support ticket with the project ref and your GitHub username; while you wait, nothing in the app depends on the dashboard — the API keys don't expire because you can't log in.

Once you're back in: Organization → Team → add a second owner that signs in with an email address and password, so one broken GitHub login can never lock the project again. Put the recovery codes somewhere safe.