I see this everywhere, unfortunately. Speed and short-time financial value over long-term quality

Thanks for sharing your experience!

phil So my fix is still there in the current source code. Can you check your version if you got the newest images? https://github.com/supabase/supabase/blame/master/apps/studio/data/auth/user-create-mutation.ts

Hey phil . Hm, that's unusual. Normally this shouldn't happen as it tries to redirect from an API request, so from a "background request". There was an error in the Supabase JS code that caused this because the auth info was explicitly omitted but I fixed this in a PR and it got merged so now I have to check again if it came back. Here's my PR: https://github.com/supabase/supabase/pull/18156 The good news: This isn't an infra problem, but a JavaScript problem in Studio if it is what it was back then. So you can still create users via API.

What do you mean with "same problem without your setup" ? Tihomir Jevtović

This blog post is complementary to its YouTube video. In the YouTube video I explain that if you want that, which I don't, you need to leave the definition in the compose file. If then it still doesn't work, that's usually due to your servers firewall so you'd have to configure that to be possible.

That narrows it a bit down. But now we have to find out if the problem is the JWT or something different. Can you tell me to where the request goes when you try to create a user in studio? (Browser Inspector -> Network). Does user creation work with the Supabase Client? Tihomir Jevtović

Can you provide specific error message? Tihomir Jevtović

Tihomir Jevtović I have just tried my node -e "console.log(require('crypto').randomBytes(32).toString('hex'))" and entered it in https://supabase.com/docs/guides/self-hosting/docker#generate-api-keys and it worked fine :) What's the issue when you do it?

Thanks for the insight. Tihomir Jevtović Will have a look into that! Wonderful.