GaryAustin1

As it it says that is for new projects or projects that might have been restarted or upgraded. I would not wait on that issue resolving to help with whatever you are seeing. Github is not support though and no one here can see your project.

If you are Pro you have 7 daily (not pitr as that has to be on first) available. If you are Free, many users have gone Pro and their are 7 daily backups there from even while free. Not documented, but seems to work.

You have to wait on support for this. I'll bump your ticket though to an informal queue the mods have in discord for such things.

You'll have to wait for support to answer but they have told us no. Pro plans are no different on deletion. This assumes you really mean the project and not just the data in the project. If you deleted tables in the DB then you might be able to go Pro and their will be backups for 7 days available. BUT if you deleted the project then those backups are deleted too.

RLS is supposed to be on auth.users and supabase_auth_admin owns those tables so does bypass RLS even with BYPASSRLS off. RLS IS NOT the issue on auth.users... <img width="563" height="478" alt="image" src="https://github.com/user-attachments/assets/9f19be67-2233-4bd7-824f-6550c4ad527a" />

Did you check your usage and database observability logs for over capacity? Disk i/o burst in particular can make a project unhealthy and restart will not work right away as it takes time to replenish. This is particularly true if you have an app doing looping error retries without backoff. There is also infra issues that could impact restart and upgrades right now so options to resolve are more limited. See the status page.

I have no way of knowing. We (user mods) have heard that the security group that handles this is very backed up. I've added your ticket to an Informal queue we have that makes sure the ticket is in the right queue. But it can't speed it up if it is. Have you been working on getting your Github account back with same email also?

Support is the only way and you have a ticket in the system.

Check your emails for the one with the signup confirmation. Support is the only one who could send an email out to that the email for the project and they certainly won't tell you the email based on url or api keys (even service role) as those are public or could be leaked.

You should get this info to your ticket thru support. I have no idea if they will look here or not. Although I did link this discussion. They normally go on tickets internally.

Supabase is leaning towards this being tied to the current general capacity outage. I'm not sure how that would have impacted running projects, but certainly at the point you start upgrading or restarting you could be impacted. I'll leave it to them to follow up. Good luck.

There is no escalation path as right now this security group is overwhelmed we have been told and working the same type of issues. We are seeing user in Discord at a week on this. The Pro was more that billing might give them a way to check. I just caution again though their official policy is you can't get back in if you lose it.

"your side"... I'm not a Supabase employee. I have flagged this because of a couple of other Discord reports thru our informal path to them. So it is up to support or someone to see my Slack message to start working the issue. Seems like either DNS or something in the DC there as close to 1/2 dozen live projects down and that is NOT the status report issue which is just upgrade/downgrade type things...

Then support@supabase.com

Do you have a support ticket generated? If so drop it here.

Why would you resize down from small to micro? If the project shows the correct size though I would think you got thru the capacity "gauntlet". You need to make sure your app is not continuing to hit the database also. I've seen cases where user code does loop retries with no backoff. This will pile up with a wall of requests that eat up the disk i/o burst for any of the nano/micro/small projects so they never come up.

Is the admin page the Supabase Dashboard? Try a different browser/VPN/device.

As I answered you on Discord only support can handle this if at all. They specifically say you will not get back in... <img width="1051" height="242" alt="image" src="https://github.com/user-attachments/assets/544e9cf2-fc87-45e6-9169-44fe9ae7948c" /> But I have seen them in the past help with verification for Pro accounts or with non public info other than email (which is why you have 2fa...). Did you get a ticket # back? If not check spam. When did you submit this? Free or Pro?

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.

For everyone in this (or similar) locked out states from Github issues, real 2fa issues, false 2fa issues, etc. it is urgent. That team is very backed up. I have no idea for how long or if it is getting better soon as we don't have a view inside Supabase. I added your ticket to the informal queue based on you saying you have an older email submitted even though your ticket # is too soon for us to normally bump. Only thing I did not see on your list for "false" 2fa (versus you lost 2fa which is a different story) is to try another device.

So you don't have ticket #'s from earlier? Also even if in the informal queue (once it gets seen there), we have been told the security team at SB is VERY backed up. I would not expect a few days.

You have to do a full project migration. https://supabase.com/docs/guides/platform/migrating-within-supabase/backup-restore

Seems like it is where it has been for ages, unless it was in another spot also... <img width="1057" height="623" alt="image" src="https://github.com/user-attachments/assets/fce29c65-4426-45bc-9565-6806d2cf5ba7" />

If it was Lovable cloud then there is no Supabase account for it and has to be accessed from Lovable dashboard.

If you don't have any organziations then this says that github account is not likely where you created it. It probably created a new supabase account with that email (from the Github primary email). So no orgs here: <img width="776" height="641" alt="image" src="https://github.com/user-attachments/assets/5b415a9f-2222-4410-aa32-11b8ecc0b62d" /> Normally Supabase sends emails with security info and updates (or pause warnings)... check your email for what email it was sent to. Likely this project was created with a different email or in Vercel/Bolt/Lovable. Does the project still work? If not then it could also have been deleted. If less than a day you can check the Audit log under your Account settings (top right avatar).

You need to file a support request, no one from Github will be able to see your account. If it existed less than 24 hours ago check the audit log in Account Settings (upper right of dashboard under your avatar). Do you have any other supabase accounts? Was it created in Lovable/Bolt/Vercel? Any team members on that org that might have transferred it?

Unfortunately, Support has told us mods that it can't be recovered once deleted. Also Supabase staff does not normally monitor Github for project specific issues. That is only done thru support.

You will have to wait on support. No one on Github can help with this. When did you submit your ticket and did you get a ticket # back? Did you get a 2nd email asking for verification? I assume you tried another device and network to rule out some weird state issue as you clearly now about Vercel/Lovable type things. I assume you also ruled out github as your login. There is a path for user mods to ask an employee to make sure the ticket is not lost in free support but a few hours is not enough to bump to that. Right now these types of issues are taking awhile to resolve unfortunately.

@cbdoil9481-lab Hopefully support@supabase.com and not superbase.com... That is the only way to resolve this and if you are pro they may not know it coming in that way. If you lost your 2fa you will also have to prove you own the account with something other than email as that is what 2fa is supposed to block. The docs actually say no recovery from lost 2fa. There is also a random but that seems to ask for 2fa when you never enabled it. Try another device if that is the case. As far as urgent this will likely take a day or more based on other user's having account login issues.

@mbozecki I can't check it but will add it to a Discord informal queue an employee checks when he can

I have not done the migration so will only confirm that is the only way. You are not missing some secret way. The migration guide https://supabase.com/docs/guides/platform/migrating-within-supabase/backup-restore covers how to copy the storage data with a js script. Auth should just transfer as password will work. Users will have to login though. 2 is a good idea basically prove you know what to do, don't have steps missing or some config you need to make sure you set up.

I've never seen any documentation or stats. Weekends are for sure slower. You don't say what your issue so can't suggest if users/mods could help you or not. Did you get a 2nd email after the ticket # saying you were being moved to the correct team or infra? If not then drop your ticket # here and we have an INFORMAL queue in Discord to try and find out where it is and get to infra. If already in infra then it is just waiting. If you came in thru email and not dashboard then they don't know you are Pro.

@jamesatFRM Added to queue.

If you had 2fa enabled then most likely you are using the wrong factor/authenticator. If you did not have it enabled, try another device/browser to rule out a state issue. Contact support@supabase.com if those don't work, although if you have 2fa you will need to verify more than your email with them most likely.

I'm pretty sure Supabase creates tables as Postgres. The dashboard calls an admin API for creating tables and they are all owned by postgres not supabase_admin. I don't find any public tables owned by supabase_admin in public schema. This is for hosted supabase. https://supabase.com/docs/guides/api/securing-your-api#default-privileges-for-new-tables-and-functions Also make sure you are up to speed on this: https://supabase.com/changelog/45329-breaking-change-tables-not-exposed-to-data-and-graphql-api-automatically

Also make sure that error lines up with your gateway api log time for the signup and is not some other error (not related). I do see that error in my logs occasionally but it does not hurt anything.

That schema is from using the CLI I believe. It is used to track your local and remote projects based on what I see. I don't use the CLI for this so my instances don't have that table and don't get an error. The auth.schema_migrations is a totally different table. Have you tried a project restart from general settings? Otherwise contact support if you have not. No one on Github or Discord can help look with your actual project internals.

You don't need any special settings to use the Postgres log for errors. <img width="812" height="630" alt="image" src="https://github.com/user-attachments/assets/97724e5d-2617-4510-85f5-04367420d41d" /> There is a severity filter if you need it. Do you have an auth.users trigger function or auth web hook enabled?

That generate always as is what it should be. If there is not email then the column gets set to null with no error. Check the Postgres logs for the exact error. It will likely point to you having an auth.users trigger function failing or an auth hook failing.

Supabase docs say deletion is permanent. Support has confirmed to the mods that it is permanent and nothing they can do. This applies to both Free and Pro. If it was just database or tables then going Pro would be an option.

If you look in the Gateway API log you should be able to see what the user role is in the detail data as decoded from the JWT. I would think if JWT is being rejected you would get a different error. Getting to RLS implies the JWT was handled which ever type it is. Note no one from Github is going to be able to check your project though only support can do that.

You need to contact support so they can resolve this. Upper right of dashboard.

You would not need policies for storage_admin and they would make no difference for API calls. You are either not the role you think you are, you are needing a select policy if doing upsert, or your policies are not on storage.objects but on the bucket table. There might be other things but those are what come to mind. Check your storage logs also. There is no known bug in this process.

Here is a user who uses supabase to teach students mobile apps and OTP is needed. Now all students have to setup SMTP provider. https://github.com/orgs/supabase/discussions/47114

If you still have access to the Supabase account then create a new account. Invite that account to your existing account. Make owner of orgs and transfer projects or drop original account as owner. If you don't have access already then support@supabase.com with both emails.

You get a credit for the unused portion. It is the TOS. https://supabase.com/terms#5-fees-and-payment <img width="1689" height="200" alt="image" src="https://github.com/user-attachments/assets/8f23c4ac-b9d6-4005-a8f1-5f769122ed9b" /> https://supabase.com/docs/guides/platform/credits https://supabase.com/docs/guides/platform/manage-your-subscription#credits-upon-downgrade <img width="1145" height="153" alt="image" src="https://github.com/user-attachments/assets/7be26bb4-ad1d-4707-91ed-b7f24b75fe00" />

If my suggestions don't work then contact support@supabase.com while you wait for the OP to say what they did.

Try a different device, network and VPN. If you are getting a banned message then contact abuse@supabase.com. Otherwise if those don't work then contact support@supabase.com. You won't get account specific help on Github.

That was why in my first post I said... "If you deleted tables and not the project" ... Backups get deleted with the Project. Unfortunately Supabase Support has told us mods that there is no recovery of deleted projects.

Not sure what is gone... project, tables, backups? When did you start the project? Were there 7 daily backups there? It is not documented but many, many users have said they are there (and I've seen them when I made a free org Pro. Did you restore an older backup and the tables are missing? If so then you deleted them before the backup or are in the wrong project.