`npx prisma` results in self-signed cert error, though npm config cafile is properly set

Bug description

When I run npx prisma migrate, I get the following error:

Error: request to https://binaries.prisma.sh/all_commits/73e60b76d394f8d37d8ebd1f8918c79029f0db86/windows/prisma-fmt.exe.gz.sha256 failed, reason: self signed certificate in certificate chain

Because my corporate proxy re-signs TLS traffic. I have npm configured to accept a cafile that describes the self-signed cert, which allows npm install to proceed w/o issue. However, the npx prisma migrate fails … presumably because prisma itself is trying to make an https request and is unaware of the npm cafile setting?

I believe we need a way make prisma aware of the cafile.

How to reproduce

1. Open a terminal on a computer that is on a network behind a proxy that re-signs TLS traffic
2. Execute the command “npx prisma migrate”

That should result in the error I’m seeing.

Expected behavior

I expect npx prisma migrate to run w/o error. 😃

Prisma information

N/A

Environment & setup

• OS: Windows 10
• Database: PostgreSQL
• Node.js version: v14.18.1

Prisma Version

Ironically, npx prisma -v results in the same error. However, inspecting my node_modules, I see that it is:

3.9.2

[eric79]

Actually, one of my teammates pointed out that if I set the environment variable NODE_EXTRA_CA_CERTS to the path to my .pem file, then npx prisma migrate works as intended.

[mm-gmbd]

Having this same issue. Came across this other ticket where someone was having an issue with a self-signed cert in the chain.

From @janpio’s comment on that thread, it appears that the engines can be downloaded manually and then paths to those engines can be set via env vars (some documentation is here about it as well).

But unfortunately, after downloading the 4x engines and 1x library, I’m still hitting a snag, but I think it has to do with me not using Docker correctly (that’s where our prisma scripts are actually run).

Here are the engines/libraries that I’ve downloaded specifically, if that helps:

• Query Library
• Query Engine
• Introspection Engine
• Migration Engine
• “Fmt Binary”

I’ll update once I get my Docker stuff figured out to say whether or not downloading/using these binaries as suggested worked or not.