---
title: "Discussion on \"The ultimate Supabase self-hosting Guide\" | Hashnode"
description: "Discussion on \"The ultimate Supabase self-hosting Guide\". Preamble: This guide is not intended for local / dev installation. Supabase already has a dev setup with the CLI - so use that one. This guide is for actual self-hosting and it's quite some honest work, definitely worth it.\nIf you don't wanna spend a..."
url: "https://hashnode.com/posts/the-ultimate-supabase-self-hosting-guide/64e85d050e78298524ccbcfd"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [The ultimate Supabase self-hosting Guide](https://blog.activeno.de/the-ultimate-supabase-self-hosting-guide?utm_source=hashnode&utm_medium=feed)

Preamble: This guide is not intended for local / dev installation. Supabase already has a dev setup with the CLI - so use that one. This guide is for actual self-hosting and it's quite some honest work, definitely worth it. If you don't wanna spend a...

Aug 25, 2023 · 16 min read · blog.activeno.de  
Updated Jun 15, 2025  
Read the article

-   [#supabase](https://hashnode.com/tag/supabase)
-   [#self-hosted](https://hashnode.com/tag/self-hosted)

## Written by

[David Lorenz](https://hashnode.com/@activenode)

@activenode

  
[View profile](https://hashnode.com/@activenode)

Frontend Architect having worked with IE5 Ω

## Responses 11

Markdown supported · ⌘↵ to post

[Boutar Badii](https://hashnode.com/@xdabier)

[May 24, 2025](https://hashnode.com/posts/the-ultimate-supabase-self-hosting-guide/64e85d050e78298524ccbcfd/comment/683129caf13730cf53059692)

Are these steps still up to date with the current 2025's version ?

[Adrian](https://hashnode.com/@avb67)

[Oct 4, 2024](https://hashnode.com/posts/the-ultimate-supabase-self-hosting-guide/64e85d050e78298524ccbcfd/comment/670032af606f55c0db5d65fd)

Hello to all commentators: To get rid of the studio errors, you should make sure in the .env file that no ports are passed in the URLs and that the correct protocol is chosen (https instead of http). Then it should work. Disclaimer: I have no idea why it works, but it does. Good luck!

[Evaldas Sedys](https://hashnode.com/@EvaldaSedys)

[Mar 7, 2024](https://hashnode.com/posts/the-ultimate-supabase-self-hosting-guide/64e85d050e78298524ccbcfd/comment/65e9ad8721f82f21510719d6)

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!

[Damien Roch](https://hashnode.com/@koryonik)

[Mar 3, 2024](https://hashnode.com/posts/the-ultimate-supabase-self-hosting-guide/64e85d050e78298524ccbcfd/comment/65e4d3a3dbfb95ac9be69d6a)

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.

[PK](https://hashnode.com/@pk992)

[Feb 19, 2024](https://hashnode.com/posts/the-ultimate-supabase-self-hosting-guide/64e85d050e78298524ccbcfd/comment/65d3bb006b78a640675af2a7)

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.

[Stephan Brüggmann](https://hashnode.com/@Neomedes)

[Feb 9, 2024](https://hashnode.com/posts/the-ultimate-supabase-self-hosting-guide/64e85d050e78298524ccbcfd/comment/65c5c84c822416dfa99e95d7)

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.

[Alireza Hajebrahimi](https://hashnode.com/@iarata)

[Feb 8, 2024](https://hashnode.com/posts/the-ultimate-supabase-self-hosting-guide/64e85d050e78298524ccbcfd/comment/65c421f276d4a6387992e664)

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"

[Sven Neubüser](https://hashnode.com/@Svenneub)

[Jan 25, 2024](https://hashnode.com/posts/the-ultimate-supabase-self-hosting-guide/64e85d050e78298524ccbcfd/comment/65b276b21cfb7b7a5093a26d)

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

[Les Kadlof](https://hashnode.com/@leskadlof)

[Nov 29, 2023](https://hashnode.com/posts/the-ultimate-supabase-self-hosting-guide/64e85d050e78298524ccbcfd/comment/656702dde1018a2c60615478)

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

[David Lorenz](https://hashnode.com/@activenode)

[Nov 29, 2023](https://hashnode.com/posts/the-ultimate-supabase-self-hosting-guide/64e85d050e78298524ccbcfd/comment/656702dde1018a2c60615478#reply-656751845d000a04d67e3969)

Hi [Les Kadlof](https://hashnode.com/@leskadlof). So you're saying you are calling your `[api/.<your-domain>/functions/v1/YOUR_FUNC_N…](http://api/.%3Cyour-domain%3E/functions/v1/YOUR_FUNC_NAME)` and the service crashes? Can you give me information about why the service crashes? There must be logs within `docker compose logs`. Do all services crash or just the functions service? If you want, you can also contact me at discord.

[Les Kadlof](https://hashnode.com/@leskadlof)

[Nov 30, 2023](https://hashnode.com/posts/the-ultimate-supabase-self-hosting-guide/64e85d050e78298524ccbcfd/comment/656702dde1018a2c60615478#reply-6567f0c184ca99a5e6170181)

[David Lorenz](https://hashnode.com/@activenode) Hi David. Yes. supa.my\_domain/functions/v1/my\_function and it crashes within the createClient() call. I've created a discord with all of the information. (the invite for discord is discord.gg/Y54YmNrY) Thanks.

[Alec](https://hashnode.com/@Aleccc)

[Nov 12, 2023](https://hashnode.com/posts/the-ultimate-supabase-self-hosting-guide/64e85d050e78298524ccbcfd/comment/65511709b114e923524ddfa1)

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?

[David Lorenz](https://hashnode.com/@activenode)

[Nov 13, 2023](https://hashnode.com/posts/the-ultimate-supabase-self-hosting-guide/64e85d050e78298524ccbcfd/comment/65511709b114e923524ddfa1#reply-65522dd80701ac13578c650c)

[Alec](https://hashnode.com/@Aleccc) Alright, that helps a bit. As you cannot set the auth urls in the Dashboard (as you can with supabase.com) have you added your URL in the configurations? So [example.com/\*\*](https://example.com/**) as a valid configuration within `ADDITIONAL_REDIRECT_URLS=` ?

[Alec](https://hashnode.com/@Aleccc)

[Nov 13, 2023](https://hashnode.com/posts/the-ultimate-supabase-self-hosting-guide/64e85d050e78298524ccbcfd/comment/65511709b114e923524ddfa1#reply-655262d6b114e923524dfc65)

Thanks [David Lorenz](https://hashnode.com/@activenode)! That was it, ADDITIONAL\_REDIRECT\_URLS was set but I needed to remove "["](https://"/) from the URLS.

[David Lorenz](https://hashnode.com/@activenode)

[Nov 13, 2023](https://hashnode.com/posts/the-ultimate-supabase-self-hosting-guide/64e85d050e78298524ccbcfd/comment/65511709b114e923524ddfa1#reply-65527aaeb114e923524dfe60)

Wonderful :party: [Alec](https://hashnode.com/@Aleccc)

[phil](https://hashnode.com/@phil383)

[Sep 3, 2023](https://hashnode.com/posts/the-ultimate-supabase-self-hosting-guide/64e85d050e78298524ccbcfd/comment/64f49c8c448e318af4d5d933)

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?

[phil](https://hashnode.com/@phil383)

[Jan 1, 2024](https://hashnode.com/posts/the-ultimate-supabase-self-hosting-guide/64e85d050e78298524ccbcfd/comment/64f49c8c448e318af4d5d933#reply-6592c95bbb9e53e89c9fb632)

[David Lorenz](https://hashnode.com/@activenode)

Hey david, I seem to run into an issue and I thought why not ask you. Everything works except for the auth creation of users. I think it has to do with my nginx/authelia settings but perhaps you know more.

I obtain the following error:

```
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.
```

with `domain.com` being my hostname of course. Do you know what to assess?

[David Lorenz](https://hashnode.com/@activenode)

[Jan 3, 2024](https://hashnode.com/posts/the-ultimate-supabase-self-hosting-guide/64e85d050e78298524ccbcfd/comment/64f49c8c448e318af4d5d933#reply-6595264de08a9c26915a0a83)

Hey [phil](https://hashnode.com/@phil383). 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: [github.com/supabase/supabase/pull/18156](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.

[David Lorenz](https://hashnode.com/@activenode)

[Jan 3, 2024](https://hashnode.com/posts/the-ultimate-supabase-self-hosting-guide/64e85d050e78298524ccbcfd/comment/64f49c8c448e318af4d5d933#reply-659527693cec7405d536754a)

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