Threads
Loading user profile...
Have you tried turning off the data api, waiting for a short while and then restarting the project?
Have you got any high usages for any of the services?
Is the project ref definitely being spelled correctly? I've seen this issue before when that has a letter missing or transposed with another letter
1. Yes that form is probably the best thing for what you are looking for, i'm sure you will get redirected if it's not though 2. Tickets are associated with orgs when you file from the dashboard https://supabase.com/dashboard/support/new 3. See form above or email support@supabase.com 4. See form above or email support@supabase.com
You should check that 1) You are not using a password with special charachters 2) You are copying the password exactly as shown and during copying/pasting nothing weird is happening like spaces. If both of those things are fine then you can try reseting your database/instance and if that doesn't work then filing a support ticket
This might not answer all of your questions but you: 1. Can create new roles with the outlines permissions judging by https://supabase.com/dashboard/project/_/database/roles?new=true 2. You can also modify the role in the SQL dashboard to have properties like noinherit https://supabase.com/docs/guides/database/postgres/roles 3. Anything that has _admin at the end is usually a platform role that you can't modify it nor can you modify any of the resources they own/created. Likewise any resources owner by supabase_admin be it schemas/tables can't be transferred. I think things in public might be fine. As for the rest of your points, i'm not sure. Perhaps someone else might know
For what it is worth, i just ran this against my own project curl https://api.supabase.com/v1/projects/<project-id>/database/query/read-only -H "Authorization: Bearer " -H “Content-Type: application/json" -d '{ "query": "SELECT * FROM public.orgs LIMIT 10;" }' and had no issues getting results so i would check that the way you generated your token is correct and that the curl request has no formatting issues
Did you use https://supabase.com/dashboard/account/tokens to generate the access token and did you set a preset of read-only <img width="789" height="944" alt="image" src="https://github.com/user-attachments/assets/092c4b0d-1a13-4bb7-8842-56d3a09adeb0" />
If there are no docs to answer these questions then it's unlikely a team member will stumble upon this to answer these questions. I would file a ticket to Supabase support if you haven't yet
how are you connecting to it and what is exact error you are seeing?
Have you turned on Database Webhooks in the integration section https://supabase.com/dashboard/project/_/integrations/webhooks/overview
I appreciate the frustration and i think silentworks has already spoken to you on our discord and mentioned that weekends can be quieter but hopefully support can get to you soon.
So judging by this https://supabase.com/docs/guides/database/postgres/column-level-security this is expected behaviour. You can set table level privileges and column level and the more general privilege always succeeds so it makes sense that granting select on public.credentials would lead to mean every column succeeds. Back to your initial issue about why insert fails, sometimes you also need a select when doing an insert, this guide explains it better https://supabase.com/docs/guides/troubleshooting/storage-error-403-forbidden-new-row-violates-row-level-security-policy-on-upload-a94384 but this make be the reason you are seeing some issues now. What does your javascript look like at the moment?
Support likely won't be able to give out that information just based on the URL, my best suggestion would be to see if 1) Any team member could have transferred the project to somewhere else 2) If your project was definitely under that email 3) check if started the project with another service such as lovable/bolt. Also check for any emails about that project across all of your accounts.
Please don't use AI generated responses without first doing a check. @fc200490-sketch SEV-1 PRODUCTION on a ticket does not do anything as far as i have seen but your data likely is intact but will require support to fix it.
I think that if you have filed a support ticket then the best thing that you can do is to wait for them to get back to you but i would caution that for free it can take a while.
Support is the best place for this but note that Supabase has said that accounts cannot be recovered that have lost MFA <img width="786" height="123" alt="image" src="https://github.com/user-attachments/assets/f5d3dd48-960d-49f3-9c6e-caeca89f6dca" />
This is due to an incident that should be resolved by now https://status.supabase.com/incidents/vfb32z24wt64
you would be an owner of that project on your new account so nothing would happen to the project is that was you questions?
Fixes are currently being rolled out. If you are getting issues still then it's likely it just hasn't reached your project yet
Usually you cannot login with email/password if you have started using Github. If you are sure you are in the right account then is it possible someone removed your access to the project? That auto response for free is given to everyone, they usually aim to respond to all queries but the account team has also been busy as of late
Have you got your support ticket to hand? When did you submit it? Did you get an email coming back saying that your ticket was removed to the right queue? The account team has been pretty backed up recently so that probably explains the issues you are seeing
Self hosting on a VPS is always an option
Will have to wait for Support on this. You should get a ticket back within 8 hours or so telling you you have moved to the infra queue.
An alternative approach is to create a new Supabase account with your desired email. Make that account a project owner and then delete your old account.
nothing that comes to mind, you could try a database or project restart from https://supabase.com/dashboard/project/_/settings/general, not sure if that will clear this issue though.
I think you already messaged the discord and we resolve it that you can create policies from the SQL editor for storage.buckets. Here is a doc with some examples https://supabase.com/docs/guides/storage/security/access-control
If you are in us-east-2 then you may be affected by this https://discord.com/channels/839993398554656828/1409892722474614814/1537760632277835797 which the team is resolving
I spun up a project in your region and did a quick connection test and it seems to have worked so i don't think it is a region wide issue. I have seen some reports on discord that point to issues with the project itself i.e stuck, paused or inaccessible in anyway from the dashboard. What are you using to connect, i only tested on https://piehost.com/tools/postgres-tester
I don't know the answer to 1) and 2) but i personally haven't come across any functionality for custom certificates in edge functions. 3. I don't believe that egress IP's can be stable. Here is a Supabase article on that along with some suggestions https://supabase.com/docs/guides/troubleshooting/why-supabase-edge-functions-cannot-provide-static-egress-ips-for-whitelisting-3d78b0 4. The maximum secret size is 48kib https://supabase.com/docs/guides/functions/limits so you should be good on that
Could it be a network/firewall issue where it treats options different to GET requests? if you use a vpn or different network do you still get the issue?
Which url in particular, the one for your project should be available on the home dashboard above status <img width="175" height="243" alt="image" src="https://github.com/user-attachments/assets/82d9198e-698f-43f5-8317-b0444cd1c4b3" />
interesting concept, in the discord we have a channel for showcase if you want to share there and also we have a casual wednesday gathering where people present projects/stuff they are working on
Hey there, unfortunately deleted projects cannot be recovered.
Did you create the project with Supabase directly and not any of the other builders/tools such as verce/lovable/bolt etc. If so, you'll probably have to reach out to support.
Does it work for the publishable key?
File a support ticket, there was another issue on reddit i responded to and suggested restarting https://www.reddit.com/r/Supabase/comments/1v11ze6/comment/oyuev3g/?context=1&screen_view_count=2 but it appears it was not persistent
A few other users have reported similar issues, you would have to email support@supabase.com to get it resolved
Usually you cannot just switch from Github to email without intervention from Supabase so it seems like you are in a seperate account. If your Github account has been locked off then email support@supabase.com from the old email that was being used and they should be able to set you up with email/password for it
You would probably have to reach out to support and file a ticket to get a change like this through
Strange, is this error the same if you log into a different browser/device or use a VPN. Could be a dashboard state bug
You should probably file a support ticket (if you haven't already). Are you the only developer on the project or could another team member have removed your permissions, was this a project created with lovable/vercel/bolt, are you sure you are in the right account (if you have set up multiple)
For a lot of these AI tools, Supabase does reccomend 1) Don't connect to prod 2) Only allow the LLM to do read-only (mainly to avoid situations like this) and then run executions youself ![Uploading image.png…]()
I would also suggest posting this in Supabase discord as there is a jobs channel in there which might also be helpful and potentially more active than this?
changing regions is not something that is possible in Supabase at the moment, you would have to reach out to support to get answers to these questions. Tokyo and Singapore are next to each other on the region selection , are you sure you didn't mistakenly select Singapore? That would make more sense
I looked into it and the only user who had a similar issue said he fixed it by restarting the Database which i caution has been having some capacity issues recently https://status.supabase.com/ so worth bearing in mind. It could be something related to the instance. Besides this reaching out ot support seems like the next step
I'll place this ticket in an informal queue just to make sure that it get's picked up as pro. Like Gary said above though, support is busier than normal
In what way is it unhealthy? Can you check your observability charts and see if there are spikes? Which services are affected? Is it possibly related to any of issues on status.supabase.com?
Yeah each branch is in effect a separate database/project so the passwords will be different.
Hey there, i searched inside of the discord and couldn't find any messages that mention either of those tickets. Have you got a message yet saying that you have been moved to the infra queue?