tag:help.rubygems.org,2010-01-19:/discussions/problems/21664-cant-install-gems-connection-timed-outRubyGems.org: Discussion 2016-05-12T17:45:34Ztag:help.rubygems.org,2010-01-19:Comment/391192832016-02-08T19:25:03Z2016-02-08T19:25:03ZCan't install gems: Connection timed out<div><p>Do you have a proxy or firewall installed?</p></div>Nick Quarantotag:help.rubygems.org,2010-01-19:Comment/391192832016-02-08T19:58:38Z2016-02-08T19:58:41ZCan't install gems: Connection timed out<div><p>No I don't think so, however I have just installed kubuntu 15.10
on my laptop and I never got rubygems to work on it, so I'm
wondering if this problem is caused by a software installed with
kubuntu. I'm using rbenv and ruby 2.1.5p273.<br>
I have changed my router but I still have the same issue. And I
also changed the dns to 8.8.8.8 but it's still the same.</p></div>btazitag:help.rubygems.org,2010-01-19:Comment/391192832016-02-09T00:27:51Z2016-02-09T01:54:41ZCan't install gems: Connection timed out<div><p>The same thing is happening here.</p>
<pre>
<code>⚡ curl -v https://rubygems.org/gems/rb-inotify-0.9.6.gem
* Trying 54.186.104.15...
* Connected to rubygems.org (54.186.104.15) port 443 (#0)
* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate: *.rubygems.org
* Server certificate: COMODO RSA Domain Validation Secure Server CA
* Server certificate: COMODO RSA Certification Authority
* Server certificate: AddTrust External CA Root
> GET /gems/rb-inotify-0.9.6.gem HTTP/1.1
> Host: rubygems.org
> User-Agent: curl/7.43.0
> Accept: */*
>
< HTTP/1.1 302 Moved Temporarily
< Server: nginx
< Date: Tue, 09 Feb 2016 00:26:58 GMT
< Content-Type: text/html
< Content-Length: 154
< Connection: keep-alive
< Location: https://rubygems.global.ssl.fastly.net/gems/rb-inotify-0.9.6.gem
<
<html>
<head><title>302 Found</title></head>
<body bgcolor="white">
<center><h1>302 Found</h1></center>
<hr><center>nginx</center>
</body>
</html>
* Connection #0 to host rubygems.org left intact</code>
</pre>
<pre>
<code>⚡ curl -v https://rubygems.global.ssl.fastly.net/gems/rb-inotify-0.9.6.gem
* Trying 23.235.40.249...
* Connected to rubygems.global.ssl.fastly.net (23.235.40.249) port 443 (#0)
* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate: a.ssl.fastly.net
* Server certificate: DigiCert SHA2 High Assurance Server CA
* Server certificate: DigiCert High Assurance EV Root CA
> GET /gems/rb-inotify-0.9.6.gem HTTP/1.1
> Host: rubygems.global.ssl.fastly.net
> User-Agent: curl/7.43.0
> Accept: */*
>
< HTTP/1.1 403 Forbidden
< x-amz-request-id: AA92670F96AC7D06
< x-amz-id-2: 8NK71kJreXq1Vj8ARmpBB5csxZoQwVpUeIRvQRwxYYtmVgbpursyinIlp+p9uYLGcp+SE4OYyu0=
< Content-Type: application/xml
< Server: AmazonS3
< Via: 1.1 varnish
< Fastly-Debug-Digest: c543323ad00febdf427b8ae0a8ffe4a4312e04b721d2523eb87dcfd41304012e
< Transfer-Encoding: chunked
< Accept-Ranges: bytes
< Date: Tue, 09 Feb 2016 00:27:11 GMT
< Via: 1.1 varnish
< Connection: keep-alive
< X-Served-By: cache-sea1926-SEA, cache-ord1721-ORD
< X-Cache: MISS, MISS
< X-Cache-Hits: 0, 0
<
<?xml version="1.0" encoding="UTF-8"?>
* Connection #0 to host rubygems.global.ssl.fastly.net left intact
<Error><Code>AccessDenied</Code><Message>Access Denied</Message><RequestId>AA92670F96AC7D06</RequestId><HostId>8NK71kJreXq1Vj8ARmpBB5csxZoQwVpUeIRvQRwxYYtmVgbpursyinIlp+p9uYLGcp+SE4OYyu0=</HostId></Error></code>
</pre></div>williamtag:help.rubygems.org,2010-01-19:Comment/391192832016-02-09T00:41:31Z2016-02-09T00:42:02ZCan't install gems: Connection timed out<div><p>It looks like the mirror is broken.</p></div>williamtag:help.rubygems.org,2010-01-19:Comment/391192832016-02-09T00:45:26Z2016-02-09T00:45:27ZCan't install gems: Connection timed out<div><p>It's entirely possible that the mirror is just behind on
syncing. I noted that a new version of rb-inotify was <em>just</em>
released: <a href="https://rubygems.org/gems/rb-inotify">https://rubygems.org/gems/rb-inotify</a></p></div>williamtag:help.rubygems.org,2010-01-19:Comment/391192832016-05-12T17:45:33Z2016-05-12T17:45:33ZCan't install gems: Connection timed out<div><p>Going to close this one out...let us know if there's any other
flakiness!</p></div>Nick Quaranto