I'm a web developer and I usually use tools like git and npm. Until recently they worked fine but lately I get this error with git:
And I get this error with npm:
Researching online it seems that the issue has to do with SSL Trusted Certificates. I believe that CovenantEyes is the problem. Here is something that someone posted:
I saw this post: https://helpforum.covenanteyes.com/covenanteyes/topics/ssl-connections-are-broken-on-windows-10-cove... had the same issue but I don't understand how he fixed it.
I don't know what changed but this was never a problem until now. My guess is it has to do with the latest update. The release notes for Version 7.2.41 (which I have) say
$ git push origin master fatal: unable to access<br>'https://github.com/$$$/$$$.git/': SSL certificate problem<br>
unable to get local issuer certificate
And I get this error with npm:
npm install --save-dev webpack<br>npm WARN package.json 613@1.0.0 No description
npm WARN package.json 613@1.0.0 No README data
npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "--save-dev" "webpack"
npm ERR! node v4.4.4
npm ERR! npm v2.15.1
npm ERR! code UNABLE_TO_VERIFY_LEAF_SIGNATURE
npm ERR! unable to verify the first certificate
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! <https://github.com/npm/npm/issues>
npm ERR! Please include the following file with any support request:
npm ERR! npm-debug.log
Researching online it seems that the issue has to do with SSL Trusted Certificates. I believe that CovenantEyes is the problem. Here is something that someone posted:
This certificate that CovenantEyes uses to encrypt the traffic of course is not an official GitHub certificate and thus Git complains that it cannot verify the certificate.
I saw this post: https://helpforum.covenanteyes.com/covenanteyes/topics/ssl-connections-are-broken-on-windows-10-cove... had the same issue but I don't understand how he fixed it.
I don't know what changed but this was never a problem until now. My guess is it has to do with the latest update. The release notes for Version 7.2.41 (which I have) say
- Added external CA certificate support