Not specifically a Rails problem; but is anyone else having problems
accessing http://rubygems.org or installing gems?
It’s not working for me from my home internet (in the UK), internet on
my phone, or a VM in Chicago…
Having not seen anyone complaining about it this morning makes me
wonder if it’s just me; but that’s three different internet
connections failing…
Michael P. wrote:
Not specifically a Rails problem; but is anyone else having problems
accessing http://rubygems.org or installing gems?
It’s not working for me from my home internet (in the UK), internet on
my phone, or a VM in Chicago…
Having not seen anyone complaining about it this morning makes me
wonder if it’s just me; but that’s three different internet
connections failing…
The same problem here in Germany:
http://www.rubygems.org/
Der DNS-Server gab:
Server Failure: The name server was unable to process this query.
C:>gem install termios
ERROR: While executing gem … (Gem::RemoteFetcher::FetchError)
bad response Service Unavailable 503
(http://production.cf.rubygems.org/gems/termios-0.9.4.gem)
Klaus-dieter Gundermann wrote:
Michael P. wrote:
Not specifically a Rails problem; but is anyone else having problems
accessing http://rubygems.org or installing gems?
It’s not working for me from my home internet (in the UK), internet on
my phone, or a VM in Chicago…
Having not seen anyone complaining about it this morning makes me
wonder if it’s just me; but that’s three different internet
connections failing…
The same problem here in Germany:
http://www.rubygems.org/
Der DNS-Server gab:
Server Failure: The name server was unable to process this query.
C:>gem install termios
ERROR: While executing gem … (Gem::RemoteFetcher::FetchError)
bad response Service Unavailable 503
(http://production.cf.rubygems.org/gems/termios-0.9.4.gem)
posted on http://twitter.com/gemcutter:
Site is up, but DNS is not. Working on it, temp fix:
rubygems_dns_failover · GitHub
I had problems most of the afternoon here in the US with gems located
at
rubygems.org. Hopefully will be fixed tomorrow. There’s gotta be some
kinda of redundancy/mirroring provided by this site or at least
and indication on the site about the DNS operational status.