tag:help.rubygems.org,2010-01-19:/discussions/problems/33671-suggestion-for-easy-solution-for-the-ipv6-related-timeout-problemRubyGems.org: Discussion 2018-12-15T01:11:38Ztag:help.rubygems.org,2010-01-19:Comment/461100872018-09-29T20:27:42Z2018-09-29T20:27:42ZSuggestion for easy solution for the IPv6-related timeout problem<div><p>Thanks for writing in. We believe the issue with IPv6 is not on our side, as our configuration appears to be correct; do you have specific information that points to an issue on our side?</p></div>kerrizortag:help.rubygems.org,2010-01-19:Comment/461100872018-10-01T11:48:31Z2018-10-01T11:48:32ZSuggestion for easy solution for the IPv6-related timeout problem<div><p>I provided some findings in<br>
<a href="http://help.rubygems.org/discussions/problems/31074-timeout-error">http://help.rubygems.org/discussions/problems/31074-timeout-error</a> ,<br>
including doing some test that Aditya asked me to do.</p>
<p>I can add that I could successfully ping, tcptraceroute and tcp-connect<br>
to ports 80 and 443 for the destination IP 151.101.0.70, but the same<br>
failed for 2a04:4e42::70.</p>
<p>I can successfully ping, tcptraceroute and tcp-connect to ports 80 and<br>
443 for the destination IP 2a00:1450:400f:80c::2004, address of<br>
<a href="http://www.google.com">www.google.com</a>. So my IPv6 setup seems to work.</p>
<blockquote>
<p>our configuration appears to be correct</p>
</blockquote>
<p>It can very well be so, but, for example, routing may be broken<br>
somewhere in the middle. Maybe it's a misconfiguration on some<br>
Internet-backbone router, I don't know. But the practical outcome is<br>
that gem is unusable. And I'd make it usable first, then investigate the<br>
problem, as it can take much time.</p>
<p>I am also reminding that it is not only me who has this issue. See, for<br>
example, these threads on Stack Overflow:</p>
<p><a href="https://stackoverflow.com/questions/49800432/gem-cannot-access-rubygems-org">https://stackoverflow.com/questions/49800432/gem-cannot-access-ruby...</a><br>
<a href="https://stackoverflow.com/questions/44763226/installing-gems-fails-with-timeout-error">https://stackoverflow.com/questions/44763226/installing-gems-fails-...</a><br>
<a href="https://stackoverflow.com/questions/49227187/error-while-executing-gem-gemremotefetcherunknownhosterror-timed-out">https://stackoverflow.com/questions/49227187/error-while-executing-...</a></p>
<p>On 29. sep. 2018 22:27, kerrizor wrote:</p></div>Alexei Khlebnikovtag:help.rubygems.org,2010-01-19:Comment/461100872018-10-07T16:35:03Z2018-10-07T16:35:03ZSuggestion for easy solution for the IPv6-related timeout problem<div><p>Thanks for the additional information, Alexei. I've raised this internally, and we'll continue to investigate.</p></div>kerrizortag:help.rubygems.org,2010-01-19:Comment/461100872018-12-12T08:45:23Z2018-12-12T08:45:24ZSuggestion for easy solution for the IPv6-related timeout problem<div><p>More than 3 months and still this issue exist ?<br>
gem is unusable. I had to disable ipv6 and then make it work.</p></div>kingsdebtag:help.rubygems.org,2010-01-19:Comment/461100872018-12-12T10:10:19Z2018-12-12T10:10:20ZSuggestion for easy solution for the IPv6-related timeout problem<div><p>Let me say some words in defense of the RubyGems' technical team. They may indeed have set up everything correctly ON THEIR SERVERS. The problem may very well be in the IPv6 routing setup between a gem user and api.rubygems.org.</p>
<p>According to <a href="https://tools.keycdn.com/ipv6-ping">https://tools.keycdn.com/ipv6-ping</a> , api.rubygems.org is accessible via IPv6 from several locations of the world.</p>
<p>Still, api.rubygems.org is inaccessible for many gem users, thus all these issue threads here and on StackOverflow exist.</p>
<p>Thus I am repeating my suggestion to move IPv6 addresses to another hostname, for example ipv6.rubygems.org, until the existing IPv6-related issues are resolved, wherever they have to be resolved - at the routing backbone, at hosting provider, or wherever else.</p>
<p>kerrizor> I've raised this internally, and we'll continue to investigate.</p>
<p>Can I ask how is it going with the investigation?</p></div>Alexei Khlebnikovtag:help.rubygems.org,2010-01-19:Comment/461100872018-12-15T01:11:37Z2018-12-15T01:11:37ZSuggestion for easy solution for the IPv6-related timeout problem<div><p>Alexei, I haven't heard any updates on this recently, but will ping Daniel R and see what the news is.</p></div>kerrizor