Prisma · runtime error · P1001
P1001: Can't reach database server
PrismaClientInitializationError: Can't reach database server at `db.example.supabase.co:5432`
Please make sure your database server is running at `db.example.supabase.co:5432`.What it means
Prisma couldn't open a network connection to the host and port in DATABASE_URL. Nothing about your schema or query yet: it's the network, the host or the database itself.
Common causes
- The local database (Docker, Postgres.app) isn't running
- A paused free-tier database (Supabase and Neon pause or suspend idle projects)
- The direct host is IPv6-only and your network or host has no IPv6: use the provider's pooler host
- Wrong host or port, or a firewall / IP allow list blocking the server
How to fix it
- Start or unpause the database, then retry
- Copy a fresh connection string from the provider dashboard (for Supabase from a serverless host, use the pooler connection string)
- Check the host's IP allow list if your provider has one
Prompt for Cursor or Claude Code
Prisma throws P1001 Can't reach database server. Without printing secrets, check the host and port in DATABASE_URL, tell me whether it's a direct or pooled connection, and list the likely causes for my provider (paused project, IPv6-only direct host, firewall). Don't change the schema.Not quite your error? Paste yours into the free VibeBoot Doctor or browse the Prisma error fixer.
next: skip the next one
Skip the setup. The VibeBoot SaaS Starter ships a ready prisma/schema.prisma and one Prisma client in src/lib/db.ts (SQLite by default, Postgres by changing the provider), plus auth and Stripe on Next.js 16.4.3. $49, one-time.
14-day money-back guarantee · lifetime updates
Other Prisma 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.