Self-Hosted dashboard stuck on `Connecting to Default Project`.

    I tried @karouvirae `docker-compose.yml` file and that did not work, I received errors from `auth`, `rest`, `realtime`, and `storage`

I tried both the following repositories and none of them worked. https://github.com/supabase-community/supabase-traefik https://github.com/supabase/supabase/tree/master/docker

First off, the unofficial Traefik setup that is supported by the community is outdated. The main self-hosting guide containers all work, although the Dashboard gets stuck, and I need to get this running as soon as possible.

I even found the following issue about it: https://github.com/supabase/supabase/issues/8721

Does this mean that self-hosting is currently not possible with the bug introduced in the above issue? I have made a help post about this in the Supabase Official discord, and so far no one has responded.

In the r/Supabase Reddit, there is a similar post. https://www.reddit.com/r/Supabase/comments/ycwude/comment/iuwa3az/?utm_source=share&utm_medium=web2x&context=3

I tried changing the following .env variables but no luck.

SITE_URL
API_EXTERNAL_URL
PUBLIC_REST_URL

Sadly I have been working on this for over 12 hours, and this is my very first experience with Supabase, a very horrible one at that.

_Originally posted by @NorkzYT in https://github.com/supabase/supabase/issues/4934#issuecomment-1302603468_

[globemediaofficial]

I’m the op of that issue on Reddit. Still no fix. It’s not really an issue with the dashboard, it’s an issue with the Database not connecting. None of the CLI will work either, because things like Auth are still stored in the Database which won’t connect. I followed the same guides as the first time I successfully self-hosted supabase so I’m sure it’s an issue with the update. As you’ve seen, I posted an issue on GitHub and Reddit over 10 days ago but got no support or help. I guess the expectation with self-hosting is that you are a developer who can fix these detrimental errors yourself instead of the Supabase team. This also came at the same time as the package updates (Flutter and JS), which were initially unannounced and made a lot of unexplained changes, so that might be a factor.

[globemediaofficial]

@NorkzYT

Looking at your .env, I see sub.domain.com for all of the URL’s even though they have different ports and paths. Do each of them have a unique subdomain that points to the corresponding port and path? If it’s just one subdomain that points to the server IP, you would need to specify ports at the end of each URL. For example: SITE_URL=https://sub.domain.com:3000. If I were you, I would try to change the URLs to the server IP and the corrects ports to make sure that’s not the issue.