Certificate issues with git and npm

  • 2
  • Problem
  • Updated 3 years ago
  • (Edited)
  • 2
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:
$ 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
Photo of Rafi

Rafi

  • 15 Posts
  • 2 Reply Likes

Posted 3 years ago

  • 2
3 years ago
Photo of Robert B

Robert B, Official Rep

  • 541 Posts
  • 51 Reply Likes

Rafi,

Thanks for posting. I'm sorry to hear about the current difficulty, but glad to hear that there's been a good track record.

For the quickest solution, please call the Customer Service Team at 877-479-1119. Let them know that you're encountering certificate problems with the 7241 and you were advised to try 7243.

Thanks again,

Robert
3 years ago
Photo of Rafi

Rafi

  • 15 Posts
  • 2 Reply Likes
I followed their instructions and downloaded the 7243 installer. I ran it, it downloaded files and said it installed. I rebooted my computer and nothing changed. My CovenantEyes still shows the version as 7241, and my certificate issues are still there.
3 years ago
Photo of Robert B

Robert B, Official Rep

  • 541 Posts
  • 51 Reply Likes
Rafi,
Sorry to hear that. What browser are you using, and what OS?
Robert
3 years ago
Photo of Rafi

Rafi

  • 15 Posts
  • 2 Reply Likes
I'm not using a browser...my web browsing is fine. My problem is using git and npm, both of which are used in the command prompt.

I'm using Windows 10
3 years ago
Photo of Robert B

Robert B, Official Rep

  • 541 Posts
  • 51 Reply Likes
Thanks Rafi,
As far as 7241 still being there, let me counsel you to remove it via the Control Panel. And then install 7243. We need to see if 7243 makes a difference in this situation.
I've reached out to one of our developers. He hasn't personally experienced a cert issue while using CE with git and npm. But he is going to take a look at it and see what comes up. I'll follow up with him next week and then get back to you.
Robert
3 years ago
Photo of Rafi

Rafi

  • 15 Posts
  • 2 Reply Likes
When I try to uninstall covenant eyes, I get an error message: InstallScript Setup Launcher Unicode has stopped working. The uninstaller then closes without doing anything. So I'm stuck
3 years ago
Photo of Rafi

Rafi

  • 15 Posts
  • 2 Reply Likes
Okay I managed to uninstall it when I went into safe mode. I installed 7243 and the git and npm errors are gone! Thanks for your help.
(Edited)
3 years ago
Photo of Rafi

Rafi

  • 15 Posts
  • 2 Reply Likes
I recently got a new laptop and installed 7243 as before, and everything was working fine. I just updated the computer to the new version of Windows 10, the Fall Creators Update (1709). Since then, I can't browse the Internet properly. Everything is really slow, Gmail won't load because of SSL issues and my old git problems are back. I'm guessing the update messed over the CE certificates. Is the solution to just reinstall CE? Or do I need a new version that addresses whatever was changed.
(Edited)
2017-10-30T00:32:54+00:00
Photo of BarneyFifeFan

BarneyFifeFan

  • 18 Posts
  • 1 Reply Like
Yeah, this happens to me every time I upgrade a major version of Windows 10. The only solution is to reinstall. I've basically taken to pre-emptively uninstalling before the version upgrade, and then re-installing once it finishes; it really simplifies things.
3 years ago
Photo of Robert B

Robert B, Official Rep

  • 541 Posts
  • 51 Reply Likes
Rafi,

I would certainly uninstall 7243. However, don't worry about reinstalling it. If you sign in at covenanteyes.com and go to the Downloads section, then select 7247. It's second on the list of CE downloads for Windows and will be labeled as 'CE for Windows (BETA)'.

Hopefully that realigns things for you. If it doesn't, then please post again or call our Customer Service team at 877-479-1119.

Robert
(Edited)
2017-11-01T13:05:21+00:00
Photo of Rafi

Rafi

  • 15 Posts
  • 2 Reply Likes
That would be great, but I'm using CE through WebChaver so I don't have access to the covenanteyes.com download page.
2017-11-01T14:30:45+00:00
Photo of Robert B

Robert B, Official Rep

  • 541 Posts
  • 51 Reply Likes
Rafi,

Check the WebChaver website once more, 7247 was scheduled to become the default download. I don't know if it's happened yet. If WC is still using 7241, then email me at robert.b@covenanteyes.com and we'll go from there.

Robert
3 years ago
Photo of Rafi

Rafi

  • 15 Posts
  • 2 Reply Likes
Okay 7247 fixed it. There should be a more efficient way than to uninstall it (alerting my compatibility partners and I have to do it in safe mode) and installing a new version.
3 years ago
Photo of Robert B

Robert B, Official Rep

  • 541 Posts
  • 51 Reply Likes
Rafi,

Thanks for the update, I'm glad 7247 worked.

You shouldn't have to use safe mode to uninstall CE. If you'd like us to look into that, call us when you have a few moment. We could remotely connect, enable debug logs and try to uninstall in normal mode. The information collected would then go to our developers for their review.

Thanks again for the update.

Robert
  • 2

Powered by Get Satisfaction