Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error evaluating "env(AUTH_GITHUB_CLIENT_ID)": environment variable AUTH_GITHUB_CLIENT_ID is unset. #2599

Open
AndaHendriksen opened this issue Aug 8, 2024 · 2 comments

Comments

@AndaHendriksen
Copy link

Describe the bug
When I run "npx supabase start" I get the error message:
Error evaluating "env(AUTH_GITHUB_CLIENT_ID)": environment variable AUTH_GITHUB_CLIENT_ID is unset.
Try rerunning the command with --debug to troubleshoot the error.

When I run "npx supabase start --debug" I get the same error:
Error evaluating "env(AUTH_GITHUB_CLIENT_ID)": environment variable AUTH_GITHUB_CLIENT_ID is unset.

I've followed this doc to add the variables and when I run "npx supabase secrets list" as the doc suggests, I can see that AUTH_GITHUB_CLIENT_ID is there. And I have a local ".env" and ".env.local" file with the variable set.

What am I missing?

Expected behavior
I want to be able to run supabase in docker

System information
Rerun the failing command with --create-ticket flag.

  • Ticket ID: c7835273637144bf897af2f1e3a21ba2
  • Version of OS: Windows 10
  • Version of CLI: v1.187.10
  • Version of Docker: v4.33.1
  • Versions of services:
    SERVICE IMAGE │ LOCAL │ LINKED
    ─────────────────────────┼──────────────────┼─────────
    supabase/postgres │ 15.1.1.78 │ -
    supabase/gotrue │ v2.151.0 │ -
    postgrest/postgrest │ v12.2.0 │ -
    supabase/realtime │ v2.29.15 │ -
    supabase/storage-api │ v1.0.6 │ -
    supabase/edge-runtime │ v1.55.0 │ -
    supabase/studio │ 20240729-ce42139 │ -
    supabase/postgres-meta │ v0.83.2 │ -
    supabase/logflare │ 1.4.0 │ -
    supabase/supavisor │ 1.1.56 │ -
@sweatybridge
Copy link
Contributor

It's most likely due to wrong config.toml. Can you reinitialise with supabase init --force?

@HuriHuchi
Copy link

I am experiencing the same issue. Above solution isn't working either.

It's most likely due to wrong config.toml. Can you reinitialise with supabase init --force?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants