tag:help.rubygems.org,2010-01-19:/discussions/problems/4322-connection-reset-while-pushing-gemRubyGems.org: Discussion 2018-10-18T19:51:17Ztag:help.rubygems.org,2010-01-19:Comment/263462342013-04-11T11:29:25Z2013-04-11T11:30:29ZConnection reset while pushing gem<div><p>Hi. Since yesterday, I've been unable to push a new version of
my jasper-command-line gem. I keep getting the "too many connection
resets" error.</p>
<p>I've checked the web for solutions, and came up with threads
from 2010, regarding the <code>~/.gem/credentials</code> file. I've
checked mine and it's in the correct format.</p>
<p>Pushing the gem with <code>-v</code> option yields the
following:<br></p>
<pre>
<code>> gem push jasper-command-line-0.4.1.gem -v
GET http://rubygems.org/latest_specs.4.8.gz
302 Moved Temporarily
GET http://production.s3.rubygems.org/latest_specs.4.8.gz
200 OK
Pushing gem to https://rubygems.org...
POST https://rubygems.org/api/v1/gems
connection reset after 1 requests, retrying
POST https://rubygems.org/api/v1/gems
connection reset after 1 requests, retrying
ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError)
too many connection resets (https://rubygems.org/api/v1/gems)</code>
</pre>
I don't know if this is related to the gem size (roughly 18 MB),
but previous versions of the gem were also roughly the same size.
<p>Any idea as to what could be causing this?</p>
<p>Thanks,<br>
Pedro</p></div>pedrotag:help.rubygems.org,2010-01-19:Comment/263462342013-05-08T00:14:58Z2013-05-08T00:14:58ZConnection reset while pushing gem<div><p>Is this working now?</p></div>Nick Quarantotag:help.rubygems.org,2010-01-19:Comment/263462342013-05-08T07:56:58Z2013-05-08T07:56:58ZConnection reset while pushing gem<div><p>Yes, sorry, it must have been a problem that day.</p></div>pedro