You should try using chatGPT with those emails as login. Is the project still running? If so then the good new it is not deleted. If you have teammates on the org maybe they dropped you as owner or deleted the org. If you can't sort the correct signin method then support@supabase.com but expect a very long wait for account security.
If your project is stuck in restore (you don't say your issue) then you need to contact support. You won't get help on individual project support from Github.
This would have to go thru their account security group which is very backed up and unfortunately has been taking over a week. They can't use email/url/keys to get users back in (and docs say you can't get back in) but we have had Pro users say they were helped with billing info. You can drop your ticket # here and we have an informal path with an employee for "lost" tickets. He can make sure you account is at least tagged pro in that queue. There is no escalation on it.
No I can't. Mods have no contact with security team. You can update your ticket. Employees can't escalate with in that team either. You are in time order with Pro users ahead of you. Did you try chatGPT login? It has solved many Github login issues. If it does not work either then that email is not your account or someone on your team moved your projects to another account (would need to be owner).
I can see that it was bumped to the account security team thru the informal process we have with Supabase. The account security team though will likely be over a week (and that is for Pro) as they are very very backed up. You also added more info below I don't know if he saw. Try using that email to create a chatgpt account and log in with that. If your Github account email changed somehow you would get a new empty account like you see.
There is no such thing as Google SignIn with Supabase. If you meant Github then email/password will not work. If you meant email/password then you had to signup that way. Does password reset send you and email? If not then likely not the way you signed up. Did you create your project directly on Supabase.com versus Lovable/Bolt/Vercel? Check past emails from Supabase and then create a ChatGPT account with the same email and try that. Otherwise support@supabase.com and expect a long wait as account security group is very backed up. Far better you try and sort how you signed up. Note if you use Github/ChatGPT and come into an empty account that is then not likely the email you used to signup.
Support will need to look at it. Did you receive a 2nd message yet being moved to infra team? Can you show the exact context of the message as never heard/seen them use that wording before. Could be new. With the outage it should get flagged eventually.
You have a support person tell you that or automation? The account security group is very backed up and can take over a week. Not commenting if a potential bug, but lost 2fa to get back in requires more than email/url/api keys. Email in particular can't be used because that is what 2fa is protecting. Github login is really about the email being used and not the github account itself. We know they get in some Pro users with billing info. Supabase does not normal monitor discussions for individual project issues in general. How long since you submitted your ticket?
You will have to see what support says to your ticket.
Did you get a 2nd email saying you have been moved to the infra team?
@hippi345 This is the correct answer. Only support can solve it without upgrading. On normal overages that reset at start of next period we have feedback that is case by case and not all get relief until the period ends. But this one is a catch 22. They (SB) knows of the catch 22 but have told the mods (discord/here) no solution yet as difficult to separate delete from access in their system. I don't have a feel on relief for this particular issue versus going Pro. Not seen a user comment back here or Github if they got relief. And Discussions are not typically monitored by staff.
Does your project run? If so it is in an account somewhere and you are most likely in a new account created by Github email not matching. Check old emails for the project. Check in account settings for the email in the account. If the project is not running and less than 24 hours check your Audit Log in account settings (under user icon top right). You also mention integration. If you created the project with Vercel most likely there is no direct Supabase.com dashboard and you need to login in thru Vercel. If this has to go to account security to verify you expect this to take over a week. Github dissucsions are not support and not normally monitored by staff.
This could be overload. If you continue to hit the instance with requests (in particular error loops) it can keep restart and pause from working as those need resource. Usually though you get a resource warning or can see issues in usage and observability charts. Disk i/o burst in particular comes up. Otherwise support contact is needed. There are no reported outages, but this is usually isolated to your instance.
So you are using the old email with chatGPT login? That usually works even if Github is linked to the same email. Changing email on Github and getting an empty account does happen. Did you happen to have Vercel dashboard involved in this? That is another common reasons for the message as you have to use their dashboard. Otherwise probably have to wait for support as there email/password option after the fact. Normally the team does not monitor for project issues and this will likely get to the right place and then there is no escalation to move you in the queue. The problem though is if it has to go thru account security team it will be many days to over a week unless things have improved very recently.
Check your past emails for that project, account creation and then confirm the email matches what is in account settings (under user icon upper right). If different you are in likely a new or different account. Github/ChatGPT all sign up a new account if email does not exist. Was the project created on supabase.com or Lovable/Bolt/Vercel. If one of those then they have their own dashboard. Any teammates on the org that could have transferred it? Those all assume the project is still running from your app or REST API. If it is not running then the project being deleted is a possibility but would no expect the "do not have access" for that case. Otherwise waiting on support is the way.
Hopefully this has resolved for you there were several reports it appears. The informal queue is for lost tickets which means days or over a week depending on the kind of issue. There is no escalation queue for individual issues.
You will need to contact their support thru the ticket system in upper right of dashboard under feedback. There is no guarantee they will give you relief. They normally give a grace period to resolve this and if you did not resolve before then are stuck with what they decide. It will not reset at start of next period. I don't have a good feel for how often they give relief for this particular issue.
There is no way to resolve this without going Pro or waiting to see if support will give you relief. It will no reset next period unless you reduced the size before grace expired.
Not a known issue and does not appear in any search. Try a different browser? Does the Transaction pooler show info? It is the same except for port number. This screen? <img width="602" height="870" alt="image" src="https://github.com/user-attachments/assets/6538e3d2-d020-4155-b3d4-a73dcba28533" />
Experience modding here and Discord is support will not modify grants on their schemas or create special roles for you. Postgres role is the only role you have do this or not to use an FK and use the trigger approach instead to add/delete the public table row on auth insert/delete.
It does look like your project is not on the net from a public check of the url. If you have tried restart project from general settings and that does not work then you'll have to wait on support to resolve it. You can use CLI to migrate to another instance if in a hurry, but somewhat painful if you have files in storage. https://supabase.com/docs/guides/platform/migrating-within-supabase
Your response hopefully means it was transferred to the infra team or to a person to check and move to the infra team. But I don't know much about "sam".
Support Infra team has to resolve this. 8 hours is long for you, but Pro support from what I've seen is a day or two for this. No idea on what their current queue times are. There is no SLA for Pro. Here they say TYPICAL (not guaranteed) 1 business day. Mods normally have said 24 to 48 hours in the past for Pro. <img width="531" height="108" alt="image" src="https://github.com/user-attachments/assets/dbf183d7-5622-4780-b212-4f6c6798efc6" /> There is no escalation path mods or general employees have for this. Even the queue I have access to can't escalate, just check and it is not for sub 2 day response. Sorry.
That is way to soon to use this path. Normally Pro tickets get handled before the informal path because it is checked by one employee when they can. There is no SLA for Pro but they say they target 24 to 48 hours. All the path we have does is make sure the ticket is not lost in general support. It is very very unlikely your ticket is lost at this point.
The path I have is for lost tickets basically. Free or Pro? How long since you submitted the ticket? Any 2nd email about being moved to infra. If a couple of days the process I have is not for that.
Not really clear on what is working or not. If the DB is still running then that is good as project is alive. If you don't see the orgs or project when you sign in then most likely you are not in the correct account. Check past emails from Supabase for the project. If the project was created with Lovable/Bolt/Vercel it may not have a Supabase.com dashboard. The other possibility is you had a team member on the org drop you as owner. Not sure how the edge functions 403 ties in though with DB working.
Also note in particular to storage there was/is and ongoing issue around this time. For me it shows as very slow loads getting an error but still loading... https://status.supabase.com/incidents/01M6F2ZNF7YMPS3V144BFQ72BD
If a project restart does not resolve it then contact Supabase. Occasionally this comes up on new and paused/restored projects and support has to fix it. You don't say if this worked and stopped after an event. You also mention storage but you entire project is not responding if that is your real project url.
If I run the query I show where I don't have it set, it returns nothing about db_pre_request at all. I don't know if there is some way you could set it that the query would not pickup. I don't think so, but beyond what I know about it.
```SQL SELECT unnest(rolconfig) AS setting FROM pg_roles WHERE rolname = 'authenticator'; ``` Will return it if set. <img width="399" height="300" alt="image" src="https://github.com/user-attachments/assets/981c9c98-9150-4f2e-aa9f-5eb39f1494b7" />
Github is not support. No one here can touch or see your project. Generate a support ticket from top right of dashboard under feedback. Your 2 solutions are to see if support will give you a temporary grace or upgrade to Pro for a month and delete the files.
I seriously doubt you will get free support to help with this but only they could tell you. If the project is not paused then the snapshot would no longer exist (at least not for "long"). The backup process is well automated, you will not likely get them to constantly delete backups on request free or Pro. Not sure where you are getting a requirement that all backup data be gone right at point of delete including backups. Can't see an app provider in the world that has backups (which you really need) would do more than say "within x days" for the deletion, unless the data is only stored on the user's device.
This is not true. Backups DO exist, just not guaranteed. You can go Pro and you will almost certainly find 7 daily backups from while free. I do not know if they keep them longer (for instance go to Team and get 14 days...)
I can add your ticket to an informal queue we have with SB in Discord for "lost tickets" BUT the fact you are already escalated to infra means it may just be taking that long. Otherwise there is no escalation externally to the support ticket system.
Really should not post your emails here. You will not get help from Supabase from Github to touch your account and would need to contact support. BUT you could set up a new account with your new email. Then invite that account from your old account to be a member of the Org team as owner. Then either drop the original owner email from the new account. You can then also add chatGPT and Github using that same email as primary if desired.
This will have to be handled by Support. They get to these issues for Free but you are behind all Pro and Free ahead of you in the infra queue when you get there. This is not likely an hours thing.
I cannot reproduce this in Firefox or Chrome. Password field goes from red to yellow to green. Try hard refresh of browser. <img width="897" height="602" alt="image" src="https://github.com/user-attachments/assets/a6e6d8e0-b0cf-4c3f-a0c8-c16046549391" />
At the moment if you go to Pro from Free everyone who has (over 100 users) finds 7 daily backups from before while Free). So if you find yourself in this state right now (and for past 2 years) this works. It is not guaranteed (for instance backups were not working) and you should do your own backups for Free anyway, but it certainly is an option if you did not.
Support has always said once they are deleted in that process they are like any other Supabase project that is deleted and there is no recovery. The backups go with the project. Certainly no one from Github could help with this.
No one can help you without some idea what the error is. That could be your app not working and not even involve Supabase. Look for some error messages in your browser logs or Supabase logs if you think it is a Supabase error.
I upgraded a project to latest Postgres and get 14.18 PostgREST... <img width="869" height="388" alt="image" src="https://github.com/user-attachments/assets/dde2b799-fba9-4b6e-b0d5-af81bacbcba8" />
You would check in General Settings for the PostgREST version. It is upgraded when you upgrade Postgres.
Can you get to project restart in general settings? Official support is only thru filing a support ticket. No one from Github can see or touch your project.
You would have to file a support ticket to get account security to help move to email. You can't use email/password with a Github created account. But you can use the same primary email from Github in a chatGPT account and that should get you in.
The SQL editor can create policies on storage.objects. You just don't use alter table method to do it. https://supabase.com/docs/guides/storage/security/access-control#policy-examples Shows SQL examples that work from the SQL editor.
You need to reinstall postgis in the proper extensions schema (default setting). It should not be in the public schema.
You are posting on a 2 year old thread. If you want to contact supabase directly use the support link at top of dashboard under feedback or "?". Discussions are not monitored regularly by staff.
You need to file a support request. Supabase staff is not likely to see this.
This is the relevant doc from Supabase. You could probably also find more info looking at Deno deploy architecture as Supabase edge is their own port of that. When you get notice back the function is deployed the Gateway has switched the pointer around the world for your new function code. No requests coming in will go to spin up old function code or to old functions still alive in their lifecycle. Any functions running though will finish the "task" they are on. This is based on observation and discussion over the years and can't point you to anything else official from Supabase. I am not an employee and Github discussions are not monitored regularly by staff, but they do catch some things.
This would typically be your individual instance is overloaded or having issues. Any warning in usage settings? Check charts in usage settings and database observability. Check project health. No other reports I've seen.