Prisma · deploy error
Prisma Client could not locate the Query Engine
PrismaClientInitializationError: Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x".
This happened because Prisma Client was generated for "darwin-arm64", but the actual deployment required "rhel-openssl-3.0.x".What it means
The client was generated on one OS (your Mac, Windows or a different Linux) and deployed to another, so the native engine file for the server isn't there.
Common causes
- The generated client or node_modules was committed or copied from your laptop
- A Docker image on Alpine (linux-musl) while the client was generated on Debian
- A monorepo or custom output path the bundler doesn't copy
How to fix it
- Run prisma generate during the build on the target machine, not locally
- Don't commit node_modules or the generated client
- If you must generate elsewhere, add the target to binaryTargets in the generator block
generator client {
provider = "prisma-client-js"
binaryTargets = ["native", "rhel-openssl-3.0.x"]
}Prompt for Cursor or Claude Code
Prisma can't find the query engine for the deployment runtime. Check whether the generated client or node_modules is committed, make sure prisma generate runs in the build on the server, and only if needed add the runtime from the error to binaryTargets.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.