Urgent: Pro Account Lockout (OAuth Bug) — Need Manual Escalation Ticket SU-408313 and SU-408269

[BeniASO]

Hi Supabase team,

I am a Pro tier customer currently completely locked out of my account due to a GitHub OAuth routing error. When I attempt to log in via GitHub, it incorrectly routes me to a new, blank Supabase account setup page instead of authenticating me into my existing Pro organization.

Because I cannot access my dashboard to submit a ticket via supabase.help, I emailed support directly from both email addresses associated with my account. However, the automated system has flagged my emails as Free tier requests.

My ticket IDs are:
SU-408313 (Primary email)
SU-408269 (Secondary email)

Could a staff member or moderator please merge these tickets and manually escalate them to the Pro support queue so my login access can be restored?

The DB is running support systems for a school of 600 students. This is an emergency.

Thank you for the help!

Ben

[GaryAustin1]

Seems like either the account was not under the primary email in the Github you are using.

Are you sure you created the projects with supabase.com and not Lovable/Bolt/Vercel? Those would not appear in a Supabase dashboard.
Check the emails for security/pausing/billing for those projects to confirm it matches the primary Github email.

Only support though can help with this as Github is not monitored by staff for project specific issues.

When did you submit the tickets? Did you get follow up automated emails? Pro or Free?

And then the bad news is the security group that has to handle this if you don't sort it yourself is running many days to week for account log in issues right now.

[BeniASO]

Our supabase DB is still online and I provided Identifying info in my emails to support. It should be easily identifiable. I've had no issues until now logging into our Supabase account via browser. Messing with the connected emails seems to have caused the account to become unglued from github login. From what I understand this is a known issue. My claude desktop account is still connected to our supabase DB and able to interact with it. And the Vercel application that runs off of our Supabase DB is still working. But I have lost all browser based login/management of the DB. As I mentioned, we have a large school depending on this DB for day to day operations. Can it really be that there is no automated method to recover a supabase login if the github connect breaks? A simple email recovery option that bypasses github would be a lifesaver. Instead lost login route just says to login via github - circular. We are in dire need of help. It is frightening to imagine that it could take weeks for support to attend to the case.

…

On Wed, Jul 1, 2026, 12:14 AM GaryAustin1 ***@***.***> wrote: Seems like either the account was not under the primary email in the Github you are using. Are you sure you created the projects with supabase.com and not Lovable/Bolt/Vercel? Those would not appear in a Supabase dashboard. Check the emails for security/pausing/billing for those projects to confirm it matches the primary Github email. Only support though can help with this as Github is not monitored by staff for project specific issues. When did you submit the tickets? Did you get follow up automated emails? Pro or Free? And then the bad news is the security group that has to handle this if you don't sort it yourself is running many days to week for account log in issues right now. — Reply to this email directly, view it on GitHub <#47464?email_source=notifications&email_token=CF7HTHFQOEDHDFQJZK7JQ6D5CQ3V7A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZUHEYDAMBUUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-17490004>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CF7HTHAEJXX35E6TT7OPESL5CQ3V7AVCNFSNUABIKJSXA33TNF2G64TZHMZDCNBVHA3TCOJTHNCGS43DOVZXG2LPNY5TCMBTGQ4DKNZVUF3AE> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/CF7HTHEYS3DMSQJYPW4BZBD5CQ3V7A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZUHEYDAMBUUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM> and Android <https://github.com/notifications/mobile/android/CF7HTHFYZEN6FGDYLEB2SET5CQ3V7A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZUHEYDAMBUUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>