Reference
Troubleshooting
Every error message you are likely to hit, and what to do about it.
Start here
Nine times out of ten it is one of these three:
The wrong Supabase connection string
Only the Session pooler on port 5432 works. The other two fail in different, confusing ways.
Never seeded
Site starts, then every page errors. Your Supabase project has no tables yet.
Changed a variable without rebuilding
Environment changes only take effect on a new build or restart. Redeploy after editing them.
The site will not start
The site starts but pages error
Images and uploads
Store problems
Admin panel problems
Build problems
Messages that are normal
These appear in healthy deployments. Ignore them.
| Message | Why |
|---|---|
"next start" does not work with "output: standalone" configuration | A suggestion, not an error. The site serves correctly. |
WARN: No email adapter provided. Email will be written to console. | Expected — the theme ships without email. |
Payload: You are using an unsupported Next.js 16 version | Payload has not yet added this Next.js version to its tested list. |
Still stuck?
Collect these before asking for help — they answer most of the first questions:
- Which deployment route you followed
- Whether your
DATABASE_URIuses the session pooler (…pooler.supabase.com:5432) - Whether
bun run seedhas been run against that project, and what it printed - The exact error text, copied not described
- Your environment variable names — never the values