rubygem timeout on bundle update

Question

I am getting a timeout error trying to update my gems. I would prefer not to have to change to unsecured paths.

I can download the gems individually from rubygems using my browser - but gem update and rvm gemset update both fail with the following error:

ERROR: While executing gem ... (Gem::RemoteFetcher::UnknownHostError) timed out (https://api.rubygems.org/latest_specs.4.8.gz)

When I run bundle update - I run into individual gems timing out (hence knowing I can download and install them individually), as an example:

Gem::RemoteFetcher::UnknownHostError: timed out (https://rubygems.org/gems/ffi-1.9.23.gem) An error occurred while installing ffi (1.9.23), and Bundler cannot continue. Make sure that gem install ffi -v '1.9.23' succeeds before bundling.

I have followed these posts:

not helpful - but I ended up having my whole environment reset. probably not the best solution. — Chris Guard, Apr 12 '18 at 15:57
This question looks like a duplicate of https://stackoverflow.com/questions/49800432/gem-cannot-access-rubygems-org — Alexei Khlebnikov, May 15 '18 at 11:57

score 4 · Answer 1 · answered Sep 18 '18 at 18:20

4

I got it solved by simple switching by wifi on/off on my Macbook Pro with OSx Mojave.

answered Sep 18 '18 at 18:20

Diego Charles

103
12

score 0 · Answer 2 · answered Nov 17 '18 at 23:11

the rubygems host server sometimes have problems dealing with ipv6.

Basically i have changed my preference from ipv6 to ipv4 in windows 10. That must help for other systems to.

For WINDOWS you'll do as follows:

check your prefixpolicies:

run

netsh insterface ipv6 show prefixpolicies

the output should be something like this:

Precedence label Prefix

----------  -----  --------------------------------

50      0  ::1/128
40      1  ::/0        
30      2  2002::/16
20      4  ::ffff:0:0/96

The higher the number of precedence, higher the priority.

So as you see, ipv6 ::/0 is right next to the localhost as the second priority.

Let's put ipv4 in a higher preference.

run:

netsh interface ipv6 set prefixpolicies ::ffff:0:0/96 46 4

After running this comand, try looking the prefixpolicies again.

You will find ipv4 in a higher precedence now, with 46 beeing higher than 40 from ipv6.

Now try reaching for the rubygem host running any "gem" command, you will probably be very pleased.

rubygem timeout on bundle update

2 Answers2