46
votes

I'm attempting to follow the Hartl Rails Tutorial, and having trouble with the bundler gem.

When using the commands 'bundle install' or 'bundle update' I get the following output:

Fetching source index from https://rubygems.org/

Could not fetch specs from https://rubygems.org/

I've searched for this output, but did not find many related issues online.

Maybe I have another gem that is interrupting bundler? I have little experience with rails at this point.

    source 'https://rubygems.org'

gem 'rails', '3.2.12'

group :development do
  gem 'sqlite3', '1.3.5'
end


# Gems used only for assets and not required
# in production environments by default.
group :assets do
  gem 'sass-rails',   '3.2.5'
  gem 'coffee-rails', '3.2.2'

  gem 'uglifier', '1.2.3'
end

gem 'jquery-rails', '2.0.2'

The solution for me was two parts: I changed https to http, and that temporarily solved the issue. The second issue was that I think I had a bad install of ruby 2.0.0 even though I was using a fresh install of ruby 1.9.3. So I reinstalled ruby 2.0.0, and I could use bundle install with https.

14
That means your ruby installation doesn't play with OpenSSL correctly. It's supposed to give a different kind of error, though, weirdenthrops
I did brew install openssl earlier today, could they have affected it?Steven
I actually installed all of these from 'rvm requirements' "brew install autoconf automake apple-gcc42 libtool pkg-config openssl readline libyaml sqlite libxml2 libxslt libksba" I'm new to this type of environment, and not sure if any of those would affect this.Steven
Well, this depends on lots of things, depending on whether you use system ruby, rbenv, or rvm. And then there are flags to go along with installing ruby, certificates, and lots of other stuff. And then ruby 2.0 handles OpenSSL differently, so unless you want to deal with all that, just go with 'http://' in the Gemfile, although it's not secureenthrops
Ah, I did accidentally install ruby 2.0 today while installing RVM. I did a clean install of Mac OS 10.8.2, installed X-code, then installed homebrew, then RVM, then Ruby 2.0, then Ruby 1.9.3. Then gcc42, and the other packages like openssl through brew. But come to think of it, I think Ruby 2.0 did not properly install, so I will reinstall that...Steven

14 Answers

53
votes

Just in case none of the above satisfies the next intrepid explorer, I thought I'd drop here that after I spent 4 hours on this doing variants of the search that landed me here, I finally discovering that IPV6 was the culprit, after finding this specific thread on help.rubygems.org. Solution? this (Fedora, Linux):

sudo sysctl -w net.ipv6.conf.all.disable_ipv6=1
sudo sysctl -w net.ipv6.conf.default.disable_ipv6=1

set up a shell script to flip IPV6 on and off so I could run a command without it, and now everything runs peachy.

25
votes

I had the same issue. The only working solution I found was to force http instead of https in Gemfile:

source 'http://rubygems.org'
10
votes

you can try the following, if in windows:

set HTTP_PROXY= <your proxy address without http://>

set HTTPS_PROXY=%HTTP_PROXY%

For eg:

HTTP_PROXY=mycompany.myproxy.com:8080

HTTPS_PROXY=%HTTP_PROXY%

Worked for me

7
votes

It can be temporary network issue as well. Try restarting network services using command

service network restart

If its *nix machine.

3
votes

I had the same issue using ruby-2.0.0-p247 on OS X 10.8.5.

Make sure the first line in Gemfile is using https://

source 'https://rubygems.org'

I reinstalled that version of ruby.

rvm reinstall ruby-2.0.0

Ruby was upgraded ruby-2.0.0-p598 (version depends on latest patch).

bundle then worked without error although all the gems were reinstalled.

2
votes

The other reason causing such that issues is the fact if you are behind proxy server. I describe here solution, maybe it will be usefull for someone else. :)

In case that you did not know Login/pass for yours proxy, and meet this issues you could firstly check if you need to (re)install anything, by command:

C:\...> bundle check
Resolving dependencies...
The Gemfile's dependencies are satisfied

If you get other respons then above, you could find properly gems in properly versions here (rubygems.org), then install it (from the directory with downloaded gem) by command:

gem install <gem-name> --locally 
1
votes

I had this issue while working in Cloud 9. After trying several 'bundle install' and sending an email to c9 support(no reply) I was able to get it working by killing all the processes and doing a hard-restart of the IDE.

Do this by clicking directly on the little bar-graphs at the top of the right-hand side that show CPU, Memory, Disk. Then click on the process list, select them all, and force kill. Then exit out of the process list. Click on the bar-graphs again, and this time click 'Restart'.

After this I was able to run bundle with no problems.

1
votes

Either with http or https did not work.

After I disabled the IP v6, it worked

https://support.purevpn.com/how-to-disable-ipv6-linuxubuntu

0
votes

Adding variable for proxy worked fine.

Additionally if you are using Bitnami redmine like me you can add that into setenv.bat then when you start command line with Bitnami Redmine short cut it will be automatically added to your environment. You can find this under Bitnami installation folder.

0
votes

If you are using Cloud9, just restart (command R) and try again

0
votes

Sometimes it happens due to proxy you are using. I tried to resolve this by using a connection without proxy and all worked perfectly fine.
Then try:

bundle update

And then go for

bundle install
0
votes

CHange your source form https to http after run

sudo bundle update sudo bundle install

0
votes

For me, restarting the computer worked. I had already reinstalled ruby, updated bundler, removed 's' https:// but none of them worked!

0
votes

Mine was just a simple network issue, just restart pc / router