There is no way to get help on Discord for this. You contact support thru the top of the dashboard under feedback.
This was a comment from our informal queue to bump tickets. "Shows "active and healthy." Ticket stuck in support, though." Mainly adding that as our informal contact sees your instance as working.
It is against the rules to shout the mods unless there is a forum issue. You need to contact support to see what might be wrong. Users here can't determine this.
<@472802732215107584> The mods do not have any more power to escalate thru informal channels than ibrahim. We are not employees here.
All we can do is add it to the informal queue that is checked by an employee when he can to make sure it gets to correct internal team.
Try a different browser/device/VPN to rule out a state issue. Contact support@supabase.com via email. You can drop your ticket # here and we have an informal path to make sure it gets seen, but not likely this weekend for that path.
Have you received an email that it has been move to infra team yet? Weekends are slower for support.
There is an auto reply email with the ticket number to your dashboard or direct email request. Check spam and the email. Nothing users here can do for you except an informal bump with a ticket number.
I bumped it. It is up to one or two employees to happen to check and the weekend. But they usually get them moved to the right team in Supabase when they see the queue.
You can drop your ticket # here and we can bump it thru an informal path for cases like this.
https://supabase.com/docs/guides/troubleshooting/rotating-anon-service-and-jwt-secrets-1Jq6yd
US is no problem for cards. If you drop your ticket number here we have an informal path to try and bump it.
Sorry. Nothing users can do for this. If you made that org Pro then you are billed for each project in it unless you move them out to a Free org (of course with the limit still of two free projects outside of the Pro org).
Then you will have to wait for Support to finish the pause or delete it whatever you asked them to do.
Did you try and go to settings and see if Transfer is available for the pausing project? If so you could move it out of the Pro Org to a Free Org.
"under control" means you are running at what would seem like a good average that would not typically put you over. There is no set number that I've seen (certainly not documented by them) on what excess use now would cut you off immediately. But they have cut off people "way" over the quota immediately.
You don't have a whole lot of control sometimes on cached egress if you have public buckets.
It is certainly the safest if this is a production project.
You have to keep things under control now and then when the new period starts you can not go over at all or you will get locked out.
The employee responded back in the queue saying that support is waiting on response from you for 2 days. Implying you should have got an email from them.
Also note you will still likely have a warning about fair use continuing because if you violate again you get cut off.
It can take 24 hours.
Can you transfer the paused project to another Free project? You might be able to not sure.
We have no one to ping. If you are Pro then you would likely get faster support than our INFORMAL path to bump lost tickets as that is thru one employee and it is the weekend.
Or you can make a new Free ORG and move projects to there (but not sure you can move a stuck project or not with transfer).
I don't understand. If you made the ORG pro then you can add another project.
Yeah, it will never recover on its own. Only support can fix it.
How did a live project get paused? That is only for unused projects.
This is a user helping user forum mainly and we can't solve this type of issue. You saw a boiler plate message. Pro will get you faster support but it will not be minutes. Could be hours or more on the weekend.
Your choices are wait until the next billing period, upgrade to pro, or contact support and see if they will temporarily drop the restriction. Note this assumes it is more than a warning and your access has been cut off.
You need to contact support.
Just curious if you are on Pro plan how you paused the project or it got paused?
This is a use helping user forum mainly. BUT if you go to Pro, users that have say their are 7 daily backups there even from while free. Also do not double post issues here it is against the rules.
The most common reason for a loop is retrying on error without any sort of backoff on retries.
Late, so just a quick comment... pgrst_source is likely from the REST API directly and not a trigger. That does not tell you edge function or front end though as both would be the same to that log. Hard to tell if you have alot of requests or long requests without time of the query (average, max). Only you can know if 15M queries is high as the log is over all time. But if this is a recent project then I think you are calling those too much. You can check the REST API log and their is a REST report in Observability tab that might give you more into on the calls. If you are not dealing with 1000's of users then something is wrong with your app. I'm assume . for you is , for the US.
Sorry. Late for me and not sure the context. Probably best to ask new question and show some function code. Heading into the weekend though so may be a bit for answers.
I don't understand the localhost thing. I don't recall ever seeing that in my hosted edge function logs (from the function UI page). I see this on boot.
But it looks like you are running CLI local hosting? I'm not familiar with the details of that.
You would see at least the function start up in the log if it got past that.
This pretty much has to be the JWT flag not being set. There are 3 ways to set it. From the UI in the dashboard (check what that says), the deploy command and then the config.toml.
You will need to contact support@supabase.com. Also you should check your emails for notices from Supabase. You will likely have to prove you own the email versus just have a key. Also are you sure you did not signup with Github? If so you can't use email login.
Oh. You just restarted the database. Restart the entire project. See if that helps.
You can try support, wait if another user has an idea or file an issue in github supabase/storage.
Got nothing else for you
Secret key would rule out RLS so that is a good check.
It is at least once a week we get someone locked out of their Pro plan.
https://supabase.com/docs/reference/javascript/storage-from-upload See react native note
Public still has to meet RLS. But for Expo I believe you have to use specific method to upload.
Yep. That is part of why we mods pushed for someway to bump things that clearly have to be handled by the team, but can get lost in the mass of general free support. Just bad timing right now.
Did it ever work? I would put a support request in. If you remove RLS does it work?