Replies: 61 comments 58 replies
|
(Notes from another report of this #19564 (comment)) |
|
Have you tried to copy the engine in the suggested location? Did that work? Which package manager are you using? Is your workspace a monorepo setup? Is a bundler in use? If yes, which one? Is a framework in use? If yes, which one? Your project uses TypeScript or just JavaScript? When you saw our message, did it happen locally or in deployment? Where is your project deployed? Paste the error message |
|
Have you tried to copy the engine in the suggested location? Did that work? Yes. I'm using AWS Lambda and Prisma does not search the Lambda task root, and none of the paths Prisma searches are available to copy files. Which package manager are you using? npm@9.6.3 Is your workspace a monorepo setup? No, it's pretty standard https://arc.codes repo Is a bundler in use? If yes, which one? esbuild via architect/plugin-typescript Is a framework in use? If yes, which one? Yes, https://arc.codes Your project uses TypeScript or just JavaScript? TypeScript When you saw our message, did it happen locally or in deployment? After deployment, in the Lambda execution environment Where is your project deployed? AWS Lambda |
|
Did you end up finding a fix for this? I am having exactly the same issues. I was hoping to deploy a lambda layer.. |
|
I also facing with same issue, did you found the solution @jeremyruppel @owlyowl |
Have you tried to copy the engine in the suggested location? Did that work?Our error message suggested you to copy the engine somewhere. How did that go? Which package manager are you using?For instance npm, pnpm, or yarn. Please attach the version if you know it. I prefer use the pnpm. But recently i found many lib not support the pnpm. I had to rollback my project. It's suck. Is your workspace a monorepo setup?Is your setup hosting multiple packages in a single workspace? Is a bundler in use? If yes, which one?Are you using webpack, swc, esbuild, rollup, or any other bundler? Is a framework in use? If yes, which one?Are you using Next.js, Next, or any other framework? Your project uses TypeScript or just JavaScript?Do you prefer using TypeScript or JavaScript within your project, or both? perfer using TypeScript. When you saw our message, did it happen locally or in deployment?The message was "Please help us by answering a few questions". On my local environment. I try to use the pkg build a single execute file. Where is your project deployed?Are you deploying to Vercel, Netlify, Lambda, or something else? I still in the develop this project. I will deploy on the factory window PC. So I had to build a single executable file. Finally. Can you support me on the pkg build Prisma project issue? |
|
Have you tried to copy the engine in the suggested location? Did that work? Which package manager are you using? Is your workspace a monorepo setup? Is a bundler in use? If yes, which one? Is a framework in use? If yes, which one? Your project uses TypeScript or just JavaScript? When you saw our message, did it happen locally or in deployment? Where is your project deployed? |
Have you tried to copy the engine in the suggested location? Did that work?Trying to avoid that right now, as this is only happening in production/deployment. Will update here if/when we try that. Which package manager are you using?yarn v1.22.19 Is your workspace a monorepo setup?Yes, however hoisting for prisma has already been disabled due to past issues. Is a framework in use? If yes, which one?Next.js 13 Your project uses TypeScript or just JavaScript?TypeScript When you saw our message, did it happen locally or in deployment?Deployment Where is your project deployed?AWS ECR |
Have you tried to copy the engine in the suggested location? Did that work?Worked perfectly, but of course, the bundler should just get it right. Which package manager are you using?Used yarn, but tried with npm, too Is your workspace a monorepo setup?Single workspace here Is a bundler in use? If yes, which one?Using Is a framework in use? If yes, which one?No framework Your project uses TypeScript or just JavaScript?TypeScript When you saw our message, did it happen locally or in deployment?The message was "Please help us by answering a few questions". Happened locally during setting up a fresh project on a Windows machine Where is your project deployed?Are you deploying to Vercel, Netlify, Lambda, or something else? No deployment yet |
|
Here is an issue that triggers a link to this discussion: #22142 |
Have you tried to copy the engine in the suggested location? Did that work?Copied (rhel-openssl-3.0.x) and existing in lamda zip, but still not working Which package manager are you using?pnpm@8.12.0 Is your workspace a monorepo setup?Yes Is a bundler in use? If yes, which one?webpack Is a framework in use? If yes, which one?nestjs 10 Your project uses TypeScript or just JavaScript?TypeScript When you saw our message, did it happen locally or in deployment?deployment Where is your project deployed?AWS Lamda |
|
Good evening @millsp, many thanks for the quick feedback!
So we have the service, within there is a directory called With that i getting:
|
|
Yes, the engine should then be placed right next to |
|
Alternatively, as per the message, you could rename |
|
Hey @millsp 👋 , Moved also the schema, hopefully that is now correct 😄 . (Changed to arm64 in the same breath, don't be surprised.)
|
|
Nice, glad to hear. Yes, we indeed had small changes in that area in the mean time as a side-effect of another fix. |
|
Have you tried to copy the engine in the suggested location? Did that work? Which package manager are you using? Is your workspace a monorepo setup? Is a bundler in use? If yes, which one? Is a framework in use? If yes, which one? Your project uses TypeScript or just JavaScript? When you saw our message, did it happen locally or in deployment? Where is your project deployed? Note: |
|
yes it was but somehow it was not detecting it there |
|
This sounds interesting. Would you be able to build/share a reproduction? |
|
I have a similar issue, it hasn't searched /workspaces/src/prisma/node_modules/.prisma/client which is where this file is located /workspaces/src/website/node_modules/.prisma/client when I copy the libquery_engine-debian-openssl-3.0.x.so.node file to the /workspaces/src/prisma/node_modules/@prisma/client location, it works |
|
Thanks for the context. Would you be able to give us a repro? |
|
Im my monrepo, The following locations have been searched:
my-app/packages/jobs/node_modules/.prisma/client
my-app/packages/jobs/.trigger/tmp
my-app/node_modules/@prisma/client
my-app/packages/jobs/.prisma/client
/tmp/prisma-engines |
|
Have you tried to copy the engine in the suggested location? Did that work? Which package manager are you using? Is your workspace a monorepo setup? Is a bundler in use? If yes, which one? Is a framework in use? If yes, which one? Your project uses TypeScript or just JavaScript? When you saw our message, did it happen locally or in deployment? Where is your project deployed? |
|
I don't know but if this is a solution but using turborepo with pnpm workspaces, I added a script to the prisma package, and in the root directory I ran the following pnpm --filter @workspace/prisma prisma:reset
pnpm --filter @workspace/prisma prisma:migrate-devThis is from the "scripts": {
"build": "prisma generate",
"format": "prisma format",
"post-install": "prisma generate",
"prisma:generate": "prisma generate",
"prisma:migrate-dev": "prisma migrate dev",
"prisma:migrate-deploy": "prisma migrate deploy",
"prisma:seed": "prisma db seed",
"prisma:studio": "prisma studio",
"prisma:reset": "prisma migrate reset"
}, |
|
so you are again migrating the schemas? after reset |
|
Have you tried to copy the engine in the suggested location? Did that work? Which package manager are you using? Is your workspace a monorepo setup? Is your setup hosting multiple packages in a single workspace? Is a bundler in use? If yes, which one? Is a framework in use? If yes, which one? Your project uses TypeScript or just JavaScript? When you saw our message, did it happen locally or in deployment? Where is your project deployed? This can help us better understand where the engine was searched for |
|
Have you found any solution? It worked for me before, but at some point it just refused to work and I don’t know what to do. |
|
Have you tried to copy the engine in the suggested location? Did that work? Nope.. I am only having this issue on Vercel PREVIEW deployments. for some reason it is working on production Which package manager are you using? pnpm@8.15.0 on local dev environment. I don't know what vercel is using when I deploy it there on preview Is your workspace a monorepo setup? Yep. TurboRepo monorepo; Is a bundler in use? If yes, which one? next bundler? I think they use webpack idk Is a framework in use? If yes, which one? NextJs Your project uses TypeScript or just JavaScript? TypeScript When you saw our message, did it happen locally or in deployment? Vercel PREVIEW deployments. for some reason it is working on production. Where is your project deployed? Vercel serverless function |
|
No the patch is related to something else. |
|
So the plugin seems to be malfunctioning for you. Is that consistent? |
|
No, it's working fine. The branch I shared has it removed in next.config.js to force the error appear. My main branch has the plugin and it is working well |
|
Ah ok, great. In the meantime this is how you should keep it then :) We want to work into removing this plugin completely. |
|
any solution for express-node backend? |
|
UPDATE: I was able to solve this by putting the following in my github action. Without that, it would stop at "native" and only pick up env:
PRISMA_CLI_BINARY_TARGETS: 'debian-openssl-3.0.x'I'm having trouble making my github action build -> google cloud function work. My However, after having the github action run The two engine files that are available are in the Oddly when I run I need to build the project on a different platform (github actions) than the run is happening (google cloud function), so it's very problematic that there's no Is there a way I can get this engine via the prisma CLI or soemthing, during my build step? I didn't see a way to do this in the prisma CLI, but maybe just missed it. Have you tried to copy the engine in the suggested location? Did that work?I can't, it's not available in the github action environment Which package manager are you using?Yarn Is your workspace a monorepo setup?Yes Is your setup hosting multiple packages in a single workspace?No, the google cloud function is not Is a bundler in use? If yes, which one?Yes, it's a custom one we wrote, so we can copy in the engine files ourselves... if they were the right version Is a framework in use? If yes, which one?Sort of... the google cloud "framework" Your project uses TypeScript or just JavaScript?Typescript When you saw our message, did it happen locally or in deployment?Deployment Where is your project deployed?
Paste the error message |
|
@millsp the problem I'm having is that the |
|
Actually, I was just able to solve this by putting the following in my github action. Without that, prisma engine downloads would stop at env:
PRISMA_CLI_BINARY_TARGETS: 'debian-openssl-3.0.x' |
|
If you put |
|
hey @mattgraphlan do i need to add that env in a platform like render or vercel where build happens in there machine not github actions? |
Have you tried to copy the engine in the suggested location? Did that work?We specify the prisma output as The error states: So when we copy the engine to /usr/src/app it works Which package manager are you using?npm Is your workspace a monorepo setup?We build these files from an Nx monorepo which is why we're trying to output to a relative directory inside the project. Everything works locally. Is a bundler in use? If yes, which one?Webpack through the @nx/webpack plugin with the following config Is a framework in use? If yes, which one?NestJS Your project uses TypeScript or just JavaScript?Typescript When you saw our message, did it happen locally or in deployment?Only in our deployed container which uses the following entrypoint script Where is your project deployed?EKS Paste the error messageError Logs |
It didn't specify how to do that copy, and Vercel's build procedure and where files are and should be is opaque to me. Yet I tried adding a command to copy the file to each of the locations it suggested. Some failed (directory didn't exist), others succeeded, so I guess it ended up in some of those spots. Yet no, it did not help.
npm 10.9.2
No.
I thought I was using Turbopack, but maybe that's just a dev-time thing? I guess it's using webpack in production? Or whatever is default for Next 15.
Aren't Next.js and Next the same thing? Next 15.3.
TS.
Deployment.
I'm trying out Vercel.
I initially avoided trying the "@prisma/nextjs-monorepo-workaround-plugin" I see mentioned in various replies in this discussion, because I'm not using a monorepo. I tried everything else I saw in this thread with no luck. Eventually I did try the workaround plugin and it did help me. So I guess the problem, and that solution, are not unique to monorepos? |
|
Have you tried to copy the engine in the suggested location? Did that work? Which package manager are you using? Is your workspace a monorepo setup? Is a bundler in use? If yes, which one? Is a framework in use? If yes, which one? Your project uses TypeScript or just JavaScript? When you saw our message, did it happen locally or in deployment? Where is your project deployed? Paste the error message I also tried various different solutions that are mentioned in previous comments, but none of them worked out for me (having output path, removing it, adding a vercel-build script, etc). Perhaps because all my backend APIs are server actions, and Vercel simply didn't copy the proper files. Very frustrating. |
|
Update: Resolved after installing Prisma Next.js Plugin and updating next.config accordingly. |
|
This thread is not circunscribed to monorepo only. |
|
No, but the name of the plugin suggests that it is specific to monorepos. |
This actually solved this issue for me |
|
Have you tried to copy the engine in the suggested location? Did that work? Which package manager are you using? Is your workspace a monorepo setup? Is a bundler in use? If yes, which one? Is a framework in use? If yes, which one? Your project uses TypeScript or just JavaScript? When you saw our message, did it happen locally or in deployment? Where is your project deployed? Paste the error message |
|
the problem is Prisma binary engines cannot run on Vercel (serverless and edge environments). You basically need driver adapters that can run on these environments. Read this article: https://www.prisma.io/blog/serverless-database-drivers-KML1ehXORxZV |
|
Thank you for the suggestion! I followed the Neon setup guide as recommended, but unfortunately it still didn’t work in my case. I’ve decided to stick with Prisma v5.14.0 for now — it works reliably with my current deployment. |
|
1. What bundler are you using? 2. What is the target environment or platform you're deploying to? 3. What is the version of Prisma Client you're using? 4. Please paste the full error message This is likely caused by a bundler that has not copied "libquery_engine-rhel-openssl-3.0.x.so.node" next to the resulting bundle. The following locations have been searched: 5. How are you importing Prisma Client? 6. What workarounds have you tried?
7. Anything else you’d like to share? To get around Prisma's bundling limitations, we manually use copy-webpack-plugin to include:
However, to make it work at runtime, we must duplicate these files inside every individual service/module folder, like: dist/ This duplication works, but is painful and not scalable across many services. It would be much more efficient if Prisma:
|
|
Have you tried to copy the engine in the suggested location? Did that work? Which package manager are you using? Is your workspace a monorepo setup? Is a bundler in use? If yes, which one? Is a framework in use? If yes, which one? Your project uses TypeScript or just JavaScript? When you saw our message, did it happen locally or in deployment? Where is your project deployed? Paste the error message |
|
https://www.npmjs.com/package/@prisma/nextjs-monorepo-workaround-plugin did work to fix this for us |
|
I am having the same problem when trying to use prisma-client-js with defined output. What is more I am using Zenstack. |
|
2025-07-26T09:28:36.042Z [error] Unhandled Rejection: Error [PrismaClientInitializationError]: 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 a bundler that has not copied "libquery_engine-rhel-openssl-3.0.x.so.node" next to the resulting bundle. We would appreciate if you could take the time to share some information with us. The following locations have been searched: |
|
You could try to set Not too sure if this is the case mentioned here, my case was bundling with pkg/deno. |
|
Have you tried to copy the engine in the suggested location? Did that work? Which package manager are you using? Is your workspace a monorepo setup? Is a bundler in use? If yes, which one? Is a framework in use? If yes, which one? Your project uses TypeScript or just JavaScript? When you saw our message, did it happen locally or in deployment? Where is your project deployed? Paste the error message: Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x". This is likely caused by a bundler that has not copied "libquery_engine-rhel-openssl-3.0.x.so.node" next to the resulting bundle. We would appreciate if you could take the time to share some information with us. The following locations have been searched: I've also tried manually setting the arch for my engine with SST. Please note this is targetting neondb but that shouldn't matter. My guess is that prisma just really doesn't like the 3.0.x which sucks because AWS seems to need it. my generator: when I searched my local node_modules/.prisma/client I got: so it's IN there. Whether it's being sent to AWS, or used while in AWS, I can't say. This is causing my project to be unusable with prisma. |
|
Brother did the your issue got resolved? I am in same problem but I am deploying this on Vercel and it also requries rhel-openssl-3.0.x.so.node. I added it and 2 days back and it was running smoothly but after when I made some further changes and deployed my code, the issue came back and isnt resolving for last 2 days. If you can help me in this matter it would mean a lot |
|
My friend sorry this happened to you. I did fix this. My discovery may not work for you so be aware. I am using SST to deploy which automatically provisions certain resources. In my case, I was provisioning it for a cron job which affected the database. Prisma was being used to do this database change. So this error was coming from a specific cron lambda running prisma, not the sst deployed nextjs thing. What I discovered is that the from these provisioned resources/lambdas it is essentially impossible to use prisma. For some reason prisma will not recognize those rhel etc "runners" (I think it's called a runner forgive me if I misremember). There's nothing I found that could make prisma actually discover the runner. What I'm saying is that if have the same issue I had, nothing you can do will fix it. But all is not lost. Because the cron job did not NEED to do the database work itself. I made the cron job do a fetch to an API within the nextjs app itself. This nextjs api endpoint does the database changes that the cron was supposed to do. Since nextjs has no problem running prisma, this workaround takes care of the problem. It is a hack and it is ugly but it works. I also added an internal only pass code so that some random person who finds the endpoint can't simply execute what the cron does by themselves. 🙏🙏🙏 hope this works for you my friend and please let me know. |
|
My issue is resolved now, brother, thanks for checking in. I was migrating a backend login API route to a Next.js server action (since the rest of the app was already using server actions). During the process, I also updated the JWT and cookie logic, name, expiry, and storage. It appears that I forgot to assign it properly, so when Prisma attempted to fetch the user, it couldn’t complete the flow and assign the cookie for login. That’s why Vercel was throwing the rhel-openssl-3.0.x.so.node error, even though the generator was present. I rolled back to the previous stable version, re-implemented the changes carefully, and now prod is working fine. |
|
Sorry my suggestion didn't help then! But thanks for the update! |
|
No worries brother, your workaround idea was actually really insightful. Even though my issue turned out to be on my end, I’m glad you shared it because it might help me or others in future. I really appreciate your time and help, means a lot! |
|
Resoved by using the nextjs monorepo workaround plugin. It was not recommended in my error message, but I did find it reading through this error thread. https://www.npmjs.com/package/@prisma/nextjs-monorepo-workaround-plugin Which package manager are you using? Is your workspace a monorepo setup? Is a bundler in use? If yes, which one? Is a framework in use? If yes, which one? Your project uses TypeScript or just JavaScript? When you saw our message, did it happen locally or in deployment? Where is your project deployed? Paste the error message 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 a bundler that has not copied "libquery_engine-rhel-openssl-3.0.x.so.node" next to the resulting bundle. We would appreciate if you could take the time to share some information with us. The following locations have been searched: |
Have you tried to copy the engine in the suggested location? Did that work?Our error message suggested you to copy the engine somewhere. How did that go? Which package manager are you using?For instance Is your workspace a monorepo setup?Is your setup hosting multiple packages in a single workspace? Is a bundler in use? If yes, which one?Are you using Is a framework in use? If yes, which one?Are you using Your project uses TypeScript or just JavaScript?Do you prefer using TypeScript or JavaScript within your project, or both? When you saw our message, did it happen locally or in deployment?The message was "Please help us by answering a few questions". Where is your project deployed?Are you deploying to Vercel, Netlify, Lambda, or something else? Paste the error messageThis can help us better understand where the engine was searched for |
|
The same here. I'm using Vercel and I got an error like this: |
|
Have you tried to copy the engine in the suggested location? Did that work? Which package manager are you using? Is your workspace a monorepo setup? Is a bundler in use? If yes, which one? Is a framework in use? If yes, which one? Your project uses TypeScript or just JavaScript? When you saw our message, did it happen locally or in deployment? Where is your project deployed? Paste the error message |
|
Next.js 16 + turbopack in vercel, I fix it by: prisma.schema and next.config.ts/mjs/js from this article: https://qiita.com/benjuwan/items/1016afb442967eb742e7 |
|
Have you tried to copy the engine in the suggested location? Did that work? Which package manager are you using? Is your workspace a monorepo setup? Is a bundler in use? If yes, which one? Is a framework in use? If yes, which one? Your project uses TypeScript or just JavaScript? When you saw our message, did it happen locally or in deployment? Where is your project deployed? Paste the error message |
and others
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi, you have been directed to this discussion 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 appreciate it if you could take 5 minutes to answer a few questions for us. You can write your reply directly in this discussion as a comment. Copy and paste these questions in your answer, and leave the answer blank if you don't know.
Have you tried to copy the engine in the suggested location? Did that work?
Our error message suggested you to copy the engine somewhere. How did that go?
Which package manager are you using?
For instance
npm,pnpm, oryarn. Please attach the version if you know it.Is your workspace a monorepo setup?
Is your setup hosting multiple packages in a single workspace?
Is a bundler in use? If yes, which one?
Are you using
webpack,swc,esbuild,rollup, or any other bundler?Is a framework in use? If yes, which one?
Are you using
Next.js,Next, or any other framework?Your project uses TypeScript or just JavaScript?
Do you prefer using TypeScript or JavaScript within your project, or both?
When you saw our message, did it happen locally or in deployment?
The message was "Please help us by answering a few questions".
Where is your project deployed?
Are you deploying to Vercel, Netlify, Lambda, or something else?
Paste the error message
This can help us better understand where the engine was searched for
All reactions