If you are not getting an error then typically this means you have RLS enabled and don't meet RLS for the select policy. Next.js also does caching in many cases which can make it hard to test if you change things on the server after it has cached. If you find you have an RLS problem and fix it you may need to figure out next.js caching or change the query filter so it does not get cached in order to test.
Probably not, but don't see it hang in storage like this typically (versus all fail). I'll add your ticket #'s to the informal queue we have in discord.
Can you restart from general settings?
If you have feedback for Supabase on this then either supabase/supabase issues for docs or supabase/cli github as related to the CLI.
Sorry, I don't use the CLI so can't comment on that. But If your data is gone, all you can do is get a back up. If there is something unclear with the CLI process then generate an issue in supabase/cli or leave comment here, but these are not normally monitored by Supabase staff.
I see a bit of info there is supposed to be a warning about it removing data. If I read this correctly it does a db-reset. https://github.com/supabase/cli/pull/3635 But I don't use migrations so could be wrong. If you don't have a backup then only way would be to go to Pro for min one month and get the last daily backup which even though not documented every user that has done it says they are there.
You did not drop your ticket # . I have no guesses as to why that would happen as pausing does not delete projects and Supabase does not either. Did you have any team members on your account? You could also try the dashboard from another device, but doubt that will matter.
You need to find the account that has them. Do you have emails sent when they were paused? Did you use Github to signup? You can drop your ticket # here and I have an informal path to try and bump it for situations where it has been awhile. Nothing you can do directly.
If not in use your projects are paused, not deleted even after many months. Are you sure you did not create the projects with Lovable/Bolt/Vercel or similar? If so they would not appear in a Supabase dashboard. Contacting support would be the only way to get someone to look at your account.
Yes the trigger function by default will run as authenticated role if that is the user role that did the update. If done from SQL then you might want to add code to check for Postgres role if you want that to update those columns. Trigger would only be on the update and if the code is simple then no it won't add much overhead. It is very common to have trigger functions on table operations.
I would add an before update trigger function and set new.validation_date = old.validation_date. Then in the function code do a check if the user is a validator or not to do that. Do the same for other columns you want to make sure don't change.
You will need to contact support.
Sorry you said blocking production... It is not what I would call common but has seen an uptick here and discord the past couple of weeks from a couple a week. Mainly wanted to make sure you were not using pause/restore instead of restart. I added your ticket to our informal queue an employee monitors when he can. All he can do is move it to infra team queue. You should get a follow up email.
Why was your production plan paused so you had to restore it? You should never Pause a production instance.
It will not resolve on its own typically and needs support.
You will have to wait for support. How long has it been? Free or Pro? We have an INFORMAL escalation path in Discord for projects in such states.
Not really clear what you are referring to or what Google has to do with anything. I assume gmail means your email account is with gmail. It really should not matter who it is thru though for the Supabase dashboad. What sort of issue are you having with your Supabase account?
You will need to generate a support request if you want someone from Supabase to look at your project. What is your full url you are using (masking password and instance (although you already posted that I guess)? Under the Database tab then Settings in the dashboard you can see if there are any bans applied to connections.
What is your login issue? Did you try another browser/device/vpn to rule out a known state issue? You can drop your ticket # here and we have an informal queue in Discord one employee monitors to get project down type issues out of general support queue.
If it is Bolt Cloud then that is managed by Bolt and there is no Supabase direct dashboard for it. You would need to check in their dashboard (if Cloud) or in your Supabase dashboard if not part of their cloud and see if the project status is good or the project is paused.
What does lost access mean? Can't log into dashboard? Blocked for over usage? Project down? Supabase does not monitor here regularly so either post more info to see if a user can offer suggestions or contact support.
Pretty sure that has been supported for quite awhile now.
The team does not normally monitor here. You also posted this on Github and I bumped it to an informal queue we have with 1 of them for project "down" type issues.
I would generate an issue in https://github.com/supabase/realtime/issues . Chances of a dev seeing this here are slim. I've not encountered this before (but I assume the connection will be lost in background and shut it down on invisibility before it errors).
Many users have upgraded to Pro (1 month $25 minimum) and say 7 daily backups are there from while free.
There is a management API issue right now... https://status.supabase.com/incidents/p78yv2qzjm7d
If you can't go back to github then contact support. I don't believe you can switch to email/password if you signed up with Github. support@supabase.com
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.