GaryAustin1

You would have to contact support to change from Github to email/password.

You would have to try support@supabase.com. But their docs on MFA clearly say if you lose your MFA and did not register a back up they can't let you in. Certainly email access would not be enough, but maybe because you are Pro they can look at something else. <img width="1153" height="300" alt="image" src="https://github.com/user-attachments/assets/9fa228fb-69fe-4d56-aa7d-d82dc1ef650d" />

You may not be banned for disposable account but for copyright or some sort of complaint about data stored in your hosting service by others. Contact abuse@supabase.com if they did not say why in your ban notice. The user above WAS using a disposable email so it was obvious.

Are you doing upsert option with the insert? If so you have to meet select and update policies also.

You can stop connections for awhile I believe with the realtime enable setting here: https://supabase.com/dashboard/project/_/realtime/settings but it is a newer setting and I've never used. Normally restart would recover if your instance was the issue. No other reports I've seen.

Project heath from homepage? Errors in Realtime Log? Not seeing much on this error at all around the web.

Try a different browser, device and VPN. Did you signup with Github versus email? Otherwise looks like you already have a support ticket in. How long ago did you file it and are you Free or Pro?

Does your Bolt project still work? This would indicated the project is still somewhere. Sure you did not use Bolt Cloud? Any team members in that Org? Your Org is named the same as your email on the account or you have no Orgs either? Supabase does not delete projects. A team member could delete or move a project. Bolt Cloud projects will not show up in Supabase accounts. Contact support otherwise.

I assume that is because it did not get found as a "down" issue and not known it is Pro. When the employee sees the informal queue and bumps it then you would be moving fairly fast as a Pro user just behind other pro users in whatever group has to deal with the issue. But I can't see when either of those will happen. It is not the weekend so hopefully the employee checks in today.

Sorry no. I'm not an employee so can't see the queue to move it. And even then the first step is the path I took to get your ticket out of the mass of general tickets to the right team.

They don't have a phone. My informal path is thru one employee when he checks a queue we have in Discord and all he can do is get it moved the right internal team out of the general support queue. I have no ability to push them and they have queues that get worked in order as most in those internal team queues need "immediate" help also.

You need to reach out to support@supabase.com It will not get handled from Github.

Drop your ticket # here and I'll try and get it bumped thru an informal path. Did you try a different device?

You will need to file a support request at support@supabase.com if dashboard does not let you file a support ticket. Probably should include both emails involved. Try a different device also.

Check your PostgREST log from Restart. Never do Pause/Restore just Restart from general settings. Check your project health. Check that the API is enabled overall and for each . Check https://supabase.com/dashboard/project/_/integrations/data_api/overview for the API being enabled.

May be waiting on support then. If you just put in the "failing" schema with no others does it work? Does another schema than the first 4 work if you just add that in? Also the log I'm referring to is not the API Gateway log now, but the PostgREST log which won't show operations thru REST but would show any errors after restart schema related. The only case I've seen of this is when there is a bad schema in the list (naming, does not exist, not granted) that ends up not letting either some or all of the schemas work... maybe those after the failing one in the list... but don't remember details now.

Back off to the original 4 then just add the impacted schema. Check spelling and case. Then build back up 1 at a time. I've seen cases where a bad schema in the update list causes it not to work, but does not error when you save. Also check the PostgREST (with a T) log to see if at restart it generates an error about schema not being there.

Double check the API Gateway log for that project to make sure the error is coming from that project and not another one with similar schemas. Check the PostgREST log for errors.

> I am also baffled by this. This is a supabase problem in that it exposes the REST API itself. > > You have to go in and set this up with the following: Dashboard > Project > Authentication > Auto-enable RLS for new tables > Learn More > Click "create ensure_rls trigger" > > That createensure_rls trigger should be default enabled, not opt-in if your database has the REST API enabled. Am I missing something here? I'm newer to Postgres but a security posture like this in 2026 seems meh at best. Probably relevant... https://github.com/orgs/supabase/discussions/45329

> > I added to our queue for an employee to look at to get out of the general queue. There is no way to escalate directly except thru support. > > i'm experiencing this too, kindly help SU-374162 You need to say your plan Free or Pro, when you submitted the ticket and if you received a 2nd automated reply saying being moved to the right team. The INFORMAL queue we have is for "lost" critical tickets NOT for all tickets to get around support.

I added to our queue for an employee to look at to get out of the general queue. There is no way to escalate directly except thru support.

@subhannadeem1 Did you get any follow up email response with ticket # and then about being transferred to a team that can help? If not, and over a day since you sent in support request I have an informal way to try and get it out of general free for critical issues. Please drop your ticket # and when you filed it here.

Not that I know of.

Only support thru the infra team can fix this. How long since you submitted the ticket?

Storage certainly handles the new asymmetric keys. If it had decoding issues it would error specifically on that most likely. It does do it's own verification though independent of PostgREST. If the new JWT's were not working suddenly there would be many many reports. I've not seen any other issues reported. Are you sure you are actually passing the this JWT in the Authorization header?. Depending on your operation the API Gateway log may show more details of the actual JWT being passed in. Also do you have upsert set? If so then you need to meet select and update policies too.

You will need to contact Supabase support@supabase.com . If you could create a new Github account with the same email that is the only "self-serve" method.

Drop your ticket # here and I can bump it thru an informal channel. Although an employee below did catch this, these threads are not monitored regularly by staff hence my message to contact support.

I've not seen this before. Contact support for now as it might be something specific to your instance.

I'm confused. You say in the UI you can see new rows being created. But in the UI you can't see tables. How are you seeing rows being created? Try another browser would be about it. The main case I see on the UI not seeing an instance but it working is it is not in that supabase account but another (maybe of a team member) or in Lovable/Bolt/V0 which would not be in the SB dashboard.

Only support could handle this but they are pretty clear in the docs that if you lose your 2fa you need to have added a backup one as they can't let you in at least just based on email.

We have been told the best email to get support for banned accounts is abuse@supabase.com

> Hello. I'm facing the same issue. I lose the access to my project. Can you please help me? You need to contact support.

You can drop your ticket # here and I can bump it in a Discord informal path we have to them. But it is the weekend and things are slower. It also probably depends on how you can prove you own it if needed.

The link implies you can have two Githubs ... one an Org and one Individual with same email. BUT I don't know that personally. Only Support can help with changing your account.

You are caught up in a purge of temporary/disposable email signups that is happening after several months of notice... https://supabase.com/aup#4-account-and-message-abuse I'm not sure when they added that to terms but likely you are caught up in that. We have been told by support/security that if signed up after the notice was added to terms then you will stay banned. I don't know how they handle if before the change or exactly when it was added.

Looks like you can't anymore and have to go to the new keys... https://supabase.com/docs/guides/getting-started/api-keys#what-to-do-if-a-secret-key-or-servicerole-has-been-leaked-or-compromised This implies you have to go to the new keys...

You have to change the JWT secret to change the old JWT style keys.

You would need to contact support@supabase.com to attempt to resolve this. Not something you can get to on your own and only Supabase staff could resolve if possible.

This is also mainly community answers here like Discord. Support is your only choice for absolute answer but they have told mods and users before it is NOT possible. I think you also got an answer and follow up already on Discord.

Support will need to get to your ticket. But we have already discussed the process on Discord.

I bumped your ticket to an informal queue we have in Discord. Did you get a follow up email on this earlier?

You should generate support requests.

Contact support.

Frankfurt might be better but probably not too much different.

Drop your support ticket #'s here. We have an informal way to bump them in Discord but it it is the weekend so can take awhile.

The employee that monitors the Discord bump queue marked that he dealt with with it sometime in the past few hours. Almost always that is just him making sure it gets to the right team. Normally you would get an email when that happens. I have no other insight into where it is at.

You would have to choose a region that is available and closest to your customer base (or server if accessing SB mainly from server). This is a popular request though... https://github.com/orgs/supabase/discussions/21429

https://supabase.com/docs/guides/troubleshooting/converted-github-account-to-organisation---lost-supabase-account-access-5wsE_1 Some info.

Drop a ticket # here. We have informal way to bump the ticket in Discord that might get it looked at. Otherwise you don't present much info on the exact error. Also try a different device.

Not likely to seen by staff here. Support is the way. Projects though are not just turned off with out warnings in the dashboard or your usage charts showing issues. What does the project home page show for status?