7

Whilst my development environment works absolutely fine my build server is suffering with errors such as the following... although at some point it was all working fine too!

warn Error on lookup for github:aurelia/event-aggregator
     Error: fatal: unable to access 'aurelia/event-aggregator.git/': error setting certificate verify locations:
   CAfile: C:/Program Files/Git/mingw64/libexec/ssl/certs/ca-bundle.crt
   CApath: none

err  Error looking up github:aurelia/event-aggregator.

I noticed that the CAfile path was different to the one on disk (C:\Program Files\Git\mingw64\ssl\certs\ca-bundle.crt) so copied the ssl folder from mingw64\ into mingw64\libexec and everything started working again.

Is this an appropriate fix?

Here are some of the versions of products I'm running:

jspm - 0.16.13
npm - 3.3.10
node - 4.2.1
Phil
  • 2,232
  • 1
  • 26
  • 35
  • I had this same issue this morning and did the same thing you did. However, I am not feeling the greatest about this as a fix. Got me going for the time being though. – Scott Smith Nov 02 '15 at 14:21
  • This seems like a legitimate issue, have you logged this issue on their github page? I had the same error (the fix also worked for me). – tympaniplayer Nov 02 '15 at 15:55
  • Interesting Given you've had similar issues I'll raise it. I've also had dreadful trouble with the aurelia-bundler and dependencies. Makes me wonder whether npm/jspm is worth the trouble or I just handle dependencies manually especially given npm@3 still doesn't solve the Windows path char limit – Phil Nov 02 '15 at 21:14
  • 2
    I had this issue too with JSPM 0.16.14. After `npm un jspm -g && npm i jspm -g` I received patched [JSPM 0.16.15](https://github.com/jspm/jspm-cli/releases/tag/0.16.15) with new SystemJS. Now the certificate issue disappeared. – Marcel Hoyer Dec 05 '15 at 13:17
  • Thanks @Marcel, 0.16.14 was a problem for me too and 0.16.15 fixed it. – sisdog Jan 01 '16 at 01:45
  • Some of these Windows-specific errors can be tough to crack. Consider using [git bash](https://git-for-windows.github.io/) if you can. – PW Kad Mar 09 '16 at 04:54
  • 1
    I'm pretty sure that installing new GitExtensions along with Git caused this. – Maxim Balaganskiy Jul 21 '17 at 07:04
  • 1
    Yeah, it happened to me when I installed the new version of GitExtensions. – Tom Bogle Aug 09 '17 at 04:00

1 Answers1

3

I executed the following command in a command window (run as admin), and it got me up and running. Still not sure this is the right answer, but it felt better than copying the folder:

git config --system http.sslcainfo "C:\Program Files\Git\usr\ssl\certs\ca-bundle.crt"
Tom Bogle
  • 464
  • 4
  • 18