rubymine failing to load remote gems (Connection refused)

Does anyone else have this problem - i'm seeing it with rubymine 3.1 and 3.1.1 - happening under ubuntu 11.04. I'm connected to the internet via a wireless router. *NO* proxies defined or being used. Yet every time rubymine comes up or i try to start a new project etc, i get these error messages saying it's unable to load remote gems because of a Connection refused error. the specific URL it's trying is http://rubygems.org/specs.4.8.gz which i can get to in my browser just fine.

I double checked the settings in rubymine's http proxy. It's set up not to use a proxy all. I checked my ubuntu network proxy settings and those are set up not to use a proxy either.  

So i can't understand why the program consistently fails to connect. Here's the full error - it's repeated 3 times:

Failed to load remote gems http://gems.rubyonrails.org
(Gem::RemoteFetcher::FetchError)
Errno::ECONNREFUSED: Connection refused - connect(2) (http://rubygems.org/specs.4.8.gz)

Please check proxy settings and gem urls

Any suggestions would be greatly appreciated.

4 comments
Comment actions Permalink

I think there is something wrong with http://gems.rubyonrails.org.  I can't even get there with a browser or wget...

yeti:~ bob$ wget http://gems.rubyonrails.org/
--2011-05-10 15:21:34--  http://gems.rubyonrails.org/
Resolving gems.rubyonrails.org (gems.rubyonrails.org)... 208.75.86.244
Connecting to gems.rubyonrails.org (gems.rubyonrails.org)|208.75.86.244|:80... connected.
HTTP request sent, awaiting response... 403 Forbidden
2011-05-10 15:21:35 ERROR 403: Forbidden.

0
Comment actions Permalink

yeah i noticed that too - but the url for the gem itself works fine. I guess i dont understand the error message - is it complaining about the url for the gem which i am able to access just fine or for gems.rubyonrails.org which as you pointed out is barfing ?

0
Comment actions Permalink

Were you able to get this issue fixed? If yes, could you please share the details?

0
Comment actions Permalink

Which rubygems version do you use? Try to update rubygems, most likely it will resolve the issue.

0

Please sign in to leave a comment.