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

Open
#44 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
docker, nextjs, supabase, typescript
Domain
devops, frontend

Research direction

Start with the Docker self-hosting setup and the dashboard entry point, then reproduce the client-side exception while checking how NEXT_PUBLIC_SUPABASE_URL and NEXT_PUBLIC_SUPABASE_ANON_KEY reach the browser. Done means a Docker deployment with those values can load the dashboard without the missing Supabase URL and key error.

Written by the indexing model from the issue text.

Description

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!

Dominant language
TypeScript
Stars
676
Forks
48
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from chroxify/feedbase

All issues in chroxify/feedbase

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.