Open mirker21 opened 11 months ago
I got same issue, any update @FiloSottile ?
I just found a solution, in the terminal when you are starting up the server I just had to include the directory of the rootCA.pem file:
HTTPS=true NODE_EXTRA_CA_CERTS="$(mkcert -CAROOT)/rootCA.pem" npm run dev
I just found a solution, in the terminal when you are starting up the server I just had to include the directory of the rootCA.pem file:
HTTPS=true NODE_EXTRA_CA_CERTS="$(mkcert -CAROOT)/rootCA.pem" npm run dev
export NODE_EXTRA_CA_CERTS="$(mkcert -CAROOT)/rootCA.pem"
in .zprofile
did the trick. Thanks! (I didn't seem to need HTTPS=true
🤷)
After using NODE_EXTRA_CA_CERTS
, I'm getting another error:
Error: self-signed certificate in certificate chain
Environment
mkcert -version
): v1.4.4What you did
I followed the instructions, first doing
mkcert -install
Entered
mkcert -cert-file ~/cert.pem -key-file ~/key.pem localhost
Here are my options for both frontend and backend Node.js https servers:
I tried adding the ca property, I found a post mentioning it and then I found an example on how to use ca on node's website.
Finally added
export NODE_EXTRA_CA_CERTS="$(mkcert -CAROOT)/rootCA.pem"
to both my frontend and backend .env files, according to the README.md and this IssueAlso tried changing
export NODE_EXTRA_CA_CERTS="$(mkcert -CAROOT)/rootCA.pem"
to/Users/blahblahblah/Library/blahblahblah/mkcert/rootCA.pem
What went wrong
The frontend terminal displayed this error:
The backend terminal displayed no errors.