GaryAustin1

Supabase has no other pricing options to be in response to your "let me know if any lower cost plan". You put this in contribute to Supabase versus Feedback. Best to use the feedback in the dashboard with suggestions. This has been requested in the past and I'm sure they know users are interested in such a plan. I have no idea the break points they could eliminate to justify more compute, more egress, backups, better support, edge function limits, etc. But there are lots of parts in play.

Are you sure you signed up with email/password and not Github? If Github then email/password won't work. Is the email on the account the one you are checking and did you receive emails in the past from them? Otherwise support@supabase.com but expect a long wait for the account group if it has to go there.

I added to an informal queue one employee checks every once in awhile to make sure email tickets are marked Pro and to make sure in right internal queue.

Did you create it thru the Vercel side? If so then there would not have been a supabase dashboard directly for it. Also if the project is running, then it is in an account. You need to try and find the email associated with that account. Did you check for emails and compare to the account setting email that was picked up from Github? Have you changed the Github email? Account support will be a long time right now from Supabase and this is almost certainly you are in wrong account unless you have teammates on that org.

This usually means you did not use Github before or your primary email has changed in Github. If the email does not exist in Supabase Github login just creates a new account. Check your emails from Supabase in the past and compare to the email in account settings. Maybe you logged in with email password or you used Vercel/Bolt/Lovable to create a supabase project thru them.

Not sure what the person answering is up to but they have no inside info and appear to be using mainly AI to answer. You should never try and pause an unhealthy project if you need it as chances are high it will completely lock up. Burst disk i/o is the usual issue for this. Make sure your app is not looping on REST API errors. This can keep disk i/o burst from replenishing which happens over 24 hours slowly. You have to try restart occasionally or wait for support to restart which if Free could be several days. Another option is to go Pro and upgrade the instance which almost always solves the issue and would get you faster support if not.

This almost always requires support which will not come from Github. There was an issue in US-east which might have been related... https://status.supabase.com/incidents/ctvf19frbkw4

I think you also posted in Discord and I responded there. No one from Github or Discord can check your project, you would need to contact support for that. I gave you some things to check in Discord.

I don't have suggestions on a workaround but Supabase custom oath is ES256 only. Check with an AI and search on LINE/Supabase would be my suggestions if no one else comes along with a work around.

You'll have to wait on support then. Not sure how that would happen if you were the owner.

Sounds like the org was in their account and you where not owner but admin or something? Is the org still in your account?

There is a process in account settings (upper right). It will send an email to both emails to confirm so do it before you lose access. The account stays the same.

You will need to submit a support request at support@supabase.com. The account group is very backed up right now so could be a week.

I can't confirm anything about the Mangement API or their behind the scenes processing. I have no idea of internals of the management API as a user mod.

You will likely need to follow up in support on your ticket. Github is not monitored by staff regularly for project specific issues. Do you have grants applied for anon, authenticated (not authenticator), service_role per the custom schema docs? I would expect a privilege error though if those are not there. Anything useful in the PostgREST logs?

This normally means you overloaded the database. Check disk i/o and look for disk burst warnings also. If your app goes into loops retrying on error this is a very typical system after an error or two the system gets pounded with retries for the API including Auth. When this happens even restart will not have enough disk i/o to come back up. Stop all API access and then restart. Note disk i/o burst slowly improves each hour for 24 hours if not taxed. Upgrading instance size if very common way to address if you are not sure what to reduce API/SQL wise to reduce load. Check the API Gateway log and charts to see if you have an influx of requests.

Clearing restrictions can take 24 to 48 hours. No one from Github can escalate this. Support is slower on weekends, but this is a days type thing, not hours.

If the project is running (not paused) then you almost certainly are in the wrong account OR you have team mates on the org and they moved it. If you use Github to login for the first time it creates a new account automatically than may not be associated with the email account if you used email/password. If Vercel then the project might be thru their dashboard. Note that if the project is Paused it will still show up and is not deleted.

Also you are sure it is on that particular SQL? You can't use 'ALTER TABLE your_table_name ENABLE ROW LEVEL SECURITY;' for instance as Postgres can't alter realtime tables, just add/change policies.

Right. Hence the suggestion to file an issue in the CLI repository. As it should work. Any other migrations running before this one? I know you said you checked for set role. I'd be surprised if the CLI is bugged here and not getting other reports.,

There are several admin roles you can't become (like supabase_auth_admin) that are only used by Supabase. Postgres is not a super user and not in total control.

As it is not working with CLI I would put it there. The only other thing you can do is file a support request or wait for another user to come along with ideas.

I do not know much about migrations. It is supposed to run as postgres user I'm pretty sure. Any chance you do a set role in the migration? You might post in the CLI repository issues... https://github.com/supabase/cli/issues Are you running the latest CLI? I'm finding no similar reports.

You won't get an answer here to specific info on your project. But you will not get back in before the 27th unless you upgrade to Pro or support were to give you relief. No idea how long support would take and depending on your violation level they may just say upgrade to Pro for the month at least. It should restore within 24 to 48 hours of your billing period starting.

Can you run that SQL from the SQL editor as Postgres? Yes you should be able to add RLS policies but not Alter Table or several other things in the realtime schema. https://github.com/orgs/supabase/discussions/48441 specifically says you can still modify/add policies as Postgres. Not seeing any other reports of this specifically.

Your tickets are probably in the right place. The account group at Supabase we have been told is swamped and we have seen well over a week for requests. There is no other path than thru support. Official documented policy is you can't get in if you lose 2fa. But we (community mods) have seen some Pro users get back in with proof other than email/projectid/keys. Support will ask you for what they need.

Supabase does not cache. But something like next.js can and does sending on your settings. Check in the API Gateway log and see if the request even makes it to the Supabase server. If a request was blocked by RLS you would get no data back and not stale data.

It can take 24 to 48 hours for restrictions to be lifted IF you only violated them for one period previously. No one from Github can touch your projects though. Contact support if after 48 hours.

Considering the link is to a repository by the Author (sole contributor), this is nothing more than an ad for that repository. Will be deleting this...

Can't you have someone on the Team org submit a request with your email info?

You should be clear on what usage you are exceeding. Take a look at the API Gateway info in Observability and logs for your high volume calls. See https://supabase.com/docs/guides/auth/server-side/creating-a-client for use of getClaims/getUser/getSession . NOTE getSession is NOT secure for what you are doing with it. I don't use next.js but you should also be able to look at the API Gateway logs to see if your caching is working.

You say to avoid the Free queue, but then say you are a Free plan... How long has your ticket been submitted? The informal queue is for tickets that might be lost or making sure Pro is not treated as free using email tickets. Right now the account group is taking over a week. Also 2fa restore is not guaranteed, especially with out billing info. Email/project id/keys are not enough.

No idea what you details are as this is normally an English forum. But database error on /token is almost always an auth.users trigger function you wrote failing or an auth hook you wrote failing. You probably can get more info in the Postgres log on the actual error.

I added to the queue. You really should keep sorting if you really are in the right account though because if you are then there will likely be no recovery.

Only support can tell you details. If you drop your ticket # we mods have an informal path to Supabase to make sure ticket is right queue. You really need to look into any other possible accounts it could be in. Vercel created? Wrong primary email on Github? Any chance it was transferred to another org? Paused projects don't get deleted. If your project was deleted there is no recovery for it.

If locked out of the account the only way to support is thru the email. But you are very likely in the correct queue and not a lost ticket so sending more requests would not move you up the queue ahead of others waiting even longer.

Only support/account team can answer those questions. Github and Discord are not monitored regularly by staff and even regular employees can't touch account issues. Right we are seeing well over 7 days and that includes Pro accounts. Free is more than those.

Nothing can happen from Github. Your ticket is in the informal queue but all that does is make sure it is in the account team queue. Only the account team can deal with these.

We heard yesterday well over a week and we have seen some clearly that in Discord. This https://supabase.com/blog/sign-in-with-chatgpt-beta is solving some issues for Github users locked out for banned Github accounts. It might be worth trying with same email you are using for Github. Of course if 2fa is turned on at the Supabase level probably won't help. But if just some glitch... maybe.

Asymmetric keys work with storage. Are you getting storage errors or just RLS blocking? Did you check the storage log? How are you determining auth.uid() is null? How do you know this is related to asymmetric JWTs versus calling with wrong session? Do you have the needed RLS policies for the type of upload you are doing? INSERT, SELECT, UPDATE?

You need to move Postgis to extensions schema where it is supposed to be installed. https://supabase.com/docs/guides/database/extensions/postgis?queryGroups=database-method&database-method=sql#enable-the-extension

Maybe this: https://status.supabase.com/incidents/w5pc099bpkdc

Github is not monitored regularly by the team. How long since you filed your support ticket? Have you got a 2nd email yet about being moved to infra team? I would not expect a response for a couple of days right now as infra is backed up and your are Free plan. Also only the infra team can resolve these type issues which is a subset of Supabase.

Did this get resolved for you yet? If not Supabase added a new log in method using ChatGPT... https://supabase.com/blog/sign-in-with-chatgpt-beta If your accounts have the same email it will login in place of Github.

Official documented policy is they can't let you back in with 2fa lost. We mods have seen though some get back in but not using email/keys/url as confirmation as that is part of what is being protected by 2fa. You just gave away one thing they might ask for and made it public so I assume that now can't be used to confirm. Support is the only way. You say no response, not even ticket numbers? How long? The account group is running over a week right now for many. If it has been several days drop your ticket # here and I have access to an informal queue with an employee for "lost" tickets. But he will just make sure it is in the correct internal queue.

You installed the Postgis extension to the wrong schema. It needs to be in Extensions. You need to unintall and reinstall. Also if you have data back it up and restore for those tables. Search on that table and you will find several hits here and the web including supabase.

Not much info. But I'm going to guess you are doing a REST insert and it either has a .select(), .single() or is a library that automatically returns data. If so you also have to meet a SELECT USING policy.

You can upgrade to Pro and all users that have reported back say they are 7 daily backups there from before while Free. This is not documented or guaranteed by Supabase, but I can confirm it worked for me and many dozens of other users as recently as 2 days ago.

I added your ticket to an informal queue we have for "lost" tickets an employee checks to make sure to the correct group. Most likely you are already in the account group. As I said we have been told and observe they are very backed up. Over a week for some.

You look in logs in the dashboard under Logs, then API Gateway. If this is happening on the Cloudflare side (which I believe that error code indicates) then they may not be showing up. The biggest thing I see online is for people using direct IP instead of full URL, which you believe you are doing correctly. Note Supabase will not likely see your issue here, but you also have a ticket generated which is correct for them to comment.