Back to threads
Loading user profile...
Please stop posting the same general thing.
You likely have on the default jwt checking which now has to be set to false for then new jwt's and API keys. See https://supabase.com/docs/guides/functions/auth Try disabling that from the Dashboard Edge function UI. If that solves the 401 then you have to follow link I just gave to add your own checking in.
You need to contact support. SB staff does not monitor here for project issues.
They usually do for project outage type things. If you don't hear something in a day drop the ticket # in your Discord thread and there is a way the mod/helpers there can add it to a "lost" ticket queue Informally that 1 employee monitors for project outage type things.
I don't have a path to expedite general support tickets, especially when they have said there is no way several times in the past to this. If you are Pro they should see it within a day.
As discussed in Discord, Support would be the only one with a chance to help (if you don't have a backup) and in the past the answer has be no it is final. But there is no downside to asking them.
You use the supavisor pooler session connection (from the connection tab at top of instance) if you are only IPv4.
<img width="1093" height="411" alt="image" src="https://github.com/user-attachments/assets/d56311d2-7401-405a-867f-75cf6ff1a57b" /> If restart does not resolve it contact back support.
Not sure if you are on Discord also as there are a few similar reports. Please file a support ticket and feel free to drop ticket # here.
https://status.supabase.com/incidents/xmgq69x4brfk There is a blocking by several ISP's in India.
If you use Lovable Cloud then you need to see if Lovable provides you with a database connection string. I see some indications it does not, but don't use Lovable. If it it does then show the connection string (mask instance id) and explain what error you are getting.
Sure Supabase is a shell around Postgres. You can use PSQL (pg_dump) or the CLI to get all your schema structure and data like any other Postgres database. Then restore it to your local database.
There are several active discussions in Discord on workarounds all involving proxy servers... https://discord.com/channels/839993398554656828/1477026509486293132
Supabase does not delete your data. So either you deleted it accidentally, someone on your team did, an AI did or you do not have your tables secured and someone deleted from the outside. Is it all the data or just some? Is the data confirmed gone in the Dashboard? If you go to Pro for $25 for 1 month minimum there will be 7 daily backups there from the last 7 days. Or at least that is what is confirmed by users who have done it.
You should file a support request if you want Supabase to look at your project.
Looks like the employee bumped it for you.
https://status.supabase.com/incidents/xmgq69x4brfk
Are you using Jio as an ISP? Seems to be a common connection. Discord has reports of AP-south-1 issues with that ISP.
What region? Do you have a support request in already?
If you are using Bolt Cloud, that is their own separate Supabase set of instances and won't show in your Supabase dashboard. Bolt docs show how to tell I believe.
It is the same time for both.
Are you in the right account? Do you have alert emails for the project to check? Did you set up the project with Supabase dashboard or is it from a 3rd party like Lovable/Bolt on their cloud? If so it would not be in the Supabase dashboard.
I don't have any idea what Hostinger/Supabase integration is ( don't think there is a relationship like Lovable/Bolt) but if you created a Supabase account you either created it with Github or email. If Github you have to use your Github account to get back in, you can't use an email signin. If you have contacted support but have not heard back (especially if you are paying for Pro) drop your ticket # here and I can get it looked at... but my contact point is an employee and you are now entering the weekend... though he does check in often.
Support would need to handle it.
If you have your ticket #'s I have a way to get an employee to make sure they get out of general support queue IF you have not received more than than the automated replies. Drop the numbers here.
Normally the supabase dashboard runs as Postgres role and bypasses RLS. Maybe you are turning on impersonation in the upper right. <img width="818" height="306" alt="image" src="https://github.com/user-attachments/assets/576c98df-5594-45f5-9aaf-074aab1a181d" />
Probably should contact their support if you have not.
Sorry I don't self-host. One of the new self-host devs Supabase recently hired comes over to discord quite a bit you might make a post there and tag it self-host.
You did not get an auto responder email with a ticket? Or no follow up after that? How long ago did you submit the ticket? Free support can be days. Drop your ticket # here and over on Discord I have an informal path to an employee to make sure tickets for infra issues are not "lost" in free.
Is this self-hosted? If so the right now you can't manage them thru studio. https://github.com/supabase/supabase/issues/10319
Sorry, just a mod/user so can't dig deeper for you. They probably are the only way to resolve it unless you have a browser state issue. Do you have multiple projects? Maybe a mix up on which one they are looking at?
You must disable the JWT verification for new API keys and JWT's. There are 3 spots that might be involved the .toml, the Edge UI has a switch, and then your deploy command (if you don't have .toml set correctly. https://supabase.com/docs/guides/functions/auth
The one thing when REST API appears unhealthy is if you disable it but the UI even though at first looks that way the description says disabled. But that would not impact auth. Any useful errors in the PostgREST or Auth logs? Read only warnings? But this is most likely a support request to resolve as you already tried restarting.
It is a totally independent thing. Your cron task uses either pg_net (which won't wait for an answer at all from the function or http extension that will wait for a response. Http is very bad to do if calling it from an external request to the db as it ties up a connection. I don't know the impact from cron. But say you use pg_net. Then your edge function gets kicked off. When it returns a response (before it goes in background mode) pg_net puts the response in an internal table in the net schema. Your function can then continue to run in background but it can't return any response to the original request, but could make its own DB/REST calls. Http you have to respond in 5 seconds I believe by default, but it has been awhile since I messed with it. The background part of the function is still independent of that.
Everyone on Discord is says it is back for them so far. And an employee says the issue was found.
No reports of issues on the Status page or Discord right now. You did not say how long. If less than a day or two wait and see if resolves (assume this is the dashboard) which you also did not clarify. Otherwise contact support as it does not appear to be a mass thing.
If this has been for less than a day and you are talking about the Dashboard there is a known issue that has not been root caused. It will usually start working again with the browser/device/network it failed on after a day or so. Otherwise what Region are YOU in (not your project)?
500MB/8GB for your database disk. 1GB/100GB storage for files. https://supabase.com/pricing
Still no when. I can't tell if I can use an informal path or not to get your ticket out of free support as it has to have been "awhile" depending on the issue. Although it sounds like it won't do any good if you don't have access, or now if it is for another free account because that implies you are using multiple emails to get multiple free accounts versus the 2 limit. Any way if you say when you filed the ticket and the ticket # I'll bump to my contact. But this is still a single employee that checks when he can, not an official queue as I'm not an employee.
If you can't prove you own the other email you won't be able to get in. Do you not know it or can't access it? You should have received emails while using it or if it was paused. If you can't get access to that old email anymore then my guess is you are out of luck as they can't just give you access to an account based on api codes or urls. But you did reply if you got a ticket # back and when.
It can vary quite a bit. How long has it been? Are you free or pro? What is your login issue? Did you get the default email with a ticket # back?
Sorry for not seeing this sooner. You need to contact support and title "Project stuck Pausing".
I believe this was resolved by the user on Discord and was logging with a different email.
This has always been you are not meeting select RLS for many different reasons (if you get deletes working and nothing else). You have to figure why you don't meet select RLS on the table as it could be no user session when you subscribe to realtime, lost session later, just bad RLS on the table. You provided no info so no one can even suggest where to look.
See the Gemini CLI section here (select dropdown). You don't add project info according to this and will get a log in prompt to sign in to supabase I believe. https://supabase.com/docs/guides/getting-started/mcp But I've not used it for Gemini but it worked for Claude Code and just brought me to a window to signup with my supabase account info if I recall.
I am not an employee. Security sort of seems like the place as you are trying to get access to an account you don't have access to. I can try and have my contact look if it is right place, but he his not a member of support or a group that can solve this issue. What does not respond mean? He says it can't be done? He asked for info and you have not heard back? If the latter the method I have is not really the right way as it is for getting "lost" tickets out of the main support queue not moving another team in supabase along.
Support is the main way. If you drop your ticket # (s) here I have an INFORMAL way in Discord to get an employee to get it out of the Free queue and to the right team IF that is where it is where it is stuck. This is dependent on when the employee checks a queue and he can only get it out of being stuck, not solve it. This has come up before but not sure how they resolve you being the real owner as they may not have your credit card details directly (I think they use Stripe) or a way to confirm you own the card. Certainly they can't just take your word for it.
Sorry. You did not state your region. So less likely. More info would be needed probably for users checking here to help (not regularly monitored by SB staff) or check the Supabase Discord as busy on the issue I linked. Otherwise contact support.
https://status.supabase.com/incidents/9t3fvctpj1hq <img width="803" height="385" alt="image" src="https://github.com/user-attachments/assets/edd314de-e485-4ff4-a861-8d0251e166b4" />
What is your ticket #? I have an Informal way to escalate after that long when the employee checks the queue in discord.