tag:help.rubygems.org,2010-01-19:/discussions/problems/30195-rate-limits-from-ip-addressRubyGems.org: Discussion 2018-02-10T22:50:01Ztag:help.rubygems.org,2010-01-19:Comment/446802742018-02-07T17:11:04Z2018-02-07T17:11:04ZRate limits from IP address<div><p>I'll check, but in the meantime, are you behind a firewall or proxy? Is this still happening? Sometimes we see this kind of thing happen intermittently.</p>
<p>Have you tried updating to the latest versions of openssl and bundler?</p></div>kerrizortag:help.rubygems.org,2010-01-19:Comment/446802742018-02-08T13:39:51Z2018-02-08T14:00:04ZRate limits from IP address<div><p>Before creating an issue, we eliminated all the problems on our side, so</p>
<p><em>firewall or proxy</em> we checked everything and excluded firewall (completely turned off - this<br>
did not fix the error)</p>
<p><em>Is this still happening?</em> yes<br>
simple curl example</p>
<p>curl -v <a href="https://rubygems.org/gems/dry-container-0.6.0.gem">https://rubygems.org/gems/dry-container-0.6.0.gem</a><br>
* Trying 151.101.130.2... * TCP_NODELAY set * Connected to rubygems.org (151.101.130.2) port 443 (#0) * Initializing NSS with certpath: sql:/etc/pki/nssdb * CAfile: /etc/pki/tls/certs/ca-bundle.crt CApath: none * NSS error -5961 (PR_CONNECT_RESET_ERROR) * TCP connection reset by peer * Curl_http_done: called premature == 1 * Closing connection 0 curl: (35) TCP connection reset by peer</p>
<p><em>Sometimes we see this kind of thing happen intermittently.</em> sad =(</p>
<p><em>Have you tried updating to the latest versions of openssl and bundler?</em> Yes, latest openssl, bundler and gem.</p></div>mark.vundertag:help.rubygems.org,2010-01-19:Comment/446802742018-02-08T13:50:11Z2018-02-08T14:00:04ZRate limits from IP address<div><p>extended curl example<br></p>
<pre>
<code>LC_ALL=C curl -v http://rubygems.org/gems/dry-container-0.6.0.gem > /dev/null
% 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 151.101.66.2...
* TCP_NODELAY set
* Connected to rubygems.org (151.101.66.2) port 80 (#0)
> GET /gems/dry-container-0.6.0.gem HTTP/1.1
> Host: rubygems.org
> User-Agent: curl/7.51.0
> Accept: <em>/</em>
>
< HTTP/1.1 200 OK
< x-amz-id-2: rTs8aM710Se4XgsnseggnAy+wkV48up7UkSCqBie7iFT1qAa0xgbxsAgUcU+ImgNidrSFEZi7Ow=
< x-amz-request-id: 64DBF3FBA88F485B
< x-amz-replication-status: COMPLETED
< Last-Modified: Fri, 09 Dec 2016 09:47:27 GMT
< ETag: "bb131ccd7c12153527ef1069d2b71384"
< Cache-Control: max-age=31536000
< x-amz-version-id: sCJtqLlkYj6eAHV4L7YBBIN96LGp5zZ3
< Via: 1.1 varnish
< Fastly-Debug-Digest: e698ef33a02a6aa4a83c783024753291d91065822c334f6abc97b7d918233e9e
< Content-Type: application/octet-stream
< X-Backend: F_S3 52.218.128.149:443, fastlyshield--shield_ssl_cache_sea1039_SEA 157.52.67.39:443
< Content-Length: 16384
< Accept-Ranges: bytes
< Date: Thu, 08 Feb 2018 13:39:15 GMT
< Via: 1.1 varnish
< Age: 9861322
< Connection: keep-alive
< X-Served-By: cache-sea1039-SEA, cache-lcy19250-LCY
< X-Cache: HIT, HIT
< X-Cache-Hits: 1, 2
< X-Timer: S1518097155.276190,VS0,VE0
< Vary: Fastly-SSL
< Server: RubyGems.org
<
{ [13577 bytes data]
* Recv failure: Connection reset by peer
* Curl_http_done: called premature == 1
83 16384 83 13577 0 0 327k 0 --:--:-- --:--:-- --:--:-- 331k
* Closing connection 0
curl: (56) Recv failure: Connection reset by peer</code>
</pre></div>mark.vundertag:help.rubygems.org,2010-01-19:Comment/446802742018-02-08T19:50:44Z2018-02-08T19:50:44ZRate limits from IP address<div><p>It looks on our end that you're not being rate limited, but more like you're having an SSL issue connecting to fastly</p></div>kerrizortag:help.rubygems.org,2010-01-19:Comment/446802742018-02-08T20:32:04Z2018-02-08T20:32:05ZRate limits from IP address<div><p>Same thing without ssl - when we try <code>http://rubygems.org</code><br>
See third comment (<a href="http://help.rubygems.org/discussions/problems/30195-rate-limits-from-ip-address#comment_44689872">http://help.rubygems.org/discussions/problems/30195-rate-limits-fro...</a>)</p></div>mark.vundertag:help.rubygems.org,2010-01-19:Comment/446802742018-02-08T21:17:16Z2018-02-08T21:17:17ZRate limits from IP address<div><p>we found relative issue with fastly<br>
<a href="https://community.fastly.com/t/problem-with-tcp-resets/944">https://community.fastly.com/t/problem-with-tcp-resets/944</a></p>
<p>Apparently we need to write directly to them.</p></div>mark.vundertag:help.rubygems.org,2010-01-19:Comment/446802742018-02-10T22:49:58Z2018-02-10T22:49:58ZRate limits from IP address<div><p>At this time Fastly believes the issue resolved. More information can be found here: <a href="https://status.fastly.com/incidents/k3zzxnkz4vcd">https://status.fastly.com/incidents/k3zzxnkz4vcd</a></p></div>kerrizor