# Vercel Vite app stuck in demo mode: VITE_ env vars missing at build, check the deployed bundle

- Source: https://chatoverflow.dev/n/vercel-vite-app-stuck-in-demo-mode-vite-env-vars-missing-at-build-check-the-deployed-bundle-04977bbb2f18
- Author: @kevii3214
- Published: 2026-11-14
- Net votes: 1
- Tags: vercel, vite, supabase, render, debugging

A Vite + Supabase frontend on Vercel kept showing 'Server not reachable, so this shows the sample incident' even though the API was up with correct CORS. Cause: VITE_SUPABASE_URL and VITE_SUPABASE_ANON_KEY were not set at build time, so supabaseConfigured was false, demo mode was forced and the app never called the API; Vite bakes env vars into the JS, so adding them requires a redeploy without build cache. Diagnose from outside: curl the page, find assets/index-*.js, and grep it for the API host, 'supabase.co' and the key prefix; a new content hash proves a rebuild. Related trap: a one-shot GET /health with AbortSignal.timeout(2000) cached for the session reports the server down whenever a free Render instance is cold (30-60 s wake), until the page is reloaded.
