Auth.js · server log
AdapterError / table does not exist
[auth][error] AdapterError … The table `main.User` does not exist in the current database.What it means
One of the adapter's database calls failed. The cause line under it says why, and with Prisma it's usually a missing table or an unreachable database.
Common causes
- Migrations never ran against the production database
- DATABASE_URL points to SQLite on a serverless host, where the file doesn't persist
- Schema models renamed so they no longer match what the adapter expects
How to fix it
- Run npx prisma migrate deploy against production (or prisma db push while prototyping)
- Use Postgres in production. SQLite files don't survive serverless deploys
- Set debug: true once to see which adapter_ method failed
Prompt for Cursor or Claude Code
Auth.js logs AdapterError with a Prisma 'table does not exist' cause in production. Check DATABASE_URL and the Prisma provider for prod, then give me the exact migrate command to run and where to run it.Not quite your error? Paste yours into the free VibeBoot Doctor or browse the Auth.js error fixer.
next: skip the next one
Skip the setup. The VibeBoot SaaS Starter ships Auth.js v5 already wired (GitHub sign-in, optional email magic links, Prisma adapter), plus Stripe and a database on Next.js 16.4.3. $49, one-time.
14-day money-back guarantee · lifetime updates
Other Auth.js errors
$ fixed it? get the next one first
New fixes for what AI agents break, by email.
When we add a fix or a Cursor rule for a new Next.js, Auth.js, Prisma or Stripe break, it goes out in the VibeBoot newsletter. Free, occasional, unsubscribe in one click.