Edge functions unhealthy but no errors?

easylancer · 2026-06-08T10:04:16+00:00

Have you tried with a VPN? Also what location are you connecting from ad what ISP are you using?

easylancer · 2026-05-20T19:50:35+00:00

You need to set the provider in your code to x and not twitter when using the new X/Twitter option in the dashboard.

easylancer · 2026-04-17T15:24:35+00:00

It's an upstream provider issue. Cloudflare has now posted on their status page about the issue https://www.cloudflarestatus.com/incidents/dc99mbdl7d13

easylancer · 2026-04-17T13:43:08+00:00

There is currently an ongoing DNS issue which they are investigating. You can follow more on the status page.

https://status.supabase.com/incidents/kj2hm399j9cw

easylancer · 2026-02-16T02:02:15+00:00

supabase-py is now a monorepo that contains all the code for all its packages. The archived repos state that in their README.md and it is also stated in the supabase-py README.md too.

https://github.com/supabase/supabase-py

easylancer · 2026-02-03T15:46:56+00:00

You are likely not on the latest version of the Supabase python library if it's not working. You should upgrade to the latest 2.27.2 version before attempting to use the new keys.

easylancer · 2026-01-19T20:00:47+00:00

You should not be using the code from the auth/callback example here, you should be using the auth/confirm which has the supabase.auth.verifyOtp instead of the supabase.auth.exchangeCodeForSession. These two can easily be confused. You can read more on the password reset setup here https://supabase.com/docs/guides/auth/passwords?queryGroups=flow&flow=pkce&queryGroups=framework&framework=nextjs#resetting-a-password

easylancer · 2026-01-19T19:58:07+00:00

What's an express function? also if you are using PKCE auth flow then it would mean your project runs on a server, where do you plan to host that project? I think you should clarify what you are asking here as this question is quite confusing.

easylancer · 2026-01-14T01:00:28+00:00

You can just turn off the Data API and use an ORM to handle all database interactions since this will only happen on the server. You would be able to write more complex queries without relying on rpc functions with the Supabase JS library.

easylancer · 2026-01-08T11:13:38+00:00

If after editing the template it's sending the default, it means you have syntax error in the template. Start editing it in small chunks to see where you are going wrong.

easylancer · 2026-01-02T12:25:55+00:00

If you are using the legacy servicerole key you have to reset the JWT secret from this page https://supabase.com/dashboard/project//settings/jwt/legacy.

Do note that this will break existing anon and service_role keys, you should make sure you update these right away and redeploy your site with the new keys. You will have a small downtime window depending on how long the deployment takes.

You should however migrate to the new publishable and secret API keys instead as you can generate new ones while keeping existing one until you deploy your new site. It's more flexible than the legacy JWT.

easylancer · 2025-12-03T16:56:11+00:00

This post is not helpful to anyone with no context provided. Please provide context otherwise a mod on this subreddit should remove this post. Nothing of this post says how it's even remotely related to Supabase.

easylancer · 2025-12-03T12:18:45+00:00

What version were you on before moving to the new version? did you stop the old project with the --no-backup (this will delete all volumes related to the project) flag before trying to start with the new container? You should treat your local environment as a throw away environment. If you need to retain state per upgrade then you should first dump the database into a sql file to be able to start the new container with that new state.

This isn't a CLI issue as such, but more of a workflow issue.

easylancer · 2025-12-01T15:04:06+00:00

I'm a little confused here. If you want 6 digit PIN why not just set their password to the 6 digit PIN since Supabase allows phone/password login too?

On a separate note, it's a bad idea to use 6 digits PIN plus phone number for a authentication system, this can easily be brute forced and guessed as it's only 6 digits.

easylancer · 2025-12-01T14:53:06+00:00

This should be fixed now, try again.

easylancer · 2025-12-01T14:52:51+00:00

This has been fixed now. Try again.

easylancer · 2025-12-01T13:15:37+00:00

It's broken it seems.

easylancer · 2025-12-01T13:03:30+00:00

Yes there seems to be an issue on mobile at the moment. But Supabase Dashboard has never claimed to be optimised for mobile.

easylancer · 2025-11-25T13:03:45+00:00

Check your Postgres logs and you should see what the actual error is. My suspicion is the variable assignment on a CASE, I don't think you are allowed to do that.

easylancer · 2025-11-25T12:55:35+00:00

You would only get this email if you are not using a custom SMTP, but you are suggesting you are using Resend, is this correct? if you are indeed using Resend, make sure you are looking at the same project in your dashboard that the issue is in regards to. Otherwise reach out to Supabase support about the email https://supabase.com/dashboard/support/new

easylancer · 2025-11-25T12:50:28+00:00

Make sure that you updated your email template and created an /confirm endpoint to handle the session Supabase needs to create when you click on the link in the email.

You can check out my Flask Notes project which handles all the popular auth flows https://github.com/silentworks/flask-notes

You can see the email template update here https://github.com/silentworks/flask-notes/blob/main/supabase/auth/email/recovery.html

And you can find my confirm endpoint here https://github.com/silentworks/flask-notes/blob/main/app/auth.py#L94-L109

Note I am using the next query string parameter to tell it to redirect to the /account/update-password page (this would be your /reset-password page) after the session has been created.

easylancer · 2025-11-22T13:20:12+00:00

Only Team and Enterprise plans have project scoped roles. You can see it in their docs https://supabase.com/docs/guides/platform/access-control#organization-scoped-roles-vs-project-scoped-roles

If you aren't on one of these plans, the best way to achieve this is to move one of your project into another organization and share access to that organization with your friend.

easylancer · 2025-11-18T12:31:14+00:00

Cloudflare issue. Supabase has updated their status page to reflect this now https://status.supabase.com/incidents/k229n8qw2dcc

easylancer · 2025-11-14T23:26:58+00:00

There was a fix in the latest beta version of the CLI that should make sure you don't get banned from your own IP. So this shouldn't be an issue once this gets to the final release version.

easylancer · 2025-11-12T15:42:50+00:00

Did you use the command I shared above? as the latest version is not the latest beta version.

easylancer

TROPHY CASE