Not compatible with OpenSSL version 3
See original GitHub issueBug description
I get this error:
Error: Unknown binaryTarget debian-openssl-3.0.x and no custom binaries were provided
This error should have been fixed in prisma 3.3.1 i believe.
OpenSSL version 3.0.2
I’m on wsl 2, ubuntu 22.04
Prisma Schema
How to reproduce
- Be on windows
- Install ubuntu 22.04 WSL 2 (maybe ubuntu 22.04 without wsl, may not work tho since i don’t have access to a native-linux machine)
- Bootstrap any project with
prisma@4.1.1
and@prisma/client@4.1.1
- Run
prisma generate
Then you should get something like this:
$ yarn dlx dotenv-cli -c local prisma generate
➤ YN0000: ┌ Resolution step
➤ YN0000: └ Completed in 3s 906ms
➤ YN0000: ┌ Fetch step
➤ YN0000: └ Completed
➤ YN0000: ┌ Link step
➤ YN0000: └ Completed
➤ YN0000: Done in 3s 989ms
// ^^ Why This? (Maybe bc i'm running yarn pnp?)
Error: Unknown binaryTarget debian-openssl-3.0.x and no custom binaries were provided
Expected behavior
That prisma works without error.
Prisma information
// This is your Prisma schema file,
// learn more about it in the docs: https://pris.ly/d/prisma-schema
generator client {
provider = "prisma-client-js"
output = "../lib/prisma-client"
binaryTargets = ["native"]
}
// Ignore this generator
generator typegraphql {
provider = "typegraphql-prisma"
output = "../lib/db-resolvers"
}
datasource db {
provider = "mysql"
url = env("DATABASE_URL")
}
model Animal {
id Int @id @default(autoincrement())
age String
name String
}
Environment & setup
- OS: Windows 11 (but error is happening on wsl 2 ubuntu 22.04)
- Database: mysql (but not relevant)
- Node.js version: v16.16.0
Prisma Version
4.1.1
Issue Analytics
- State:
- Created a year ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
OpenSSL 3.0 Has Been Released!
OpenSSL 3.0 is a major release and not fully backwards compatible with the previous release. Most applications that worked with OpenSSL ...
Read more >OpenSSL 3.0: What you should know - SSLTrust
OpenSSL 3.0 constitutes a major version and is NOT backwards compatible. Additionally, OpenSSL 3.0 includes a new module which enforces only ...
Read more >Replace OpenSSL 1.1.1 with OpenSSL 3.0.0 #40106 - GitHub
OpenSSL 3.0 is a major release and not fully backwards compatible with the previous release. Most applications that worked with OpenSSL 1.1.1 ...
Read more >The experience of bringing OpenSSL 3.0 into Red ... - Red Hat
OpenSSL 3.0 strives to be as API compatible as possible with version 1.1.1, but it is ABI incompatible. While, in most cases, ...
Read more >Is OpenSSL V3.0.0 compatible with V1.1.1 - Stack Overflow
0.0 not work like v1.1.1? C:\openssl3> openssl pkcs12 -export -name tomcat -in cert.cer -inkey key -out ks300.p12 C:\ ...
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
yarn dlx [command]
just executes dependencies bin file, and puts node_modules/.bin at path.dotenv-cli -c local
just loads my environment variables. I got the error withprisma generate
, But for some weird reason it worked later, without any reinstall of deps 🤷🏼♂️Optimally just open a new issue with a more targetted description of the problem.