Hello David, Great tutorial!

I was wondering whether you have come across the "Invalid Signature" error while creating bucket in studio? I have tried both, S3 Mimio storage and default volume storage. Both result in the same error. Common fix suggestions refer to default ANON_KEY and SERVICE_KEY mismatching, however, in your tutorial you have guided how to update them, so presumably they shouldn't be an issue, however, I get exact same error every time I'm trying to create a bucket :/

Thanks for your tutorials, they're great!

Hey, Nice Post, thanks! Has anyone already tested Supabase fully managed by elest.io? It seems you can deploy Supa stack on some EU service cloud provider like Hetzner or Scaleway. It appears as a good alternative for GDPR compliant for a managed supabase stack.

Thanks a lot! Where would you host the database for prod applications? Hosting containers is great but for a DB I would like to have point-in-time recovery... I've been using Aiven or ElephantSQL but they lack the extensions like pg_net to support the most basic Supabase features like webhooks.

Hi there and thanks for the well rounded tutorial. I've had a few problems myself setting up a self hosted supabase instance. Especially love the nginx proxy manager. But some problems still remain:

Setting up everything together with minio wouldn't work with the additional nginx for supabase: ports already in use, since i have had everything on the same server. But since I did not need this, I reinstalled the server and skipped the s3 part.

But now my auth container was restarting over and over. Reason was the URL for my api.my-domain.com in .env was malformed: it needed to begin with https://. Since changing it (and same for studio.my-domain.com to be sure) everything works as intended for the moment.

Now onto authelia to try this one out.

Hey, thanks a lot for such a helpful guide. Also in the "Secure minio" section under "2. Dashboard Host" the hostname should be "minio" and the domain is "storage-dashboard.yourdomain.com"

Hi David, We self hosted a Supabase DB with your guide and most parts working correct. But if we try to add a user we got the following error messages:

GUI: Logs -> Kong API: 503 Kong Error logs of the Docker Container: 172.29.0.5 - - [23/Jan/2024:15:48:48 +0000] "POST /auth/v1/admin HTTP/1.1" 503 36 "-" "PostmanRuntime/7.34.0" 2024/01/23 15:49:00 [error] 1109#0: *1462886 [lua] init.lua:310: execute(): DNS resolution failed: dns server error: 3 name error. Tried: ["(short)auth:(na) - cache-miss","auth:1 - cache-miss/scheduled/querying/dns server error: 2 server failure","auth:5 - cache-miss/scheduled/querying/dns server error: 3 name error"], client: 172.29.0.5, server: kong, request: "POST /auth/v1/admin/users HTTP/1.1",

Do you have a solution for that error? Best regards Sven

Hi David, Thanks for your effort for making this guide.

I hope you can help me with an issue you might already know how to solve.

I created supabase server using your guide (minus authelia) and enabled FUNCTIONS_VERIFY_JWT=true in .env. Everything appears to work fine which my own domain.

Have you tried running edge functions on your setup that requires a supabase client connection?

Can you try and create a simply function that runs createClient() using esm.sh/@supabase/supabase-js@2 and connects into kong:8000 using ANON_KEY?

The function works on a local development environment but on this self-hosted system it crashes the edge-function docker service when run in the createClient() call.

If you have suggests I would appreciate it.

Cheers

This has been helpful with getting a newer version of Supabase hosted! I was struggling with getting Auth to work until you posted the Advance Tab settings for the dashboard. Now I can add users, but I'm getting a '403 Forbidden' error on the user verification links. Any ideas on what's causing this?

Great blog. Although I still run into an issue where I cannot fully use the authentication panel inside supabase. For example, I cannot use create new user feature. Do you perhaps have a git repository of this project?

Access to fetch at 'auth.domain.com (redirected from 'studio.domain.com/auth/v1/admin/users&) from origin 'studio.domain.com& has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.