Can't ran 'npx prisma init'
See original GitHub issueHello! I need some help with installation Prisma.
When I run the command “npx prisma init”, I get an error like this
Downloading Prisma engines for Node-API for windows [ ] 0%Error: request to https://binaries.prisma.sh/all_commits/b71d8cb16c4ddc7e3e9821f42fd09b0f82d7934c/windows/migration-engine.exe.gz.sha256 failed, reason: self signed certificate in certificate chain
in the console.
I downloaded binaries and ran scripts:
"prismaEngine": "set PRISMA_MIGRATION_ENGINE_BINARY=.C:/Users/myPath/migration-engine.exe.gz set PRISMA_INTROSPECTION_ENGINE_BINARY=.C:/Users/myPath/introspection-engine.exe.gz set PRISMA_QUERY_ENGINE_BINARY=.C:/Users/myPath/query_engine.dll.node.gz set PRISMA_FMT_BINARY=.C:/Users/myPath/prisma-fmt.exe.gz"
I get: Process finished with exit code 0
And then I tried to ran “npx prisma init” again. And caught the same error.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:5 (3 by maintainers)
Top Related StackOverflow Question
It is a common corporate IT practice to decrypt/re-encrypt TLS traffic through their proxies so they can inspect packets flowing across the border of their network (for cybersecurity and information security purposes). When they re-encrypt the traffic, they sign the encrypted packet with their own cert.
For all of this to work, software that enforces TLS needs to be configurable such that we can make it aware that there is a new certificate authority (CA) that we want to accept as valid (the CA of the corporation).
Is there a way to configure prisma to accept another CA?
And just to save someone from needing to read through that other thread, here was the answer to my above question:
The way to configure prisma (and many other npm modules) to accept another CA is to set the environment variable NODE_EXTRA_CA_CERTS to the path to your .pem file.