Network problems with gems fetching

[AlexWayfer]

I'm having a problem.

My current problem is:

$ gem i browser --verbose
ERROR:  Could not find a valid gem 'browser' (>= 0), here is why:
          Unable to download data from https://rubygems.org/ - timed out (https://api.rubygems.org/specs.4.8.gz)

$ gem update --system --verbose
ERROR:  While executing gem ... (Gem::RemoteFetcher::UnknownHostError)
    timed out (https://api.rubygems.org/specs.4.8.gz)

$ curl -O https://rubygems.org/gems/browser-2.5.3.gem
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 46592  100 46592    0     0  74428      0 --:--:-- --:--:-- --:--:-- 74428

This issue is related to:

• Network problems
• Installing a library
• Publishing a library
• The command line gem
• Other

Here are my current environment details:

$ gem env version
2.7.3

I will abide by the code of conduct.

[duckinator]

hi,

If you're still having this issue, can you provide the output of running this command?:

curl -vO https://api.rubygems.org/specs.4.8.gz

As well as this command?:

ruby -r rubygems/remote_fetcher -e 'puts(Gem::RemoteFetcher.new.fetch_path("https://api.rubygems.org/specs.4.8.gz") ? "success" : "failure")'

[WedgeSparda]

I'm having the same problem. Here's my output for those commands

curl -vO https://api.rubygems.org/specs.4.8.gz

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0*   Trying 2a04:4e42:600::514...
* TCP_NODELAY set
*   Trying 151.101.194.2...
* TCP_NODELAY set
* Connected to api.rubygems.org (151.101.194.2) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/cert.pem
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* TLSv1.2 (IN), TLS handshake, Server hello (2):
{ [102 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [5039 bytes data]
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
{ [333 bytes data]
* TLSv1.2 (IN), TLS handshake, Server finished (14):
{ [4 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
} [70 bytes data]
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS handshake, Finished (20):
} [16 bytes data]
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
{ [1 bytes data]
* TLSv1.2 (IN), TLS handshake, Finished (20):
{ [16 bytes data]
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use h2
* Server certificate:
*  subject: C=US; ST=California; L=San Francisco; O=Fastly, Inc.; CN=f2.shared.global.fastly.net
*  start date: Mar 26 22:40:12 2018 GMT
*  expire date: Oct  6 14:45:12 2018 GMT
*  subjectAltName: host "api.rubygems.org" matched cert's "*.rubygems.org"
*  issuer: C=BE; O=GlobalSign nv-sa; CN=GlobalSign CloudSSL CA - SHA256 - G3
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x7faf32806000)
> GET /specs.4.8.gz HTTP/2
> Host: api.rubygems.org
> User-Agent: curl/7.54.0
> Accept: */*
> 
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
< HTTP/2 200 
< x-amz-id-2: dmdpMm1Zh7GoRcd4M+yenfHgEb2+GBEt3YWPqx9lWcuTxWu8bl+jVYefWSmPRGezKBGjyeExqcA=
< x-amz-request-id: 3CEED0923A9CC5FE
< x-amz-replication-status: COMPLETED
< last-modified: Fri, 13 Apr 2018 08:25:30 GMT
< etag: "1aa92c124ad6e4d87316ec18772ca172"
< cache-control: max-age=31536000
< x-amz-meta-surrogate-key: full-index
< x-amz-version-id: 2Oe30418VBqqyOzIjSENhDzSF_CXwQpr
< via: 1.1 varnish
< content-type: application/octet-stream
< x-backend: F_S3 52.218.212.73:443, fastlyshield--shield_ssl_cache_sea1037_SEA 157.52.67.37:443
< accept-ranges: bytes
< date: Fri, 13 Apr 2018 08:28:47 GMT
< via: 1.1 varnish
< age: 194
< x-served-by: cache-sea1037-SEA, cache-cdg8726-CDG
< x-cache: HIT, HIT
< x-cache-hits: 1, 2
< x-timer: S1523608128.514265,VS0,VE0
< vary: Fastly-SSL
< server: RubyGems.org
< content-length: 3541980
< 
{ [2213 bytes data]
100 3458k  100 3458k    0     0  2569k      0  0:00:01  0:00:01 --:--:-- 2569k
* Connection #0 to host api.rubygems.org left intact

And

ruby -r rubygems/remote_fetcher -e 'puts(Gem::RemoteFetcher.new.fetch_path("https://api.rubygems.org/specs.4.8.gz") ? "success" : "failure")'

/Users/Wedge/.rvm/rubies/ruby-2.3.0/lib/ruby/site_ruby/2.3.0/rubygems/remote_fetcher.rb:306:in `rescue in fetch_path': timed out (https://api.rubygems.org/specs.4.8.gz) (Gem::RemoteFetcher::UnknownHostError)
	from /Users/Wedge/.rvm/rubies/ruby-2.3.0/lib/ruby/site_ruby/2.3.0/rubygems/remote_fetcher.rb:284:in `fetch_path'
	from -e:1:in `<main>'

[AlexWayfer]

If you're still having this issue

No, I no longer have this problem:

$ gem i browser --verbose
HEAD https://api.rubygems.org/api/v1/dependencies
200 OK
GET https://api.rubygems.org/api/v1/dependencies?gems=browser
200 OK
Getting SRV record failed: DNS result has no information for _rubygems._tcp.api.rubygems.org
GET https://api.rubygems.org/quick/Marshal.4.8/browser-2.5.3.gemspec.rz
200 OK
...

But since @WedgeSparda has — I'll not close this issue for now.

[WedgeSparda]

@AlexTalker Did you do something to fix your problem?

[AlexWayfer]

@AlexTalker Did you do something to fix your problem?

Sorry, I don't remember. I think no…

Probably, rebooted my Internet-connection (router, computer, etc.).

[WedgeSparda]

This is really weird. I can't install anything using RubyGems, always getting a timeout. But If I connect remotely to another computer in another network it works. How can I get more info about this weird problem?

[WedgeSparda]

Making more tests. Pings to rubygems.org and api.rubygems.org work perfectly.
Accesing to https://api.rubygems.org/specs.4.8.gz via web browser works too.
It seems that only happens from my terminal. I'm using macOS High Sierra 10.13.4.

Running gem i fastlane --verbose returns a timeout.

ERROR:  Could not find a valid gem 'fastlane' (>= 0), here is why:
          Unable to download data from https://rubygems.org/ - timed out (https://api.rubygems.org/specs.4.8.gz)

Anyone can help me? I'm unable of installing fastlane because of this and need to run a deploy.

Thanks.

[AlexWayfer]

Anyone can help me?

Did you try to reboot your computer and router?

[WedgeSparda]

@AlexWayfer Yes. No luck.

[AlexWayfer]

But If I connect remotely to another computer in another network it works.

Maybe you can use some proxy or VPN temporarily, while problems are here?

[WedgeSparda]

So I was able to run the installation using tethering with my phone. Any idea why a specific connection is giving error? Any port that I should open on my router?

[AlexWayfer]

@WedgeSparda You can try traceroute rubygems.org and traceroute api.rubygems.org, I guess, and paste outputs here.

[WedgeSparda]

@AlexWayfer Sorry, I'm not familiar with traceroute, which options should I run it with?

Version 1.4a12+Darwin
Usage: traceroute [-adDeFInrSvx] [-A as_server] [-f first_ttl] [-g gateway] [-i iface]
	[-M first_ttl] [-m max_ttl] [-p port] [-P proto] [-q nqueries] [-s src_addr]
	[-t tos] [-w waittime] [-z pausemsecs] host [packetlen]

[AlexWayfer]

@WedgeSparda Without any option, I think.