Docker self-hosted - Clientside exception occurred (unknown Supabase project URL and key)

[paulchartres]

Hey there, first off just wanted to say phenomenal work on the app!

I've been trying to self-host it on my server using Docker and I am running into issues with the Supabase configuration. I have properly passed the NEXT_PUBLIC_SUPABASE_URL and NEXT_PUBLIC_SUPABASE_ANON_KEY (using the env command within the container does show that the environment variables are populated), however when I try to access the dashboard, I am greeted with the following error:

Application error: a client-side exception has occurred (see the browser console for more information).

When I check the console, I have the following:

Error: Your project's URL and Key are required to create a Supabase client!

Check your Supabase project's API settings to find these values

Maybe I just forgot an important step, but I'm not sure what the problem could be.
Thanks for your help!

[LawMixer]

Are you using a server or a web application panel like easypanel?

[LawMixer]

Something similar is happening to me, and the maintainer is investigating why this is.

[paulchartres]

I'm using a basic server (running Debian) and I manage everything through a single Compose file. If that matters, I'm also using Traefik as my reverse proxy.

[LawMixer]

Weird, we both use Traefik (easypanel does and you do), maybe that's the problem? It's a long shot, but I can't seem to figure it out. Could you maybe try to disable it and see if it works then?

[paulchartres]

I'll give it a shot and keep you posted sometime today or tomorrow, not sure if Traefik has something to do with it but who knows!

[LawMixer]

It will make sense if it does, as Traefk and Feedbase are colliding with each other and I do believe Feedbase handles it's subdomains and all, but who knows? I might be wrong.

Whenever the maintainer tried it, I don't think he had Traefk

[LawMixer]

Alright, I've talked with a person about it because I'm not really knowledgable in this stuff. I could be 100% wrong, but I feel like I'm right here.

Feedbase handles it's own subdomains, and Traefk is a reverse proxy, so they are going to be fighting for position and obviously Traefk is going to win this battle and that happens, it breaks the Feedbase, so it gets confused in the long-run.

I'm hoping it makes sense, but if it doesn't, I can explain it in different ways

[chroxify]

hey @paulchartres, thanks for the issue! As @LawMixer mentioned, it seems like you guys have a similar problem.

I’m currently trying to figure out what this could be caused by as, weirdly, everything works fine using the prebuilt public image on my local machine. Will test this on an external server too and keep you guys posted!