Prisma•11mo ago•

13 replies

Could not locate Query Engine

Repo: https://github.com/DarkstarXDD/interactive-card-details-form
Live site: https://interactive-card-details-form-darkstarxdd.vercel.app/

Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x".

Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x".

Hi, I get this error when i deploy the project to Vercel. (Let me know if you need the full error message i can send it)

I have searched online and came across multiple github discussions where others had encountered the same issue with different setups. I tried few solutions mentioned in those but nothing worked. I searched this server as well but there doesn't seem to be an exact solution.

- This issue does not happen in development. I ran

npm run build

npm run build

and tested this with a production version locally and still no errors.
- When deployed to Vercel there are no build errors.
- But at run time when i submit the data through my form and the Prisma query is called, it throws the error.

My setup is extremely simple since it's a small practice project.

-

Next.js 15.2.4

Next.js 15.2.4

, App Router.
-

prisma CLI

prisma CLI

and

@prisma/client 6.6.0

@prisma/client 6.6.0

.
- Calling the Prisma query in a Server Action.
- The database is Supabase Postgres.
- Used the new custom path option to define a path in

src/genereted/prisma/client

src/genereted/prisma/client

.
- Provider is the old

prisma-client-js

prisma-client-js

.
- I have removed the generated folder from git tracking, and have added

prisma generate

prisma generate

in a

postinstall

postinstall

script in the

package.json

package.json

. So the Prisma Client gets newly generated on the Vercel server during the production build.
- I have followed this guide and created a

globalForPrisma

globalForPrisma

as well. Inside that i directly import the client from the generated output. When in earlier versions i didn't define a custom output i imported from

@prisma/client

@prisma/client

.
- I have tried adding

binaryTargets

binaryTargets

as well, but didn't work.

Could not locate Query Engine

Repo: https://github.com/DarkstarXDD/interactive-card-details-form
Live site: https://interactive-card-details-form-darkstarxdd.vercel.app/

Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x".

Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x".

npm run build

npm run build

Next.js 15.2.4

Next.js 15.2.4

, App Router.
-

prisma CLI

prisma CLI

and

@prisma/client 6.6.0

@prisma/client 6.6.0

.
- Calling the Prisma query in a Server Action.
- The database is Supabase Postgres.
- Used the new custom path option to define a path in

src/genereted/prisma/client

src/genereted/prisma/client

.
- Provider is the old

prisma-client-js

prisma-client-js

.
- I have removed the generated folder from git tracking, and have added

prisma generate

prisma generate

in a

postinstall

postinstall

script in the

package.json

package.json

. So the Prisma Client gets newly generated on the Vercel server during the production build.
- I have followed this guide and created a

globalForPrisma

globalForPrisma

as well. Inside that i directly import the client from the generated output. When in earlier versions i didn't define a custom output i imported from

@prisma/client

@prisma/client

.
- I have tried adding

binaryTargets

binaryTargets

as well, but didn't work.

Could not locate Query Engine

Similar Threads

Could not locate Query Engine

Similar Threads

Similar Threads

Similar Threads