silentworks

People are helping you based on their experience and experiences of others we’ve seen on here. Troubleshooting requires both parties to work together, you should always remember we only have as much context as you give. Again follow the steps provided and give feedback on the results you get and not just blindly dismiss them. The url your provided is incorrect, it’s rather pages.dev than dev.pages. I tested it on my end and it’s working ok, but then again you haven’t stated what exactly isn’t working.

No, thats the only option.

Your customers aren't using the Supabase Dashboard so this would/should not affect them. Ibrahim asked if you could test with a VPN to see if the issue is the same as what was reported before as some ISPs in your region have had issues in the past. If someone is trying to help you troubleshoot an issue please try and follow along.

Upgrade to pro and you should be able to get the last 7 days backup. This has worked for a number of users on here and was last reported working just last week.

Have you changed your network?

Pausing and resuming an instance was once a way to force missing migrations to run but we don't recommend this anymore as pausing could lead to your project getting stucked when trying to restore. When did you open your support ticket?

You need to contact Supabase support about this. They are the only ones who can check if your domain was setup correctly.

All the steps are noted in the restore guide link https://supabase.com/docs/guides/platform/migrating-within-supabase/dashboard-restore

You follow the restore link

The restore process is telling you about the details for the new project. There is no way to access the old project settings, but you have the backup file.

Why would you need to backup via SQL when there is a Download backups button there?

What exactly is confusing?

The information for backing up and restoring is on the project paused page.

I would like to think this is only true in systems where an email isn't a unique identifier, so that system would allow username instead. In the case of Supabase Auth, an email is a unique identifier, so two accounts cannot be associated with the same email.

The UI allows you to update other existing secrets by just updating the values and clicking save. You might be getting a failure as you are trying to update the `SUPABASE_` reserved key. Try only updating the ones you've set first.

Firstly `SUPABASE_` is reserved, you cannot update any environment variables starting with that as it's automatically set by Supabase themselves.

Was there any errors in your Postgres logs about the migration running? maybe the function has an issue hence why it didn't run. Also have you tested this migration on a testing environment before pushing it to your production?

You need to contact Supabase support. https://supabase.com/dashboard/support/new

This would be an Vercel issue if you made payments through Vercel. Also it’s confusing that you are making payment for one Vercel teams account for another Vercel teams account. I can see where this would trip the Vercel support team up. It would be up to Vercel to contact Supabase on your behalf to resolve this as they manage the Supabase integration.

Yes as you have gone over your quota as stated in the screenshot

The apple account should already have an email associated with it as that is a requirement for creating OAuth with Apple. You can use the `supabase.auth.updateUser` function to set a password for that user once they are logged in with the Apple OAuth. This will now allow them to use both email/password and Apple OAuth.

Already escalated from yesterday through the informal path. Nothing else we can do here.

More context is required here. Helpme! isn't really helpful.

What additional permissions is it asking for?

Try restarting the project and see if it makes a difference. If it doesn't then share your support ticket id here and I will pass it along our informal path.

It would say **PRO** instead of **FREE** if it was a paid organisation with two paid projects.

You said you have 2 projects which are paid, but your organisation there clearly states **FREE**. Which would mean you have 2 free projects, they are not paid. Paid account is based on the organisation and not the actual project.

So when you click on this inside of your Dashboard, you only see 1 organisation?

It's 2 free projects per account and not per organisation, so if you have other organisation inside of thie account with free projects then that could also be the reason.

If you were invite to someone else project that is on a free plan then this would be the reason for the messaging.

You can follow these guides on how to migrate https://supabase.com/docs/guides/platform/migrating-within-supabase, if you are on the Pro plan Supabase has just released an feature currently in beta to restore to a new project from backup in the UI https://supabase.com/dashboard/project/_/database/backups/restore-to-new-project. And more information about why no superuser role can be found here https://supabase.com/docs/guides/database/postgres/roles-superuser

Share your ticket id here and I will try and push it through the informal path we have

I replied on your other post already https://discord.com/channels/839993398554656828/1487725618740199595

If you turn off confirm email, the email is auto confirmed on account creation. There is no option to have it the way you are asking unless you create your own custom auth mechanism. This is just how Supabase Auth works.

The docs state it's necessary, maybe it wasn't before but Apple might have changed the way how these work and so Supabase would have to implement this update. https://supabase.com/docs/guides/auth/social-login/auth-apple?queryGroups=framework&framework=nextjs#generate-a-client_secret

What happens if you leave the input empty?

What does the policy you are trying to create look like?

I have not worked with custom domains so I'm not of much help here. Maybe someone else will come along who can help with this.

You will need to provide more context than what you have above. What are you trying to do exactly?

Supabase support are the only ones who can help you with this. We can however bump your ticket through an informal path, please post your ticket id here and I will do so. Also note it's the weekend and Supabase support is generally a bit slower than on the weekdays.

You need to contact Supabase support to get this resolved https://supabase.com/dashboard/support/new

All posts on here should be made in english.

I see another mod bumped this to our informal path for such things but just one employee checks that path when he can. During the weekend there is less staff.

You contact support through the dashboard https://supabase.com/dashboard/support/new or if you cannot access the dashboard their email can be found here https://supabase.com/support-policy#official-support-channels

Drop your support ticket id here so we can bump it.

Did you get a message about your account being banned? was there a reason given? What is your support ticket id?

What do you mean by the email by which it was hosted has been removed? do you mean you no longer have access to that email address? did you originally sign up with email/password or with GitHub?

Supabase support are the only ones who can help with this. It’s the weekend and support is a bit slower than on a weekday.

You will just have to check the other provider that you use to see if you have the Supabase integration enabled.

Moving the conversation here as this is the appropriate channel