Database errors

getaddrinfo ENOTFOUND … neon.techCopy Anchor Link

Error: getaddrinfo ENOTFOUND ep-cool-name-123456.ap-southeast-1.aws.neon.tech

Why: your network's DNS refuses to look up Neon's hostnames. It's common on some Indian ISPs. Your database is fine; your computer just can't find it.

Fix: switch your computer to public DNS. Your internet still goes through your provider; only name lookups change.

nmcli connection show                     # find your Wi-Fi connection's name
nmcli connection modify "<wifi name>" ipv4.dns "1.1.1.1 8.8.8.8" ipv4.ignore-auto-dns yes
nmcli connection up "<wifi name>"

Then run the command again. If you're on a phone hotspot or office network, the same fix applies per network.

This only affects your computer: your live site on Vercel isn't affected.

Missing environment variable DATABASE_URLCopy Anchor Link

Missing environment variable DATABASE_URL. Run the setup script or copy .env.example to .env.local and fill it in.

Why: the app tried to query the database, but DATABASE_URL isn't set.

Fix:

• Locally: run npm run setup, or put your connection string in .env.local. The file must be named exactly .env.local, in the project root (next to package.json). Restart npm run dev after editing it.
• On Vercel: add DATABASE_URL under Settings → Environment Variables for Production, then redeploy.

DATABASE_URL is not set. Add it to .env.local first.Copy Anchor Link

From npm run make-admin. Same cause and fix as above: the script reads .env.local.

No account found for you@example.com. Sign up in the app first, then run this again.Copy Anchor Link

From npm run make-admin. Why: no user with that email exists in the database in DATABASE_URL.

Fix: sign up in the app first (with the same email; capitalisation doesn't matter). If you signed up on the live site, make sure .env.local points at the same database production uses.

Migrations failCopy Anchor Link

Migrations failed (see the output above). Fix it, then run `npm run setup` again.

Look at the output above it:

Failed query: … During prerenderingCopy Anchor Link

You see lots of these in the logs on every page load of signed-in pages, often with Better Auth errors.

Why: Next.js's partial prefetching was turned on. It renders signed-in pages alongside each request and aborts their queries.

Fix: keep partialPrefetching: false in next.config.ts. The kit ships with it off; check it wasn't changed.

drizzle-kit generate hangs or fails asking about renamesCopy Anchor Link

Is user_name column in user table created or renamed from another column?
❯ + user_name           create column
  ~ name › user_name    rename column

Why: Drizzle can't tell a rename from a delete-and-add, so it asks. In a non-interactive terminal (an AI agent, CI), the prompt can't be answered.

Fix: run npm run db:generate yourself in a normal terminal and pick the answer. Or write the migration by hand:

npx drizzle-kit generate --custom --name rename-user-name

Write the SQL (ALTER TABLE "user" RENAME COLUMN "name" TO "user_name";) in the new file, then check that npm run db:generate says there's nothing to change.

No transactions support in neon-http driverCopy Anchor Link

Why: the kit uses Neon's HTTP driver, which runs one statement per request and doesn't support db.transaction().

Fix: use db.batch([…]) to run several statements atomically. See Querying.

Pages are slow on the live siteCopy Anchor Link

Why: your server functions run far from your database. Each query crosses an ocean.

Fix: pin functions to the database's region in vercel.json. Setup does this when it deploys; see Function region. Check vercel.json has a regions entry and is committed.

Accounts I create locally show up in productionCopy Anchor Link

Why: setup uses one database for both. See Local and production share this database.