tag:help.rubygems.org,2010-01-19:/discussions/problems/28678-500-internal-server-error-when-pushing-a-gemRubyGems.org: Discussion 2018-05-27T22:04:44Ztag:help.rubygems.org,2010-01-19:Comment/440029502017-11-09T20:17:04Z2017-11-09T20:17:04Z500 Internal Server Error when pushing a gem<div><p>Hi,</p>
<p>I'm trying to push a new gem to RubyGems this afternoon and am getting a 500 internal server error. Here is the verbose output:</p>
<p>$ gem push --verbose fanciful-0.0.1.gem GET <a href="https://api.rubygems.org/latest_specs.4.8.gz">https://api.rubygems.org/latest_specs.4.8.gz</a><br>
304 Not Modified<br>
Pushing gem to <a href="https://rubygems.org">https://rubygems.org</a>...<br>
POST <a href="https://rubygems.org/api/v1/gems">https://rubygems.org/api/v1/gems</a><br>
500 Internal Server Error<br>
There was a problem saving your gem. Please try again.</p>
<p>and the debug output</p>
<p>$ gem push --debug -V fanciful-0.0.1.gem NOTE: Debugging mode prints all exceptions even when rescued<br>
Exception <code>LoadError' at /Users/landry/.rbenv/versions/2.4.0/lib/ruby/2.4.0/resolv.rb:171 - LoadError Exception</code>Errno::EEXIST' at /Users/landry/.rbenv/versions/2.4.0/lib/ruby/2.4.0/fileutils.rb:228 - File exists @ dir_s_mkdir - /Users/landry/.gem/specs/api.rubygems.org%443<br>
GET <a href="https://api.rubygems.org/latest_specs.4.8.gz">https://api.rubygems.org/latest_specs.4.8.gz</a><br>
304 Not Modified<br>
Pushing gem to <a href="https://rubygems.org">https://rubygems.org</a>...<br>
POST <a href="https://rubygems.org/api/v1/gems">https://rubygems.org/api/v1/gems</a><br>
500 Internal Server Error<br>
There was a problem saving your gem. Please try again.</p>
<p>Is something going on with the server? <a href="https://status.rubygems.org/">https://status.rubygems.org/</a> is 'All Systems Operational`</p></div>Conortag:help.rubygems.org,2010-01-19:Comment/440029502017-11-09T21:17:03Z2017-11-09T21:17:05Z500 Internal Server Error when pushing a gem<div><p>I found the problem. I had gem.date set to '1017-11-09' instead of '2017-11-09'. It works now. Should the server be giving a 500 error when this happens or is this a bug in rubygems?</p></div>Conortag:help.rubygems.org,2010-01-19:Comment/440029502017-11-09T21:18:18Z2017-11-09T21:18:18Z500 Internal Server Error when pushing a gem<div><p>I saw this error on the server. It was unable to parse the data. We probably should be returning a 4xx error since this was bad input.</p></div>David Radcliffe