Issue on vercel deploy
What is this issue on vercel deploy? I use neon db
2025-10-12T06:56:40.703Z [error] 2025-10-12T06:56:40.696Z ERROR [Better Auth]: PrismaClientKnownRequestError Error [PrismaClientKnownRequestError]:
Invalid
prisma.verification.create() invocation:
Error validating datasource db: the URL must start with the protocol prisma:// or prisma+postgres://
at async Object.create (.next/server/app/api/auth/[...all]/route.js:9:7692)
at async Object.create (.next/server/app/api/auth/[...all]/route.js:155:129360)
at async createWithHooks (.next/server/app/api/auth/[...all]/route.js:2:56452)
at async Object.createVerificationValue (.next/server/app/api/auth/[...all]/route.js:2:65184)
at async af (.next/server/app/api/auth/[...all]/route.js:11:6595)
at async (.next/server/app/api/auth/[...all]/route.js:23:23296) {
code: 'P6001',
meta: [Object],
clientVersion: '6.17.1'
}
2025-10-12T06:56:40.704Z [error] # SERVER_ERROR: Error [PrismaClientKnownRequestError]:
Invalid prisma.verification.create() invocation:
Error validating datasource db: the URL must start with the protocol prisma:// or prisma+postgres://
at async Object.create (.next/server/app/api/auth/[...all]/route.js:9:7692)
at async Object.create (.next/server/app/api/auth/[...all]/route.js:155:129360)
at async createWithHooks (.next/server/app/api/auth/[...all]/route.js:2:56452)
at async Object.createVerificationValue (.next/server/app/api/auth/[...all]/route.js:2:65184)
at async af (.next/server/app/api/auth/[...all]/route.js:11:6595)
at async (.next/server/app/api/auth/[...all]/route.js:23:23296) {
code: 'P6001',
meta: [Object],
clientVersion: '6.17.1'
}
5 Replies
You selected to wait for the human sages. They'll share their wisdom soon.
Grab some tea while you wait, or check out
#ask-ai if you'd like a quick chat with the bot anyway!I use this command also
prisma generate --no-engine && prisma migrate deploy && next build
#ask-ai
Are you still observing the issue?
yes
this issue
2025-10-13T15:23:01.157Z [error] 2025-10-13T15:23:01.155Z ERROR [Better Auth]: INTERNAL_SERVER_ERROR Error [PrismaClientInitializationError]:
Invalid
prisma.session.findFirst() invocation:
Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x".
We detected that you are using Next.js, learn how to fix this: https://pris.ly/d/engine-not-found-nextjs.
This is likely caused by tooling that has not copied "libquery_engine-rhel-openssl-3.0.x.so.node" to the deployment folder.
Ensure that you ran prisma generate and that "libquery_engine-rhel-openssl-3.0.x.so.node" has been copied to ".next/server/chunks".
We would appreciate if you could take the time to share some information with us.
Please help us by answering a few questions: https://pris.ly/engine-not-found-tooling-investigation
The following locations have been searched:
/var/task/.next/server/chunks
/vercel/path0/src/generated
/vercel/path0/src/generated/prisma
/vercel/path0/.prisma/client
/tmp/prisma-engines
at async Object.findOne (.next/server/chunks/7483.js:176:566719)
at async Object.findOne (.next/server/chunks/7483.js:166:45098)
at async Object.findSession (.next/server/chunks/7483.js:2:60593)
at async (.next/server/chunks/7483.js:168:134695)
at async d (.next/server/chunks/7483.js:97:70897)
at async c.<computed> [as getSession] (.next/server/chunks/7483.js:97:12430) {
clientVersion: '6.17.1',
errorCode: undefined,
retryable: undefined
}
2025-10-13T15:23:01.158Z [error] Error creating EdgeStore context: [Error [APIError]: Failed to get session] {
status: 'INTERNAL_SERVER_ERROR',
body: [Object],
headers: {},
statusCode: 500
}Prisma
Prisma | Instant Postgres plus an ORM for simpler db workflows
Build, fortify, and grow your application easily with an intuitive data model, type-safety, automated migrations, connection pooling and caching.
GitHub
User questions: Engine not found (tooling) · prisma prisma · Disc...
Hi, you have been directed to this issue because we want to learn more about your project setup. Thanks to your answers, we will be able to make better design decisions in the future. We'd appr...
I added
import type { NextConfig } from "next";
const { PrismaPlugin } = require("@prisma/nextjs-monorepo-workaround-plugin");
const nextConfig: NextConfig = {
images: {
remotePatterns: [
{
hostname: "lh3.googleusercontent.com",
},
],
},
webpack: (config, { isServer }) => {
if (isServer) {
config.plugins.push(new PrismaPlugin());
}
return config;
},
};
export default nextConfig;
my dependancy versions
prisma": "^6.17.1",
"@prisma/client": "^6.17.1",
"@prisma/nextjs-monorepo-workaround-plugin": "^6.17.1",
prisma client look like this
generator client {
provider = "prisma-client"
output = "../src/generated/prisma"
previewFeatures = ["fullTextSearchPostgres"]
}