Failed to load remote gems http://gems.rubyonrails.org
The following notification keeps popping up:
Failed to load remote gems http://gems.rubyonrails.org
(Gem::RemoteFetcher::FetchError)
bad response Not Found 404 (http://gems.rubyonrails.org/prerelease_specs.4.8.gz)
Please check proxy settings and gem urls
Has any one else seen similar?
I don't use a proxy server and the settings aren't set to use one. I've added http://gems.rubyonrails.org to my gem sources with the following:
gem sources -a http://gems.rubyonrails.org
but it keeps popping up any ideas, anyone?
--
Taine
Please sign in to leave a comment.
I'm getting the same exact error as of yesterday. Noticed it right after RubyGems upgraded to 1.5.0 -- not sure if that's a coincidence or a cause.
-BT
Mine doesn't keep popping up, but it displays whenver I am creating a new project and click the elipses link to the right of "Rails Version:"
I've had a lot of gem wonkiness going on, so I decided to start at the beginning and follow the RubyMine quick start guide, but I can't get past the first thing, creating a new project. ? Here is the screen shot of the popup error:
Here's the wonky part...settings can find all my local gems with correct versions (under "List Gems...") as well as remote gems with latest versions (under "Install Gems..."), but when using the app, it's like it doesn't have access to the same gem information that the settings page has access to. VERY frustrating. I can't even begin to learn how to use the app because of the gem issues (more than just not being able to install gems).
When I go into File / Settings / Template Project Settings / Ruby SDK and Gems, the Ruby Interpreter is correctly showing the version of ruby I built: "Ruby SDK 1.8.7-p302(/usr/local/bin/ruby)[1.8]". It is the only SDK in the drop down, although I probably do still have the default ruby that comes with OSX, it is not displayed in the drop down.
I don't know if I should start new discussion threads for each of the gem-related errors I've been struggling with, or wait and see if this one has a work around/resolution that might apply to all of them. BTW, I just purchased/installed RubyMine 3.0.1 last night, so I don't konw if this is something that has just recently happened, or a known bug, but this thread is the only one I found via search that describes the error I'm getting.
OSX 10.6.6
(I believe my ruby version is 64bit)
RubyGems Environment:
- RUBYGEMS VERSION: 1.3.7
- RUBY VERSION: 1.8.7 (2010-08-16 patchlevel 302) [i686-darwin10.4.0]
- INSTALLATION DIRECTORY: /usr/local/lib/ruby/gems/1.8
- RUBY EXECUTABLE: /usr/local/bin/ruby
- EXECUTABLE DIRECTORY: /usr/local/bin
- RUBYGEMS PLATFORMS:
- ruby
- x86-darwin-10
- GEM PATHS:
- /usr/local/lib/ruby/gems/1.8
- /Users/randy/.gem/ruby/1.8
- GEM CONFIGURATION:
- :update_sources => true
- :verbose => true
- :benchmark => false
- :backtrace => false
- :bulk_threshold => 1000
- :sources => ["http://rubygems.org/", "http://gems.github.com", "http://gems.rubyonrails.org"]
- REMOTE SOURCES:
- http://rubygems.org/
- http://gems.github.com
- http://gems.rubyonrails.org
Hope somone can help us get past this.
-=Randy
It would sure be nice if someone from Jetbrains could fill us all in on what's going on...
Is the problem with http://gems.rubyonrails.org is still actual? I've just tried and seems it works. Probably it was some temporary problem with rubyonrails web site?
Also you may remove this gem url in "File | Settings | Ruby Sdk And Gems | Install (button) | Manager gem URLs..." dialog
Our college managed to reproduce the problem. Seems it is related to new rubygems version. Just remove http://gems.rubyonrails.org source from list. This repo contains some exotic rails db adapters and most likely you don't need them.
It still fails for me. I did not start this thread, so I'm not sure what steps the originator took to reproduce this popup error. I hope he is reading this and verifies if his issue was resolved by removing rubyonrails.org from the 'manage gem urls' list. But I can tell you the steps I take that still cause the error:
Per the getting started guide, I click on Create New Project:
This opens the following dialog box that I configure like so:
When I click OK, it opens this next dialog box, displaying the correct Ruby SDK for my system and the latest version of the Rails gem I have installed:
When I click the highlighted elipses to the right of the Rails Version: drop down, I get the following three popups every time:
If I go into File / Settings / Ruby SDK and Gems / Install Gems..., I see all of the remote gems available for install:
If I scroll down a bit, I can see that rails 3.0.4.rc1 is found:
This tells me the app can indeed find remote gems. I got this full list even before I removed rubyonrails.org from the "Manage gem URLs..." list. I have since added "http://rubygems.org" to the list so it is just now github and rubygems.org.
RubyMine can see remote gems in the settings section but it cannot find specific Rails version gems after clicking the Rails Version elipses while trying to create a new project.
You mentioned your colleague reproduced the issue and that it was linked to the latest rubygems version. The latest rubygems version is 1.5.0 and I still have 1.3.7 installed. So it may be something else that is not linked to the latest.
Nope this problem is no longer actual for me. Apparently it found and loaded the necessary gem, without me removing http://gems.rubyonrails.org from gem URLs. Perhaps, it was some temporary problem with the rubyonrails site.
Taine
I'm still getting the errors. I tried removing http://gems.rubyonrails.org/ using the "Manage gems URLs..." button and adding http://rubygems.org, but these changes aren't persisting - every time I reopen a project, I see the same old gem URLs.
-BT
Did you install rspec-rails BTW? If I recall thats when I believe it started popping up on me.
Taine
Woops! Spoke to soon, its back. :|
Taine
I did, but it was with a bunch of other gems in a fresh install.
-BT
My gem URLs are also reverting back to the original two every time I reopen a project.
Ok, serialization indeed doesn't work. I've filed an issue - http://youtrack.jetbrains.net/issue/RUBY-7796.
Update: Fixed serialization will be available in next 3.1 EAP
Randy,
Thank you for a detailed scenario, but I didn't manage to reproduce it on my Mac. I tried Gem manager 1.3.7 and 1.5.0
Here is the output from the console when I click the ellipse to search for rails gems:
-=Randy
Ok, serialization indeed doesn't work. I've filed an issue - http://youtrack.jetbrains.net/issue/RUBY-7796.
Update: Fixed serialization will be available in next 3.1 EAP
Hi again,
Please try RubyMine 3.1 Beta - http://blogs.jetbrains.com/ruby/2011/02/rubymine-3-1-beta-—-better-faster-and-still-a-lot-cheaper/. If the problem occurs again please attach a log as described at javascript:;
It is still happening with 3.1 beta. I will read through the attach logs section later today.
I have the Little Snitch firewall installed and when I clicked the ellipse to search remote rails gem versions, Little Snitch asked permission for RubyMine 3.1 to access each of the URLs from my gem sources list. One by one, I allowed access forever.
Yes, it still fails when I completely disable Little Snitch.
-=Randy
I started to get these same errors today loading up my current project.
Yes, I am getting these pink messages too.
It looks like there might be a recursive loop somewhere in the new code. It keeps recursing until it runs out of memory, or triggers a non-obvious error, or encounters a stack level check..
Is there any way to increase the stack available? (Although, if this is a recursive code error, no amount of stack will prevent the error - it will just take longer to get there).
Bob G
I just ran a long process (about an hour) under RoR which usually goes without a problem.
The SegFault error I got may be related to the pink messages
See attached file for fragment of error traceback.
The second file is more of the error traceback - further down in traceback.
Attachment(s):
Segfault.zip
Segfault-more.zip
The segfault error reported above does not seem to be related to the pink messages.
I made some code changes to overcome changes in new data and my next run was successful.
Even though there were pink messages at initial load of Rubymine and my application, they don't seem to have an effect on the running.
duplicate
Same problem here. 3 pink messages everytime I start my project.
It occurred for the first time using RubyMine 3.1.1 in some new Git branch (clone of the master) my colleague created. It only appeared when this branch was checked out. At some point, we merged the branch with the master.. and guess what..? Now, the problem started to appear when the master was checked out as well !! ?:|
I compared the two branches and attempt to discover what could be the reason that cause RubyMine to report those errors. I was not able to find anything relevant. We only added a bunch of JS and CSS files, and changed some ERBs. Gemfile remained unchanged.
I, too, have been getting the three pink boxes as of yesterday. I close them and they don't seem to have any impact on the execution of my code, as far as I can tell, but it'd be nice to know what's going on and how to fix it.
Attachment(s):
failed to load remote gems errors.jpg
To start off, I am not a very experienced programmer but I love Rubymine.
That aside, I did a little digging and would like to add to the discussion with my findings.
First, following a suggestion earlier in this thread, I found that there were no gems listed as available under File > Settings > Ruby SDK and Gems > Install Gems as shown in the included screenshot.
Next, I performed a few scans using nmap to test open ports on the network. Since no gems are showing under my gem list (above), I would assume that a connection problem would be the issue. Here is a list of all relevent open ports (all secured, no bad ideas here, people).
Nmap scan report for gems.rubyonrails.org (208.75.86.244)
Host is up (0.045s latency).
rDNS record for 208.75.86.244: 208-75-86-244.slicehost.net
Not shown: 993 closed ports
PORT STATE SERVICE
.....................................
80/tcp open http
.....................................
Here is the same scan on gems.github.com.
Host is up (0.048s latency).
Not shown: 997 filtered ports
PORT STATE SERVICE
....................................
80/tcp open http
....................................
Since the listed info within the gem urls uses HTTP, we can assume that port 80 is the only relevent port to this request. A curl request to gems.rubyonrails.org returns a forbidden page (possibly part of the issue) while the same request to gems.github.com returns a page stating that, while gems are still hosted on github, they will no longer be hosting them down the road. The page refers you to www.rubygems.org. Possibly this is the root of the issue. Have github and rubyonrails.org blocked your service from requesting gem urls automatically in an attempt to migrate this service to a site dedicated to it? Thousands on concurrent users all making requests for gems constantly can kill a server especially one that has other purposes (possibly github has another use than hosting gems, who knows???).
Thanks for the hard work, guys. Hope to see a fix for this. Let me know if I can be of any further help.
Attachment(s):
screenshot1.jpg
Me too.
(rubymine 3.2.1, windows vista, rspec 2.6.0, ruby 1.9.2 )
Same problem here. 3 pink messages everytime I start my project.
Since yesterday.
I wonder if it could be connectivity issues at http://gems.rubyonrails.org.
I just tried opening the page up to be rewarded with a 403 Forbidden message.
Agree, no connect to http://gems.rubyonrails.org/
The link in your message points to the message itself. You have to key in the http://gems.rubyonrails.org/ but no connect.
For me, this seems to be specific to Ruby 1.9x Loading up a 1.8.7 project it had no issues and perhaps the latest verson of the gem. However, I did not update any gems before this began so perhaps something changed on the sources for the gems that has confused RM. I am able to update directly from git bash, so that also suggests some change in the sources (but why all of them at once?) trickled something that is only present when RM (3.1.1 in my case....not tested on latest RM) initiates the check for gems.