Error library · Config missing from the build
“supabaseUrl is required” in production
Your live site can't connect to Supabase: the settings it needs (its address and key) are missing or wrong in the published version. It works where you build, because the settings are there — they just never made it to the live site.
Who it affects
Anything that needs Supabase — usually signing in and loading data — fails for everyone on the live site. 5 sessions affected so far.
Numbers here are from an example app where 5 visitors hit it. How serious: Critical — it stops people using the app, or costs you money.
How to fix it
Give this to the AI that builds your app. It’s the prompt Vigilia writes for this error — shown here for an example app (an orders table, a /checkout page); for your app, Vigilia fills in the real details from what your visitors hit.
For Lovable
Lovable: Bug: on the live site the Supabase client fails to start with "Error: supabaseUrl is required.".
Evidence: "Error: supabaseUrl is required." — seen 12 times across ~5 sessions, on /checkout.
What to change:
1. Find the environment variables the Supabase client reads (for example VITE_SUPABASE_URL and VITE_SUPABASE_ANON_KEY).
2. Set them in the hosting provider's environment settings for production, with the same names the code uses, then rebuild and redeploy — build tools bake these in at build time.
3. Only public client values belong here (the anon key, never the service_role key).
4. Fail with a clear message if configuration is missing, instead of a blank page.
Acceptance criteria: the live site signs in and loads data, with no "supabaseUrl is required" errors.For Bolt
Bolt: Bug: on the live site the Supabase client fails to start with "Error: supabaseUrl is required.".
Evidence: "Error: supabaseUrl is required." — seen 12 times across ~5 sessions, on /checkout.
What to change:
1. Find the environment variables the Supabase client reads (for example VITE_SUPABASE_URL and VITE_SUPABASE_ANON_KEY).
2. Set them in the hosting provider's environment settings for production, with the same names the code uses, then rebuild and redeploy — build tools bake these in at build time.
3. Only public client values belong here (the anon key, never the service_role key).
4. Fail with a clear message if configuration is missing, instead of a blank page.
Acceptance criteria: the live site signs in and loads data, with no "supabaseUrl is required" errors.For Cursor
Cursor: Bug: on the live site the Supabase client fails to start with "Error: supabaseUrl is required.".
Evidence: "Error: supabaseUrl is required." — seen 12 times across ~5 sessions, on /checkout.
What to change:
1. Find the environment variables the Supabase client reads (for example VITE_SUPABASE_URL and VITE_SUPABASE_ANON_KEY).
2. Set them in the hosting provider's environment settings for production, with the same names the code uses, then rebuild and redeploy — build tools bake these in at build time.
3. Only public client values belong here (the anon key, never the service_role key).
4. Fail with a clear message if configuration is missing, instead of a blank page.
Acceptance criteria: the live site signs in and loads data, with no "supabaseUrl is required" errors.For Claude Code
Claude Code: Bug: on the live site the Supabase client fails to start with "Error: supabaseUrl is required.".
Evidence: "Error: supabaseUrl is required." — seen 12 times across ~5 sessions, on /checkout.
What to change:
1. Find the environment variables the Supabase client reads (for example VITE_SUPABASE_URL and VITE_SUPABASE_ANON_KEY).
2. Set them in the hosting provider's environment settings for production, with the same names the code uses, then rebuild and redeploy — build tools bake these in at build time.
3. Only public client values belong here (the anon key, never the service_role key).
4. Fail with a clear message if configuration is missing, instead of a blank page.
Acceptance criteria: the live site signs in and loads data, with no "supabaseUrl is required" errors.For any other tool
Bug: on the live site the Supabase client fails to start with "Error: supabaseUrl is required.".
Evidence: "Error: supabaseUrl is required." — seen 12 times across ~5 sessions, on /checkout.
What to change:
1. Find the environment variables the Supabase client reads (for example VITE_SUPABASE_URL and VITE_SUPABASE_ANON_KEY).
2. Set them in the hosting provider's environment settings for production, with the same names the code uses, then rebuild and redeploy — build tools bake these in at build time.
3. Only public client values belong here (the anon key, never the service_role key).
4. Fail with a clear message if configuration is missing, instead of a blank page.
Acceptance criteria: the live site signs in and loads data, with no "supabaseUrl is required" errors.Vigilia catches this automatically
When this happens on your live app, Vigilia recognises it at once — no waiting, no AI credits — tells you who it affects, hands your AI the fix, and confirms it held with real visitors.