silentworks

You can use the `--use-pg-delta` flag with the diff command to test it out. You can see it here in the docs https://supabase.com/docs/reference/cli/supabase-db-diff

You have to confirm both if Secure email change is enabled inside of the Dashboard https://supabase.com/dashboard/project/_/auth/providers?provider=Email

What do you mean by default privileges for new entities? Please provide an example of this or a screenshot of the message you are getting.

Have you opened a support ticket with Supabase? https://supabase.com/dashboard/support/new

What does the data in that column look like? It’s hard to tell if you are doing something wrong without knowing the database structure or the column type.

Try from a different browser. Also are you sure you signed up via supabase.com and not a third party site like Vercel, Lovable or something else?

If it’s still using the default templates then it’s normally a syntax issue inside of the custom email template you created. Check the auth logs and it should tell you the issue.

Not really trapped by Amazon themselves because that’s just the nature of authentication systems. No two should be the same.

Yeah you could setup magic link for them and then do a password update after they login in via the magic link

Check your browser network logs to see how many redirects are happening and to where each time. This way you can see if it ever hits localhost at all or just bypasses it all together.

You need to sign into Vercel and manage your Supabase from there. You cannot use the forgotten password feature on supabase.com in this case.

The pricing page shows what’s available on each plan. Free plan doesn’t have backups.

You need a Pro account.

Which means you probably signed up with GitHub or through a third party like Vercel, Lovable or the others.

They will have to reauthenticate as the passwords are hashed differently

Did you get an email from them with the password reset link?

Open a support request with Supabase support. They are the only ones that can help.

You probably didn’t sign up with email/password if forgotten password isn’t working. Try signing in with GitHub.

We’ve had multiple people report that going pro allowed them to get the last 7 days backup. There is no official document from Supabase on this so it’s not guaranteed.

Which forgotten password are you referring to? The one on supabase.com? or the one you’ve implemented in your own project using the Supabase SDK?

The `cookies()` function has been asynchronous since Next 15 https://nextjs.org/docs/app/api-reference/functions/cookies

Ask any AI to convert the CSV into an SQL file with multiple inserts and then just copy and paste that in the SQL editor in the dashboard. It should be much faster too. If you don't want AI to introspect the CSV file you can ask it to write a script based on a sample of your CSV to convert that sort of file into an SQL file and then use that.

Do you mean you can't log into GitHub anymore?

I never install it globally, onl insteall it in the project as devDependency. This way the project can be t locked to that version without worrying about anything breaking on an upgrade. It also means it's consistent for anyone else working on the project as we would both be on the same version.

Signing up again with the same email should resend the confirmation link.

Can you share an example repository with this issue? it will be easier for someone to look into it that way. Also what version of the CLI are you using? and does this only happen on deploy or even when running the edge function locally?

Is on your dashboard

What does your project status look like?

It's normally hours. Also note that Mods are not Supabase staff, so we are only giving information based on past tickets that we have escalated.

There are no ETAs and you are best to open a new support ticket now that you are on the Pro plan as I'm guessing the previous one was opened when you were on the free plan which wouldn't put it in the pro plan priority queue.

What issue did you have when you tried to make a payment with your credit card? was there any errors on the payment page?

I've not seen anyone else on here report this happening before and I've never experienced it myself. Although I mainly work on the web and not in mobile development. You also shouldn't need to be explicilty calling `setSession` as this should be done by itself when you `signInWIthOtp`. If you are manually calling it then something might not be right in your code.

You would have to build this yourself. There is no such built in feature from the SDK itself.

If you rotated the JWT secret then the anon and service_role keys are rotated. Are you still using the old anon and service_role keys setup or the new API keys setup which has a publishable and secret keys?

You would have gotten an automated reply, if you didn't get that then I'd suggest you open a ticket again

Same answer as I gave above

It will mainly tell you which API endpoint is getting hit a lot by requests. You can then see if maybe your code is hitting an endpoint too much as we've seen users DDOS themselves before because of bad code in their React project.

This is a user helping user platform and not an official Supabase support channel. You should contact Supabase support instead https://supabase.com/dashboard/support/new

You should still monitor API Gateway logs and the other logs in order to see what may be causing your system to become unhealthy.

Support is the only way to go. When did you open the ticket?

You will need to contact Supabase support to find that out. Mods are not Supabase staff, we don't have any knowledge of the internals of Supabase nor their projects.

No one here would know why it got stuck except for Supabase support. As Gary stated you need to contact Supabase support. https://supabase.com/dashboard/support/new

Plans are on a per organisation basis and not per project basis. If you change your subscription plan on the organisation that contains only 1 project then it should use your credit for the first month. If the organisation has multiple projects then you should move one to another free organisation in order to not be charged for it.

Restart your project and then monitor API Gateway after to see what could be the cause of the spike. You can find the restart button on this page https://supabase.com/dashboard/project/_/settings/general

There is no one-click restoration. The Postgres command line instructions are the only way.

You should contact Supabase support. But do note that if you didn't set your branch as a persistent branch then that data is likely gone. You should setup a persistent branch for staging and not use preview branches for staging. https://supabase.com/dashboard/support/new

There was/is no google auth with Supabase. If your GitHub got suspended and you didn’t link or write to support during the time to link to a different email then I’m not sure if they can do much. You can try reaching out to Supabase support with the email you had on your old suspended GitHub account.

If you share the detailed error here someone might be able to help you solve it if you are unable to solve it yourself.

Dev console won't show you as much details as the logs themselves.

Auth logs https://supabase.com/dashboard/project/_/logs/auth-logs