Cannot login to dashboard — invalid credentials + password reset email not arriving

[rajarshi02bhattacharjee-stack]

Is anyone else facing this issue . Not sure if its related to the auth issue supabase was facing yesterday but I'm unable to log in to my Supabase dashboard since yesterday . When I enter my email and password, I get "Invalid credentials". When I use the "Forgot password" flow, the page shows "Check your email for a reset code" but no email arrives (checked inbox, spam, promotions, all tabs — nothing). (checked inbox, spam, promotions — nothing). I cannot go through the normal route of opening a supabase portal ticket because it needs you to be logged in , i have shared an email to support@supabase.io but since i am on a free plan i am not guaranteed a response. Wondering what other members have done if faced with the issue

[Samielakkad]

Supabase's current status page shows Dashboard and Auth as operational. The July 15 incident was about viewing/managing authentication providers and is marked resolved, so there is not enough evidence to treat this as the same outage: https://status.supabase.com/

The first thing to check is how this Supabase account was originally created. Supabase's dashboard recovery guide says that a common reason for this exact combination (invalid password plus no reset email) is that the account uses GitHub login rather than an email/password identity:

https://supabase.com/docs/guides/troubleshooting/i-am-not-receiving-password-reset-emails-for-supabase-dashboard--cO5yf

Try these in order:

1. Open a private/incognito window and choose Continue with GitHub, using the GitHub account whose primary email matches the Supabase account.
2. If the account came from the Vercel Marketplace, use the Vercel-linked identity or GitHub login. Supabase documents that those accounts cannot use direct email/password login or password reset: https://supabase.com/docs/guides/troubleshooting/email-password-login-disabled-supabase-vercel-marketplace-a7dd36
3. Confirm the email address exactly, including aliases such as +something, and avoid repeatedly requesting resets while testing.
4. If neither identity method works, contact support@supabase.com (not support@supabase.io) from the affected account email. Include the account email, original sign-in method if known, UTC timestamp, browser, and a screenshot of the error. This email route is the official instruction when you cannot access the dashboard.

Do not post a password, reset code, access token, project key, or recovery link in this public discussion.

Because both password login and reset delivery fail, I would test the original OAuth identity before assuming the password or email system is broken. If GitHub login succeeds, no password reset is needed.