Error fetching https://gems.ruby-china.org/: bad response Not Found 404 (https://gems.ruby-china.org/specs.4.8.gz)

https://gems.ruby-china.org/ 访问不了

域名改为

https://gems.ruby-china.com/

所以替换 ruby-china 提供镜像，正确的操作是：

$ sudo gem update --system

$ gem sources --remove https://rubygems.org/

$ gem sources --remove https://ruby.taobao.org/ //如果安装了淘宝的镜像

//等有反应之后再敲入以下命令

gem sources -a https://gems.ruby-china.com/

为了验证你的Ruby镜像是并且仅是ruby-china，可以用以下命令查看：

$ gem sources -l

p.p1 { margin: 0.0px 0.0px 0.0px 0.0px; font: 11.0px Menlo; color: #000000; background-color: #ffffff }
p.p2 { margin: 0.0px 0.0px 0.0px 0.0px; font: 11.0px Menlo; color: #000000; background-color: #ffffff; min-height: 13.0px }
span.s1 { }

*** CURRENT SOURCES ***

https://gems.ruby-china.com

原文地址：https://www.cnblogs.com/joyce306/p/9542777.html

时间： 2024-11-01 13:26:45

Error fetching https://gems.ruby-china.org/: bad response Not Found 404 (https://gems.ruby-china.org/specs.4.8.gz)的相关文章

cocoapods 更新失败 bad response Not Found 404 (http://ruby.taobao.org/specs.4.8.gz)

ERROR: Could not find a valid gem 'cocoapods' (>= 0), here is why: Unable to download data from http://ruby.taobao.org/ - bad response Not Found 404 (http://ruby.taobao.org/latest_specs.4.8.gz) 解决办法:换源地址 gem sources --remove http://ruby.taobao.org/

Jenkins报错Error fetching remote repo ‘origin‘真正解决办法

Jenkins build时报错Error fetching remote repo 'origin',网上大部分文章都说是git权限问题,其实并不是,造成这个问题的原因是Jenkins有个工作空间( workspace)的概念,Jenkins build时产生的缓存会保存到工作空间里,我们把缓存清理掉就好,参照截图原文地址:https://blog.51cto.com/kusorz/2358348

ERROR: Error fetching remote repo 'origin' 错误解决

千万不要慌张,认真看控制台输出 ERROR: Error fetching remote repo 'origin'...... Caused by: hudson.plugins.git.GitException: Command "git config remote.origin.url http://aaaaaaaaaaaaaaa.git" returned status code 255: stdout: stderr: error: could not lock config

解决Jenkins上git出现的“ERROR: Error fetching remote repo 'origin'”问题

今天对清掉了Jenkins中项目的工作空间,结果构建出现“ERROR: Error fetching remote repo 'origin'”问题:网上各种找也没找到解决这个问题的方法. 后来看错误之前是“> git.exe config --local --remove-section credential # timeout=10”,不会是跟密码有关吧! 于是将url改成http://用户名:密码@ip/的格式,git配置改成不使用密码,结果OK了. 解决Jenkins上git出现的"

eth0: error fetching interface information: Device not found

转载,原文出处:http://zh888.blog.51cto.com/1684752/775447 亲测有效,感谢作者!!! ----------------------------分割线---------------------------------------------------- eth0不见了的处理方法 1.刚开始运行ifconfig eth0发现网卡不见了.[[email protected] ~]# ifconfig eth0eth0: error fetching inte

Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

sudo docker run hello-world docker: Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers).See 'docker run --help'. 修改docker镜像源: docke

docker pull / docker login 报错 Error response from daemon: Get https://registry-1.docker.io/v2/: x509

docker pull 和 docker login 的时候报错 Error response from daemon: Get https://registry-1.docker.io/v2/: x509: certificate is valid for bw-production.space, brickworksoftware.com, *.bw-production.space, *.brickworksoftware.com, not registry-1.docker.io 从报错

mac上docker pull是报错Error response from daemon: Get https://xx.xx.xx.xx/v2/: Service Unavailable

执行docker pull xx.xx.xx.xx/xx/xx,下载私有库的镜像时报错如下: Error response from daemon: Get https://xx.xx.xx.xx/v2/: Service Unavailable 原因大概是docker默认支持https的协议,而私有库是http的协议. mac桌面可以在Preferences-->Docker Engine里配置以下代码,xx.xx.xx.xx是自己私有库的地址. { "insecure-registri

Docker问题解决：Error response from daemon: Get https://registry-1.docker.io/v2/yandex/clickhouse-server/manifests/latest: net/http: TLS handshake timeout

方法1: vi /etc/docker/daemon.json { "registry-mirrors": ["http://hub-mirror.c.163.com"] } systemctl restart docker.service 方法2: vi /etc/sysconfig/docker OPTIONS='--selinux-enabled --log-driver=journald --registry-mirror=https://docker.mi