garyaustin

All I can do is add to the queue for an employee to check on his time schedule. And all he can do is get it out of general support queue to the correct team. But it is added.

That is normally the case, but normally you just get a warning and next billing period it goes away UNLESS you violated over 2 billing periods. So not sure if Pro solves or not. I would think yes but your state seems odd and may be because you were WAY over the egress limit. Also if you drop your ticket number we have an Informal path to get it out of general free queue if lost but that path depends on the employee checking in.

Do you mean Github? Try another browser if so. Otherwise you have a ticket in which is the correct thing.

There is no Google log in for Supabase ever.

There is not exact formula... normally if not "too" abusive and you do not exceed the next billing period then you are fine.

You can still access your account? If you are more than a day into the new billing period then contact support or go Pro.

If no schema cache error then post your rpc call and function definition for parameters. I'll be out for awhile but others might check.

You can check if schema cash by running `NOTIFY pgrst, 'reload schema'` and looking in the PostgREST log for any schema cache error.

This is almost always your parameters being passed to the rpc call don't match the function's. Postgres treats each parameter combo as a unique function. What is the detail error coming back? Any useful error in the API Gateway or Postgres log?

Most likely you will need to contact support to resolve if it is past the point you can restart again or see if compute/memory/disk has reached "limits" and need to upgrade size. (note I don't use branching though, so not sure how sizes/resources come into play).

Looks like the dev did see your github post and there is movement on the Functions front in self-hosted... https://github.com/orgs/supabase/discussions/42947#discussioncomment-15836156

Are you using Supabase's built in auth? Do you have an auth custom claims hook? Do you modify the jwt/access token in your code?

Anything not in the admin section of auth can be set up to be used by users.

You'll have to dig or see if someone comes along. I'm not up on what each requires now as Brevo did not and I think they do now.

yeah that won't work (I don't believe) if the email provider requires you to confirm your domain... But I don't think they all do.

Vercel certainly works with custom domains. I can't image it does not.

The list shows many that are known to work with Supabase. I don't know of any that don't except maybe hostinger seems to have a few issues.

https://supabase.com/docs/guides/auth/auth-smtp

I use Brevo which has a great free plan. Many use Resend which has an integration with Supabase (or did last time I checked). Here is Supabase's docs with a list of plenty. Yeah you just set one of those up and make sure you can send a test invite from the auth panel. I don't know which ones require a domain though or not as I have domains.

I assume you are using their internal email SMTP which is only good for 2 or 3 an hour (just basic how does this work). Plus you are making up fake emails maybe? Use your own SMTP provider, which you will need to do anyway. You should never use their default SMTP in production.

I've never seen any real discussion from Supabase on this other than a performance doc mentioning what they are used for. We have one user helper here (<@1086143228652306506>) that is really good with Postgres that might have more to offer. I would assume though nothing supabase has added to what default postgres provides. You could also try their support.

There are no SSL settings for Supabase custom SMTP. My understanding is port 465 works with SSL. https://github.com/supabase/auth/issues/1660#issuecomment-2311166430

Also if you were using the project why is it pausing? If you attempted to resolve an issue you should always use restart in infrastructure settings and never use pause/restore. Do you actually have access to doing operations on the instance still or is the pause state hung past that?

You need to contact support directly.

https://supabase.com/docs/guides/functions/auth

It is the same thing. It will become the Secret key if you are using the new API key styles. The label though still says service role as that is what secret key becomes when you use it for a call.

Not quite sure what you are asking. But if you go to the edge function UI on hosted you will see a secrets tab and it shows the labels for the default secrets that are provided. Service role being one of them.

I recommend you post as best you can your specific issue in English. Many here can probably help, or determine where to send you for help, but you do not say what your issue is.

This is the call. https://supabase.com/docs/reference/javascript/auth-admin-inviteuserbyemail you can also see other admin stuff around that in the docs.

You would need to use an admin client with service_role on a server or edge function. There is no client side code that would work. All the rest is likely server side code you have to deal with and not specific to Supabase. Edge functions might be able to handle some of those checks.

A restore to a new project does not impact your current one... It might give you a way to see if the back up does have data and possibly use psql to backup from that and restore?

This is user helping user mainly, and this user is running out of things to suggest/ask.

Try a different browser. Get a support ticket in.

Or they are empty.... I'm assuming you are talking Supabase dashboard (not some other cloud thing like Bolt) and you have a physical back up shown about once a day. Do the tables show? Any data? Does this have anything to do with branches? And I assume you reset it with the CLI?

If you go back to a previous backup is the data there?

Did you try to pause/restore more than once? Not sure you are any worse off at this point being stuck in pause if it can't pause it. But pause restore does start it up on a new hardware instance, were restart is just reboot.

As you paused and restored I take it you are running on a free plan?

There is no one here to reach out to as this is user helping user mainly.

You said you generated a request.... `I did start a support request`

Well at this point as it appears to be something with the REST API and from multiple routes it will have to be them to sort it.

You just said you worked with them yesterday...

You did not mention support being involved. Seem like what ever they did to get around this linking issue must have dropped something with DNS.

Wait... was this a bolt cloud project you somehow moved to supabase or it was just linked and you unlinked it? I guess though it does not matter at this point as still likely need support needed to fix it.

Not pause/restore as you should never use that for a restart.

If you restarted and it did not work then you need to wait for support.

The other services are shared (well except DB).

That could be DNS too potentially.

What did you CURL that failed? Does your app use supabase-js?

No idea what that is. I'm talking like supabase.co/rest/v1/.....

Please clarify the URL you are using so we know if it is a REST API request or a direct DB port request. If it is REST API then you will probably be waiting on Support.