tag:help.rubygems.org,2010-01-19:/discussions/problems/31280-rubygems-connection-timeout-from-rackspace-serversRubyGems.org: Discussion 2018-07-22T17:38:12Ztag:help.rubygems.org,2010-01-19:Comment/451934802018-05-04T16:48:34Z2018-05-04T16:48:34ZRubyGems connection timeout from Rackspace servers<div><p>Hi Donald, thanks for writing in.. and apologies on the late reply, its been a hectic couple of weeks! A couple questions..</p>
<ul>
<li>Is this still an issue for you?</li>
<li>Have you tried traceroute'ing to see where the bottleneck is? If not, could you do so and let me know the results of that?</li>
</ul></div>kerrizortag:help.rubygems.org,2010-01-19:Comment/451934802018-05-04T19:18:13Z2018-05-04T19:18:15ZRubyGems connection timeout from Rackspace servers<div><p>Yes it is still an issue.</p>
<p>I can ping api.rubygems.org. However, I'm thinking it's an issue connecting via SSL/TLS. If I do a "gem search sanitize" for instance, it just hangs. This only happens from my servers at Rackspace, and I presume it's because they are behind some kind of NAT as other users have experienced with Amazon. The problem is that the NAT servers are not mine, they belong to Rackspace, so I can't just change them out.</p>
<p>My workaround has been to vendor the gems in my development environment and deploy so that the hosted cloud servers on Rackspace never have to connect to Rubygems.</p></div>Donald Webstertag:help.rubygems.org,2010-01-19:Comment/451934802018-07-22T17:38:11Z2018-07-22T17:38:11ZRubyGems connection timeout from Rackspace servers<div><p>Just following up, Donald - is this still an issue? I've seen other issues with NAT servers. Are you able to connect via http? What output do you get for <code>gem search --remote --verbose --debug sanitize</code>?</p></div>kerrizor