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?
I think a look at this page should help debug https://supabase.com/docs/guides/troubleshooting/dashboard-errors-when-managing-users-N1ls4A
Projects that are created with vercel will become deleted unfortunately if you disconnect or delete vercel
Usually you have to give it 24-48 hours for everything to clear. If you still haven't seen things come back then reach out to support@supabase.com
There are apps out there that are doing similar things btw, https://supabase.com/partners/integrations/dreambase this is one example that comes to mind but i'm sure there are others.
For Supabase MCP doesn't it gate behind feature groups instead of individual tools and then also allows restricting to read only? If there are changes to thins like the schema and what not i don't think i would have an impact to say the database tools and how they are used? Please correct me if i'm misunderstanding your point btw
Could you expand a bit more on the invalid logins and not being able to get in? How did you eventually get in? When you did get in, did you see your organisation/project but no database data or did you not even see your organisation/project at all. Could it be that an Ai model that you connected deleted some of the data?
This project looks like it is an internal tool, i'm not sure how open it is for external contributors
For the connection string i think you can make it yourself if you just follow the patterns laid out in the top of the dashboard connect tab provided you have the project id and the password. I'm assuming you have the project id to hand after you create the branch and then running `supabase branches get <project-id>` seems to give you the password? Does that work for you?
https://supabase.com/docs/guides/deployment/branching#:~:text=They%20are%20automatically%20paused%20after,staging%2C%20QA%2C%20or%20development see the section about preview branches for pausing. In terms of having multiple branches it gives you a cost when you create a new branch <img width="553" height="96" alt="image" src="https://github.com/user-attachments/assets/0cf06192-f901-4863-952b-2de087a6bf96" /> and it is per hour so you can calculate from that. I believe the max is 50 and the exact per hour cost will depend upon your instance size.
This is a very hacky way to do it but if you create a function, the end point and slug are created so in your case it would be `send-email` then if you were to go into the edge function -> settings -> name you can modify the name without changins the slug/endpoint so i think you can change the name to `Sends transactional emails after user registration` but invoke it as `send-email`. Though this might make things a bit ugly if descriptions are very long
https://github.com/supabase/supabase/blob/self-hosted/minimal-config/docker/docker-compose.min.yml this is a link to a docker composed file that is more minimal but you should be able to edit your one to remove logflare
Do the postgres/storage logs highlight anything? There was a similar issue in Supabase discord thread https://discord.com/channels/839993398554656828/1499260918528213012/1499426986957869117 which a user managed to resolve otherwise you might need to reach out to support in order to get a resolution.
Yeah i think that is part of the standard functionality. You should be able to do persistent branches if you would prefer that on merging it does not remove the merged branch.
Judging by this https://supabase.com/docs/guides/platform/migrating-within-supabase/dashboard-restore it does mention ```The backup file will be gzipped with a .gz extension. You will need to unzip the file to look like this: backup_name.backup``` and from there i think you run the backup. Did you try and target the gz file before unzipping or are you saying that backup_name.backup did not help much?
Are these users using auth tokens signed by the old JWT perhaps or have you not revoked the Legacy key yet as an option? Sometimes when auth get's into this state you can try resetting the project to "force reboot" or reach out to support to see if its an infra level issue
Sorry what is the issue you are seeing, i can't make out the error from above. Did you intend to attach a screenshot? Also if you are migrating away from lovable cloud, it is not so easy to do that.
If this was working before then you should leave an issue on cli but i'm wondering about the the use of `new URL` instead of just doing `Deno.readTextFile`
wouldn't your custom SMTP have logs?
Based on what you are asking for could you not use an auth trigger https://supabase.com/docs/guides/database/postgres/triggers to populate any information that you need when an auth user is updated e.g. `auth.users.is_confirmed_at`
Could this be a vpn or network related issue? Try using a different network like a phone hotspot to see if it gives the same error
What is service a in this example? Are we still working within the same app context or are you using different schemas for different frontend projects?
This seems like a state bug issue that users occasionally run into and is not that reproducible. You could try using a different browser/device/vpn or you could try signing in with github/google. This would link your accounts