Https-ksperez

Hi, how are you? Could you let us know how you're handling the connection process? For example: 1. Via API 2. Via project URL with an anonymous key

Hey MRebirth! 👋 Garyaustin is right 🤭 Since the deletion is failing even when you try it directly from the Table Editor (which normally bypasses RLS), this is almost certainly a Foreign Key constraint blocking the action. PostgreSQL is doing exactly what it's supposed to do: protecting your database from having "orphaned" records (like a task that belongs to a user who no longer exists). Here is how you can properly solve this depending on what you need right now: 1. If you just need to delete them manually right now: You will need to design and execute a SQL script to clean up all existing dependencies first. You essentially have to go in reverse order: manually delete their tasks, then remove them from any teams, then delete their public profiles record. Finally, once there are no records tied to their ID, you will be able to delete the user from the auth.users table without getting the database error. 2. How to handle this from your application (The scalable way): Writing a massive script to delete dependencies one by one every time a user leaves is a nightmare. The absolute best practice in Supabase is to update your Foreign Key relationships in your tables to use ON DELETE CASCADE. By doing this, you are telling Postgres: "When I delete this user from auth.users, automatically delete their profile, their tasks, and any other linked data instantly." A quick heads-up on executing it from your client: Keep in mind that a user cannot delete their own account directly from auth.users using the standard public client (for security reasons). To do this from your app, you will need to create a Supabase Edge Function (using your service_role key) or a Postgres RPC function with security definer. Your frontend app simply calls this function, the function deletes the user from auth.users, and the CASCADE magic cleans up all the related tables in one go! 💚 Hope this helps you set up a clean deletion flow!.

Hey Alex! You are completely safe. Upgrading your Supabase project won't break your existing setup. If by "custom link" you mean setting up a Custom Domain (which is a paid feature), your original auto-generated Supabase URL (https://[project-ref].supabase.co) will actually remain active. Both the new custom domain and the old "temporary" link will work in parallel. This is actually a great advantage because it means your current webhooks will continue to function perfectly fine after you upgrade. You will have zero downtime, and you can take your time updating your webhook endpoints to the new custom link at your own pace! Hope this helps!

Hi, Anandharaj. That error (exceed_egress_quota) means your project has reached the monthly data transfer limit (bandwidth) included in the free plan, which is 5 GB of cached outbound traffic and 5 GB of uncached outbound traffic. Since you’re on the free plan, Supabase automatically restricts the service when you reach this limit to protect you and prevent overcharging. To resolve this, you have these main options: 1. Wait for the next billing cycle: The free way to fix this is simply to wait. Your data transfer quota will reset to zero at the start of your next monthly cycle, and your project will automatically start working again. 2. Upgrade to the Pro plan: If it’s urgent and you need your app back online today, the only immediate solution is to upgrade your project to the Pro plan (starting at $25/month). This will automatically increase your limit to 250 GB of outbound traffic (both cached and uncached). 3. Contact support: As the error message itself indicates, you should go to https://supabase.help and open a support ticket so the Supabase team is aware of the issue and can assist you. 4. Optimize your architecture (Very important): Once you regain access, go to the "Usage" section in your control panel to investigate what caused that spike in usage. This is often caused by repeated downloads of large files from Storage without proper client-side caching, or by inefficient database queries. If you have any other questions, feel free to ask.

Sure, no problem ☺️

I think I'll look over the code on my own, but if you'd like, we can go over it together and you can share your screen with me. Whatever makes you feel most comfortable.

Yes, Or send me a message so we can call on Discord, and share your screen with me. That's another option.

You can compress your project and send it to me as a ZIP file via the internal chat. Don't worry, I'll just review the code. I'll run it through my SupaBase to check for any potential errors, and then I'll send you a summary or the modified project with minimal changes to make it work, and I'll ask you a couple of questions along the way.

Sure, I could help you—no problem.

I share with you this video: https://youtu.be/Gz9bvYybaws?si=8u9W6N1-ZuelbqFn In this video explain that you need to connect Supabase with your app with a .env file.

Where do you have to deploy your app? O is only in the cloud of famous.ai?

Don't worry In the .env

How to find your Supabase credentials: For the Project URL: Go to the Project Overview page when you are inside your project. Right below your project's name, you will see a URL. If you hover your mouse over it, the full Project URL will appear. Copy that. For the API Key: 1. On the left navigation bar, click on the gear icon to select Project Settings. 2. Go to the API section. 3. Look under the "Project API keys" section. There you will find the anon public key. Copy it. About the .env file: Make sure to store these values only in your local .env file. Using a .env file keeps your credentials out of your source code repository (like GitHub). It allows your web or mobile app to connect to the database while keeping the file itself from being uploaded. Since the anon key is public by design and will be compiled into your frontend app, make sure you have Row Level Security (RLS) enabled on your Supabase tables to keep your data safe!

No worries at all! Since Famous.ai built the app for you, you don't need to stress about the technical jargon. You can actually just ask the AI to handle this part for you! Try giving Famous.ai a prompt like this: "Please create an environment file (like a .env file) to store my credentials, and set up the connection to the Supabase endpoints using those credentials." Once the AI sets that file up, it will ask you for your Supabase details. You just need to provide it with two things: Your Project URL Your anon public key (this is what they mean by the publishable key). You can find both of these in your Supabase Dashboard by going to Project Settings > API. Just paste those into the environment file the AI creates, and Famous.ai should automatically handle all those complicated "Headers" and "Endpoints" for you. Let us know how it goes!

I've been there! What I usually do when I can't remember which of my many emails I used to create an account is just search all my inboxes for the company's name (like 'Supabase') to see which one got the welcome or login emails. Hope this helps!

Hi! A 401 Unauthorized error almost always means there's an issue with your API keys or missing headers. Please double-check that you've copied your anon key correctly into your famous.ai environment variables and that your API calls include the proper Authorization: Bearer <YOUR_API_KEY> header. You can verify the exact setup requirements in the official docs here: https://supabase.com/docs/guides/api Let us know if that fixes it!

I am so sorry to hear this has happened. I completely understand how incredibly stressful and critical this situation is for your startup and your clients. As a community member/SupaSquad, I don't have the backend access required to restore deleted projects or access internal backups. Because this is a critical production-level incident, you need to escalate this directly to the core Supabase Support team immediately. Please open an urgent support ticket right now through this link: https://supabase.com/dashboard/support/new When you submit the ticket, make sure to: Select the highest severity level available. Clearly state in the subject that it was an accidental project deletion of a production database. Include your Project Reference ID if you have it saved anywhere (it's the 20-character string that was in your Supabase API URLs). The internal team will be able to tell you if a point-in-time recovery or backup restoration is possible for "funnelway-v2". Wishing you the best of luck getting this resolved quickly!

If you are experiencing any issues with your platform, you can go to: https://supabase.com/dashboard/support/new We are here to help 😊

If you want to check the status of Supabase services, you can do so at the following link: https://status.supabase.com/ Usually, most SaaS platforms have a status page like this. It's necessary to indicate the name of the page and the status.