Rate limits from IP address

mark.vunder's Avatar

mark.vunder

07 Feb, 2018 10:09 AM

Hello.
We try to use rubygems.org from IP 52.212.31.113 and have Connection reset by peer error message
Are we in some black lists or we exceed rate limits by IP?
Can you check this?

  1. Support Staff 1 Posted by kerrizor on 07 Feb, 2018 05:11 PM

    kerrizor's Avatar

    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.

    Have you tried updating to the latest versions of openssl and bundler?

  2. 2 Posted by mark.vunder on 08 Feb, 2018 01:39 PM

    mark.vunder's Avatar

    Before creating an issue, we eliminated all the problems on our side, so

    *firewall or proxy*
    we checked everything and excluded firewall (completely turned off - this
    did not fix the error)

    *Is this still happening?*
    yes
    simple curl example

    curl -v https://rubygems.org/gems/dry-container-0.6.0.gem
    * 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

    *Sometimes we see this kind of thing happen intermittently.*
    sad =(

    *Have you tried updating to the latest versions of openssl and bundler?*
    Yes, latest openssl, bundler and gem.

  3. 3 Posted by mark.vunder on 08 Feb, 2018 01:50 PM

    mark.vunder's Avatar

    extended curl example

    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: /
    > 
    < 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
    
  4. Support Staff 4 Posted by kerrizor on 08 Feb, 2018 07:50 PM

    kerrizor's Avatar

    It looks on our end that you're not being rate limited, but more like you're having an SSL issue connecting to fastly

  5. 5 Posted by mark.vunder on 08 Feb, 2018 08:32 PM

    mark.vunder's Avatar

    Same thing without ssl - when we try http://rubygems.org
    See third comment (http://help.rubygems.org/discussions/problems/30195-rate-limits-fro...)

  6. 6 Posted by mark.vunder on 08 Feb, 2018 09:17 PM

    mark.vunder's Avatar

    we found relative issue with fastly
    https://community.fastly.com/t/problem-with-tcp-resets/944

    Apparently we need to write directly to them.

  7. Support Staff 7 Posted by kerrizor on 10 Feb, 2018 10:49 PM

    kerrizor's Avatar

    At this time Fastly believes the issue resolved. More information can be found here: https://status.fastly.com/incidents/k3zzxnkz4vcd

  8. kerrizor closed this discussion on 10 Feb, 2018 10:49 PM.

Comments are currently closed for this discussion. You can start a new one.

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