It seems the problem is already solved, as noted in the external source: http://permalink.gmane.org/gmane.comp.lang.ruby.rails/264228
It was a network problem. On 2 feb, 05:35, Mirage2008 <rose.emm...@gmail.com> wrote: > Actually it wasn't trivial. It helped me :0) > > After the RubyGem/Bundler update mess yesterday, I was afraid there > was yet another problem with my set up. Turns out my Time Machine's 5 > GHz network was insanely unstable and caused the error. If it weren't > for your post, I would have spent hours searching for the problem (as > I'm a Rails newbie). A big thank you to you Mr. Melzer is in order, > so "Thank you!" > > On Jan 25, 4:56 am, Norbert Melzer <timmel...@googlemail.com> wrote: > > > > > > > > > I know that sounds trivial, and the thread is two weeks old, but are you > > sure you are connected to the Internet during that tests? It took me > > yesterday 2 hours to find that problem on my local staging environment. Due > > to configuration problems I could connect via ssh and remote control, but my > > network did not route requests from the staging to the Internet, the just > > got lost. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
