23

Trying to install Foundation after installing nodejs, ruby, and git plus bower.

I keep getting the following error and I dont know how to fix it:

Could not find a valid gem 'foundation' (>= 0), here is why: Unable to download data from https://rubygems.org/ - SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed (https://api.rubygems.org/latest_specs.4.8.gz)

Any ideas?

Knut Holm
  • 3,988
  • 4
  • 32
  • 54
NixondisNRVA
  • 341
  • 1
  • 2
  • 9
  • 1
    This [answer][1] works, saved me a day! [1]: https://stackoverflow.com/questions/27278966/error-sass-installation-for-windows/27892148#27892148 – user1981526 Mar 30 '15 at 08:11

5 Answers5

16

If you're using RVM (highly recommended) you can run

rvm osx-ssl-certs update all

Otherwise you can follow the directions at http://guides.rubygems.org/ssl-certificate-update/ and while the update_rubygems patch didn't do anything for me, manually installing the .pem file probably would have worked.

Without RVM the link suggests that you can try...

gem install bundler

or

gem update --system
Ryan Taylor
  • 12,559
  • 2
  • 39
  • 34
9

Please read the background and follow the official guide from rubygems.org on how to fix this.

TL;DR:

  1. Download rubygems-update-2.6.7.gem (link will be stale when new version is out)
  2. gem install --local $USER\Downloads\rubygems-update-2.6.7.gem
    (Try %userprofile% instead of $USER if using Windows)
  3. update_rubygems --no-ri --no-rdoc
  4. gem uninstall rubygems-update -x
Dennis K
  • 3
  • 3
gerrytan
  • 40,313
  • 9
  • 84
  • 99
  • Thanks very much! It worked for me, and isn't nearly as dangerous as the top-rated answer. – Fomentia Dec 21 '16 at 18:40
  • This worked perfectly, this should be the accepted answer, The top rated answer should not be done in a production environment – Williz Dec 07 '17 at 23:34
4

Taken from the reference given by Sébastien

Basicaly, you download the latest certificate and place it in $RUBYHOME/lib/ruby/2.1.0/rubygems/ssl_certs. (Note that you might have a different version of rubygems installed than 2.1.0, so adjust the path appropriately).

Rubygems should be using the certificate the next time you call the gem command.

binki
  • 7,754
  • 5
  • 64
  • 110
h3xStream
  • 6,293
  • 2
  • 47
  • 57
1

You need to update your gem installation to the version 2.6.7. Try this solution here:

https://github.com/rubygems/rubygems/issues/1770

http://guides.rubygems.org/ssl-certificate-update/#installing-using-update-packages

André Luiz Reis
  • 2,273
  • 21
  • 14
1

On linux, or in a docker container the following command will solve the problem:

curl https://raw.githubusercontent.com/rubygems/rubygems/master/lib/rubygems/ssl_certs/index.rubygems.org/GlobalSignRootCA.pem > $(ruby -ropenssl -e 'puts OpenSSL::X509::DEFAULT_CERT_FILE')

The above command will fetch the CA cert that rubygems expects when connecting to its website and install it in the location that ruby expects the cert to live.

Thanks to Gabe Evans helpful blog post, for detailing a smart way of solving the problem in one line of code.

I modified Gabe's solution to use the CA cert specified on the rubygems website. Further discussion of why this problem arose can be found there.

The benefit of this solution is that it uses https to fetch the updated cert for rubygems. Since it fetches this cert from github it can work even with a SHA1 cert. It is also handy because it uses ruby, by pulling in the openssl library to place the cert where it needs to go.