connect() failed (113: No route to host)
程序员文章站
2022-03-12 18:53:09
...
nginx connect() failed (113: No route to host) while connecting to upstream
Centos7中默认将原来的防火墙iptables升级为了firewalld
请尝试关闭防火墙
systemctl stop firewalld.service #停止firewall
systemctl disable firewalld.service #禁止firewall开机启动
折腾一天。。
上一篇: No route to host
下一篇: kubectl get 报错:Unable to connect to the server: dial tcp 10.20.2.224:6443: connect: no route to host
推荐阅读
-
connect to host slavenode1 port 22: No route to host
-
ssh: connect to host 10.224.120.107 port 22: No route to host
-
ubuntu: ssh: connect to host ubuntu port 22: No route to host
-
Ubuntu 16.04 远程 ssh: connect to host x.x.x.x port xxx: No route to host
-
ssh: connect to host 192.168.1.20 port 22: No route to host解决方案
-
yum -- Failed connect to mirrors.aliyuncs.com:80; No route to host
-
Unable to connect to remote host: No route to host(亲测解决)
-
Tiller pods can‘t connect to k8s apiserver,dial tcp 10.254.0.1:443: no route to host
-
Get value from agent failed: cannot connect to [[192.168.186.130]:10050]: [113]No route to host
-
mount报错failed: No route to host