Close
Glad You're Ready. Let's Get Started!

Let us know how we can contact you.

Thank you!

We'll respond shortly.

LABS
Where, oh where has my gem server gone?

Uh-oh!

ERROR:  While executing gem ... (Gem::RemoteFetcher::FetchError)
    bad response Moved Permanently 301 (http://gems.rubyforge.org/latest_specs.4.8)

Whew!

gem sources -a http://rubygems.org/
gem sources -r http://gems.rubyforge.org/

Looks like they weren’t kidding when they said to switch from rubyforge to rubygems.org (née gemcutter)!

[Edited to change “http://production.s3.rubygems.org/” to “http://rubygems.org/”. Note that the trailing slash is significant!]

Comments
  1. Luis Lavena says:

    You shouldn’t be adding the s3 configuration directly but instead http://rubygems.org

    That will handle automatically the redirect to either S3 or the CDN for faster delivery of gems.

    gem sources -a http://rubygems.org

  2. Alex Chaffee says:

    Thanks, Luis! I’ll go update the article now.

Post a Comment

Your Information (Name required. Email address will not be displayed with comment.)

* Copy This Password *

* Type Or Paste Password Here *