Invalid Binary Target for OpenSSL V3 on CentOS Stream 9
See original GitHub issueBug description
Prisma CLI fails to initialize when deploying a new or existing project to a CentOS Stream 9 server. The error references an unknown binary target for openssl 3.0.x.
# npx prisma init
prisma:engines binaries to download libquery-engine, migration-engine, introspection-engine, prisma-fmt +0ms
prisma:download file /root/hello-prisma/node_modules/@prisma/engines/libquery_engine-rhel-openssl-3.0.x.so.node does not exist and must be downloaded +0ms
Error: Error: Unknown binaryTarget rhel-openssl-3.0.x and no custom binaries were provided
at /root/hello-prisma/node_modules/@prisma/engines/dist/index.js:21277:15
at async Promise.all (index 0)
at async /root/hello-prisma/node_modules/@prisma/engines/dist/index.js:6621:29
The same error is received when trying to initialize the new project directory or generating artifacts (prisma client) from an existing project.
OpenSSL v3.0.1 is confirmed to be installed.
# openssl version
OpenSSL 3.0.1 14 Dec 2021 (Library: OpenSSL 3.0.1 14 Dec 2021)
# cat /etc/redhat-release
CentOS Stream release 9
Running npx prisma
completes successfully and shows help output.
How to reproduce
- Start with an updated CentOS Stream 9 server with Node installed.
- Create a new project.
mkdir hello-prisma
- Enter the directory.
cd hello-prisma
- Initialize the project.
npm init -y
- Install prisma.
npm install prisma --save-dev
- Test prisma to make sure it is working.
npx prisma
- Initialize prisma.
npx prisma init
- The error is now received.
Expected behavior
Prisma CLI should work as expected correctly generate the project files.
Prisma information
N/A as the error prevents a project from getting this far.
Environment & setup
- OS: CentOS Stream 9
- Database: MySQL
- Node.js version: v16.10.0
Prisma Version
Prisma version flag fails to complete. I can confirm prisma was installed from NPM as detailed in the quickstart.
# npx prisma -v
prisma:engines binaries to download libquery-engine, migration-engine, introspection-engine, prisma-fmt +0ms
prisma:download file /root/hello-prisma/node_modules/@prisma/engines/libquery_engine-rhel-openssl-3.0.x.so.node does not exist and must be downloaded +0ms
Error: Error: Unknown binaryTarget rhel-openssl-3.0.x and no custom binaries were provided
at /root/hello-prisma/node_modules/@prisma/engines/dist/index.js:21277:15
at async Promise.all (index 0)
at async /root/hello-prisma/node_modules/@prisma/engines/dist/index.js:6621:29
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:8 (4 by maintainers)
Top Results From Across the Web
openssl 3.0.3 not found - CentOS forum
Hi, I'm updating the openssl from 3.0.0 to 3.0.7 but there was an error. the ... Neither of those are versions supplied by...
Read more >Unknown binaryTarget debian-openssl-3.0.x and no custom ...
Error: Unknown binaryTarget debian-openssl-3.0.x and no custom binaries were provided error Command failed with exit code 1. openssl · prisma.
Read more >OpenSSL 3.0 - OpenSSLWiki
The "low level" APIs are targeted at a specific algorithm implementation. For example, the EVP APIs provide the functions `EVP_EncryptInit_ex`, ...
Read more >2059101 – rpm checksig fails on valid rpm - Red Hat Bugzilla
On CentOS Stream 9: Downgraded openssl: openssl-3.0.1-5.el9.x86_64.rpm openssl-libs-3.0.1-5.el9.x86_64.rpm # rpm --checksig -v ...
Read more >Before You Get Mad About The CentOS Stream Change ...
All of the key pieces of software in RHEL like the kernel, glibc, openssl, are in compatibility level 1 or 2 which means...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is fixed and will ship with 3.13.0: https://github.com/prisma/prisma/issues/11356#issuecomment-1103977740 That version will be release next Tuesday, and this comment includes instructions how you can temporarily use the development version of Prisma to confirm it works: https://github.com/prisma/prisma/issues/11356#issuecomment-1106208683
I have the issue for debian
Error: Unknown binaryTarget debian-openssl-3.0.x and no custom binaries were provided