garyaustin

Top right of dashboard to contact Supabase.

Yes if you canceled you got a credit for the unused time in the month. You should be able to use that in the future depending on if it is same account and org. But this is a user helping user forum mainly and we can't help with billing, only support can.

Glad you found it. We can't close the original ticket with support, but I did drop the bump we tried to do.

You need to contact support.

Pausing does not reset usage threshold and in fact usually hangs because of lack of resources to do a backup... I can drop your ticket in an informal queue we have but not sure it will be faster than Pro support. Drop your ticket # here.

It will likely be awhile with the long weekend for many. But paused should be low priority as that means it is not being used normally. How long ago did you contact support?

If your project is stuck pausing it the only way to resolve is thru support.

You need to file a support request titled project stuck pausing. How did it get paused?

Only support can do that. This is a user helping user forum mainly. I added your ticket to an informal queue one employee checks, but holiday weekend for many.

No idea what that says.

Can you switch the "primary" email of the github account? That is the one Supabase uses. I believe it also has to be verified in Github.

Column 'name' is the path. You use that with the bucket name. But really should not be relying on look up in storage.objects.

You need the path.

The postgres log and checking for triggers you have added to auth would be the things I would first look at.

This is the only ON CONFLICT ON CONSTRAINT in Auth...

What does your exact postgres error from the logs say?

Do you have any functions operating on this table?

A unique index is sufficient for upsert. Mine only has the unique index. I assumed that was what you were missing.

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

Make your own key header and pass that from the DB functions. Store it in Vault and Edge secrets. You can also use the Secret key in the edge functions. The functions though now have to be invoked and then you check before running anything. The new keys and JWT's do not work with the jwt_enabled flag.

It has not been seen by our informal contact (employee) for bumping yet.

Are you down or safer waiting for support if a production app.

Yes.

This is a user helping user forum and support won't likely see this post. BUT they have said it can take up to 24 hours to clear. I think the warning looks like this...

You can't use verify_jwt anymore with the new API keys or asymmetric JWTs. https://supabase.com/docs/guides/functions/auth

I do not know, your last statement was you thought better support would be useful which implied it was a suggestion to SB. You'll have to see if any other users have ideas. I don't use this for Edge functions.

Is your database deleted or your project? If project there is no recovery. If database then going to Pro should have the entire database in the backups that are kept daily for 7 days. Not documented but only one user has said it did not work out of dozens.

Are you sure it was not just doing a 2nd signup?

FYI this is a user helping user forum and not regularly monitored by Supabase. There is a feature request at top of dashboad.

Check if you are fully upgraded in infrastructure settings. If not you might want to consider an upgrade which might run the migrations.

You do if your network (or network from your app server) is not IPv6 compatible.

Could you have lost IPv6 support for whatever is trying to connect?

What is that from?

Do not ask users here to DM for help. If you want to help do so in public.

There is no outage.

I bumped your ticket to an informal path we have but no guarantee it is faster than support.

I can confirm that is a constraint on one of my instances. This is a user helping user forum though mainly so no one here can fix your instance.

It is highly recommended to see if users here can help as support can take awhile.

This site is not monitored by staff regularly. You will need to wait on email support, unless a user here has ideas for you. I don't use this and have no ideas for you.

The pricing page covers the per GB price for storage... https://supabase.com/pricing .021 per GB

Another user might be able to comment if you are doing something wrong, or confirm if broken or not (no other reports)... BUT this is not support and no one here can see your project. You would need to contact support from top right of dashboard if you are sure it is an issue with your project.

RPC or generated/stored columns would be it. All the filters are covered in the Supabase docs for Supabase-js and PostgREST.org for PostgREST itself (but that is not there). Users here (or probably even Supabase) can't answser what PostgREST will support in the future. They have a github where people ask for features (or might have yours already there).

Yes, that support email is very generic, and users here can help with alot, but not backup errors. Very few users try to restore 90 day old instances AND have the backup not there so not sure you will get suggestion on that. But we will see.

I would think so IF you have not exceeded egress. But you really did not answer if REST API or not as that also hits the DB.

You should also change code so you don't loop on error but do a exponential back off or limited number of tries.

You can shut of the REST API with a button in settings. DB I guess you could change the password....

REST API or database?

The 7 days won't likely be relevant as that is not for paused projects.

No way users here can tell what the issue is with the backup. Support is the way.

Seems more like a code loop (maybe on error bug) or attack of some sort.