This help site has been deprecated. Please send your requests to support@rubygems.org
gem update --system times out
I try to perform gem update --system
ERROR: While executing gem ... (Gem::RemoteFetcher::UnknownHostError)
time out (https://rubygems.org/specs.4.8.gz
I have disabled Ip6 still happens and added google DNS's 8.8.8.8 and 8.8.4.4
I am attempting to install on Ubuntu 18.04
Thanks for the help
Keith
Discussions are closed to public comments.
If you need help with RubyGems.org please
start a new discussion.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
1 Posted by Prakhyat on 14 Nov, 2019 03:38 PM
Hello,
I'm also having the same error since yesterday (nov 13th).
Gem::RemoteFetcher::UnknownHostError: timed out (https://rubygems.org/gems/aws-sdk-connect-1.20.0.gem)
Are there any issues in EU region?
Thanks
Prakhyat
Support Staff 2 Posted by sonalkr132 on 28 Nov, 2019 03:34 PM
Hi,
Sorry about delay in our response. We aren't aware of any issue with EU region or otherwise. Is this still not working? if so, can you please paste the output of following two commands:
3 Posted by Humberto on 07 Jul, 2020 01:34 AM
curl -vvv https://rubygems.org/specs.4.8.gz
pi@raspberrypi:~ $ curl -vvv https://rubygems.org/specs.4.8.gz
* Expire in 0 ms for 6 (transfer 0xa357c0)
* Expire in 1 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 1 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 1 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 1 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 2 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 2 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 2 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 2 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 2 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 2 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 2 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 2 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 2 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 2 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 2 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 2 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 2 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 2 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 0 ms for 1 (transfer 0xa357c0)
* Expire in 2 ms for 1 (transfer 0xa357c0)
* Expire in 1 ms for 1 (transfer 0xa357c0)
* Expire in 1 ms for 1 (transfer 0xa357c0)
* Expire in 2 ms for 1 (transfer 0xa357c0)
* Expire in 1 ms for 1 (transfer 0xa357c0)
* Expire in 1 ms for 1 (transfer 0xa357c0)
* Expire in 2 ms for 1 (transfer 0xa357c0)
* Expire in 1 ms for 1 (transfer 0xa357c0)
* Expire in 1 ms for 1 (transfer 0xa357c0)
* Expire in 4 ms for 1 (transfer 0xa357c0)
* Expire in 2 ms for 1 (transfer 0xa357c0)
* Expire in 2 ms for 1 (transfer 0xa357c0)
* Expire in 4 ms for 1 (transfer 0xa357c0)
* Expire in 2 ms for 1 (transfer 0xa357c0)
* Expire in 2 ms for 1 (transfer 0xa357c0)
* Expire in 4 ms for 1 (transfer 0xa357c0)
* Expire in 3 ms for 1 (transfer 0xa357c0)
* Expire in 3 ms for 1 (transfer 0xa357c0)
* Expire in 4 ms for 1 (transfer 0xa357c0)
* Expire in 4 ms for 1 (transfer 0xa357c0)
* Expire in 4 ms for 1 (transfer 0xa357c0)
* Expire in 4 ms for 1 (transfer 0xa357c0)
* Expire in 4 ms for 1 (transfer 0xa357c0)
* Expire in 4 ms for 1 (transfer 0xa357c0)
* Expire in 4 ms for 1 (transfer 0xa357c0)
* Expire in 5 ms for 1 (transfer 0xa357c0)
* Expire in 5 ms for 1 (transfer 0xa357c0)
* Expire in 4 ms for 1 (transfer 0xa357c0)
* Expire in 6 ms for 1 (transfer 0xa357c0)
* Expire in 6 ms for 1 (transfer 0xa357c0)
* Expire in 8 ms for 1 (transfer 0xa357c0)
* Expire in 8 ms for 1 (transfer 0xa357c0)
* Expire in 8 ms for 1 (transfer 0xa357c0)
* Expire in 8 ms for 1 (transfer 0xa357c0)
* Expire in 8 ms for 1 (transfer 0xa357c0)
* Expire in 8 ms for 1 (transfer 0xa357c0)
* Expire in 8 ms for 1 (transfer 0xa357c0)
* Expire in 11 ms for 1 (transfer 0xa357c0)
* Expire in 11 ms for 1 (transfer 0xa357c0)
* Expire in 8 ms for 1 (transfer 0xa357c0)
* Expire in 11 ms for 1 (transfer 0xa357c0)
* Expire in 11 ms for 1 (transfer 0xa357c0)
* Expire in 16 ms for 1 (transfer 0xa357c0)
* Expire in 15 ms for 1 (transfer 0xa357c0)
* Expire in 15 ms for 1 (transfer 0xa357c0)
* Expire in 16 ms for 1 (transfer 0xa357c0)
* Expire in 15 ms for 1 (transfer 0xa357c0)
* Expire in 15 ms for 1 (transfer 0xa357c0)
* Expire in 50 ms for 1 (transfer 0xa357c0)
* Trying 2a04:4e42::70...
* TCP_NODELAY set
* Expire in 149969 ms for 3 (transfer 0xa357c0)
* Expire in 200 ms for 4 (transfer 0xa357c0)
* Trying 151.101.192.70...
* TCP_NODELAY set
* Expire in 149969 ms for 3 (transfer 0xa357c0)
* Connected to rubygems.org (151.101.192.70) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: none
CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use http/1.1
* Server certificate:
* subject: C=US; ST=California; L=San Francisco; O=Fastly, Inc.; CN=l.ssl.fastly.net
* start date: May 27 22:55:10 2020 GMT
* expire date: Aug 18 14:31:03 2022 GMT
* subjectAltName: host "rubygems.org" matched cert's "rubygems.org"
* issuer: C=BE; O=GlobalSign nv-sa; CN=GlobalSign Organization Validation CA - SHA256 - G2
* SSL certificate verify ok.
> GET /specs.4.8.gz HTTP/1.1
> Host: rubygems.org
> User-Agent: curl/7.64.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Connection: keep-alive
< Content-Length: 4184957
< x-amz-id-2: IaUHYlXzWq9aEsLTh5hyQEu3WIsY5AuoqwlhlQfEQB3nXil+b+1qoePZ0caIn9+W9rj3FUoCiSA=
< x-amz-request-id: 1E439B2BE8AFF78A
< x-amz-replication-status: PENDING
< Last-Modified: Tue, 07 Jul 2020 01:26:15 GMT
< ETag: "6f67a1cbda1d2f990fb6dda69326b110"
< Cache-Control: max-age=31536000
< x-amz-meta-surrogate-key: full-index
< x-amz-version-id: Jg.3rNPoE5ylt8E_DF1uMgAjDiodp1mm
< Via: 1.1 varnish
< Content-Type: application/octet-stream
< X-Backend: F_S3 52.218.252.137:443, fastlyshield--shield_ssl_cache_sea4467_SEA 199.27.78.67:443
< Accept-Ranges: bytes
< Date: Tue, 07 Jul 2020 01:29:53 GMT
< Via: 1.1 varnish
< Age: 216
< X-Served-By: cache-sea4467-SEA, cache-lax8640-LAX
< X-Cache: HIT, HIT
< X-Cache-Hits: 1, 1
< X-Timer: S1594085394.741036,VS0,VE8
< Vary: Fastly-SSL
< Server: RubyGems.org
<
Warning: Binary output can mess up your terminal. Use "--output -" to tell
Warning: curl to output it to your terminal anyway, or consider "--output
Warning: <FILE>" to save to a file.
* Failed writing body (0 != 1371)
* Closing connection 0
wget https://rubygems.org/specs.4.8.gz
--2020-07-06 18:31:05-- https://rubygems.org/specs.4.8.gz
Resolving rubygems.org (rubygems.org)... 2a04:4e42::70, 151.101.192.70, 151.101.64.70, ...
Connecting to rubygems.org (rubygems.org)|2a04:4e42::70|:443... failed: Connection timed out.
Connecting to rubygems.org (rubygems.org)|151.101.192.70|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 4184988 (4.0M) [application/octet-stream]
Saving to: ‘specs.4.8.gz.1’
specs.4.8.gz.1 100%[===================>] 3.99M 4.17MB/s in 1.0s
2020-07-06 18:33:19 (4.17 MB/s) - ‘specs.4.8.gz.1’ saved [4184988/4184988]
pi@raspberrypi:~ $
Support Staff 4 Posted by sonalkr132 on 07 Jul, 2020 01:10 PM
Unfortunately, you have hit our IPv6 issues. You can use this https://stackoverflow.com/questions/49800432/gem-cannot-access-ruby... to disable IPv6 for rubygems.org. Can you please also run
traceroute 2a04:4e42::70
and send us the output?Support Staff 5 Posted by sonalkr132 on 07 Jul, 2020 02:32 PM
Additionally, if would be very helpful if any of you could send debug output you see on the following site when visiting it from the host with IPv6 issue:
https://v6.fastly-debug.com/
6 Posted by José Humberto A... on 07 Jul, 2020 03:31 PM
Hi, site screen shots.
El mar., 7 jul. 2020 a las 7:32, sonalkr132 (<
[email blocked]>) escribió:
Support Staff 7 Posted by sonalkr132 on 07 Jul, 2020 03:46 PM
Thank you for screenshots Jose. However, I am looking for the base64 blob you would see on this: https://v6.fastly-debug.com/ page under "Please submit text block below with your ticket to Fastly". The blob may not be visible right away, so give it a few seconds to generate.
Also, make sure you are visiting https://v6.fastly-debug.com/ from the host where you have IPv6 issue. In your screenshot I see IPv4 address, it is suppose to be IPv6 address.
Again, thank you so much for your effort and time.
8 Posted by José Humberto A... on 07 Jul, 2020 03:53 PM
Text:
ewogICJnZW9pcCI6IHsKICAgICJjaSI6ICJoZXJtb3NpbGxvIiwKICAgICJzdCI6ICJTT04iLAogICAgImN0IjogIm1leGljbyIsCiAgICAiY28iOiAiTkEiLAogICAgImNfaXAiOiAiMTg3LjE1OC45NS4xNjciLAogICAgImNfYXNuIjogIjgxNTEiLAogICAgImNfYXNuX25hbWUiOiAidW5pbmV0IHMuYS4gZGUgYy52LiIsCiAgICAicl9pcCI6ICIxODkuMjMzLjEwLjIiLAogICAgInJfYXNuIjogIjgxNTEiLAogICAgInJfYXNuX25hbWUiOiAidW5pbmV0IHMuYS4gZGUgYy52LiIsCiAgICAicl9jaSI6ICJoZXJtb3NpbGxvIiwKICAgICJyX3N0IjogIlNPTiIsCiAgICAicl9jdCI6ICJtZXhpY28iLAogICAgInJfY28iOiAiTkEiCiAgfSwKICAicG9wTGF0ZW5jeSI6IHsKICAgICJkZnciOiA1NywKICAgICJkZW4iOiA2NSwKICAgICJvcmQiOiAxMDgsCiAgICAibWR3IjogOTQsCiAgICAiaWFoIjogNzUsCiAgICAiZGFsIjogNjgsCiAgICAiZGNhIjogOTEsCiAgICAibGdhIjogOTgsCiAgICAiYndpIjogOTMsCiAgICAiYXRsIjogODgsCiAgICAicGRrIjogOTAsCiAgICAiamF4IjogOTcsCiAgICAiYm9zIjogMTA1LAogICAgIndkYyI6IDExNywKICAgICJ5eXoiOiA5NywKICAgICJ5dnIiOiA2MywKICAgICJ5dWwiOiAxMDMsCiAgICAiamZrIjogOTYsCiAgICAiZXdyIjogOTEsCiAgICAibWlhIjogOTgsCiAgICAibGF4IjogMzIsCiAgICAic2pjIjogMzgsCiAgICAic2VhIjogNTcsCiAgICAibXNwIjogODcsCiAgICAiY21oIjogMTA1LAogICAgInBhbyI6IDQyLAogICAgImJ1ciI6IDMzLAogICAgImNoaSI6IDkzLAogICAgInB3ayI6IDk0LAogICAgIm1jaSI6IDcyLAogICAgInN0bCI6IDc5LAogICAgImFueSI6IDMyCiAgfSwKICAicG9wQXNzaWdubWVudHMiOiB7CiAgICAiYWMiOiAibGF4IiwKICAgICJhcyI6ICJsYXgiCiAgfSwKICAicmVxdWVzdCI6IHsKICAgICJyZXNvbHZlcl9pcCI6ICIxODkuMjMzLjEwLjEiLAogICAgInJlc29sdmVyX2FzX25hbWUiOiAiVW5pbmV0IFMuQS4gZGUgQy5WLiwgTVgiLAogICAgInJlc29sdmVyX2FzX251bWJlciI6ICI4MTUxIiwKICAgICJyZXNvbHZlcl9jb3VudHJ5X2NvZGUiOiAiTVgiLAogICAgImNsaWVudF9pcCI6ICIxODcuMTU4Ljk1LjE2NyIsCiAgICAiY2xpZW50X2FzX25hbWUiOiAiVW5pbmV0IFMuQS4gZGUgQy5WLiwgTVgiLAogICAgImNsaWVudF9hc19udW1iZXIiOiAiODE1MSIsCiAgICAidGltZSI6ICIyMDIwLTA3LTA3VDE1OjQ3OjUzLjAwMFoiLAogICAgImhvc3QiOiAidjYuZmFzdGx5LWRlYnVnLmNvbSIsCiAgICAiYWNjZXB0IjogInRleHQvaHRtbCxhcHBsaWNhdGlvbi94aHRtbCt4bWwsYXBwbGljYXRpb24veG1sO3E9MC45LGltYWdlL3dlYnAsKi8qO3E9MC44IiwKICAgICJ1c2VyYWdlbnQiOiAiTW96aWxsYS81LjAgKE1hY2ludG9zaDsgSW50ZWwgTWFjIE9TIFggMTAuMTE7IHJ2Ojc4LjApIEdlY2tvLzIwMTAwMTAxIEZpcmVmb3gvNzguMCIsCiAgICAiYWNjZXB0bGFuZ3VhZ2UiOiAiZXMtTVgsZXM7cT0wLjgsZW4tVVM7cT0wLjUsZW47cT0wLjMiLAogICAgImFjY2VwdGVuY29kaW5nIjogImd6aXAiLAogICAgImZhc3RseXNlcnZlcmlwIjogIjE1MS4xMDEuMjQuNjQiLAogICAgInhmZiI6ICIxODcuMTU4Ljk1LjE2NyIsCiAgICAiZGF0YWNlbnRlciI6ICJMQVgiLAogICAgImJhbmR3aWR0aF9tYnBzIjogIjE2LjQxIiwKICAgICJjd25kIjogMTE3LAogICAgIm5leHRob3AiOiAiMTcyLjE4LjEwMC4xIiwKICAgICJydHQiOiAzNS44NjEsCiAgICAiZGVsdGFfcmV0cmFucyI6IDAsCiAgICAidG90YWxfcmV0cmFucyI6IDE3CiAgfQp9
El mar., 7 jul. 2020 a las 8:46, sonalkr132 (<
[email blocked]>) escribió:
Support Staff 9 Posted by sonalkr132 on 07 Jul, 2020 04:09 PM
Thank you. can you please confirm you are running the diagnosis from the same host where you have IPv6 connectivity issue to rubygems.org[1] and you have not applied the fix mentioned in SO link I shared?
Client IP is suppose to be an IPv6 address or else this timeout issue won't exist and wget won't attempt to connect over IPv6 address first. In the blob (and screenshot) I am seeing your client IP is an IPv4 address.
[1] wget should still be showing conn timeout for IPv6 address of rubygems.org
10 Posted by José Humberto A... on 07 Jul, 2020 04:21 PM
Never loads
El mar., 7 jul. 2020 a las 9:09, sonalkr132 (<
[email blocked]>) escribió:
11 Posted by José Humberto A... on 07 Jul, 2020 04:22 PM
OS
El mar., 7 jul. 2020 a las 9:21, José Humberto Abril García (<
[email blocked]>) escribió:
Support Staff 12 Posted by sonalkr132 on 07 Jul, 2020 04:26 PM
It's okay. I am pretty sure
gem update --system
is working for you without issue andwget https://rubygems.org/specs.4.8.gz
is not attempting IPv6 address. Please confirm this.13 Posted by José Humberto A... on 07 Jul, 2020 04:33 PM
In my network and gem update --system works on MacOS, Windows, Ubuntu but
on Rapeberry.
El mar., 7 jul. 2020 a las 9:26, sonalkr132 (<
[email blocked]>) escribió:
Support Staff 14 Posted by sonalkr132 on 07 Jul, 2020 04:40 PM
Okay, now it makes sense. Can you please run following from your Raspberry and send the output:
15 Posted by José Humberto A... on 07 Jul, 2020 04:45 PM
El mar., 7 jul. 2020 a las 9:40, sonalkr132 (<
[email blocked]>) escribió:
Support Staff 16 Posted by sonalkr132 on 07 Jul, 2020 08:03 PM
Great! I was trying to clarify if your raspberry has working IPv6 connectivity. Fact that you can access
www.ttora.com
over IPv6 proves that you do.We need more info about IPv6 connection to rubygems.org on your raspberry pi.
Do you think you can install tshark (or tcpdump for that matter) on your raspberry and send us packet capture file of request to rubygems.org:
tshark -i any -f "host rubygems.org" -w rubygems.pcap
. you may need to prepend the command with sudo, in which case make the rubygems.pcap file beforehand.touch rubygems.pcap && sudo chown root:root rubygems.pcap
.run
wget https://rubygems.org
from a different terminator on raspberry pie itself. You can verify if you were able to successfully capture packets by reading the same pcap filetshark -r rubygems.pcap
.It would also be very helpful if you can send us the output of traceroute:
traceroute 2a04:4e42::70
.Thank you for taking the time to help us debug this. Feel free to reach out if any of the instruction is unclear.
17 Posted by Lohith on 20 Oct, 2020 07:13 PM
This comment was split into a new private discussion: gem update --system times out
Hi Team,
I have a same issue and not able to rectify the error. I wanted to install hologram and using below mentioned command
> gem install hologram
Unable to download data from https://rubygems.org/ - timed out (https://rubygems.org/specs.4.8.gz)
Kindly do the needful. I have also tried installing gem install rails/ gem update --system. PFB, attached error screen
sonalkr132 closed this discussion on 30 Nov, 2020 08:21 AM.