No route to host: container does not start

Node Operators troubleshooting
, ,
1

hello,
I got this message for all satellites:
ping satellite: rpc: tcp connector failed: rpc: dial tcp 34.2.157.232:7777: connect: no route to host"

canyouseeme works fine, and this from the host

nc -vz 34.2.157.232 7777                                                                                                                                                                                                                                                                                   
Connection to 34.2.157.232 7777 port [tcp/*] succeeded!

for other ip I get this from the host sometimes

nc -vz 35.207.121.91 7777                                                                                                                                                                                                                                                                                 
nc: connect to 35.207.121.91 port 7777 (tcp) failed: No route to host

in docker:

ip route
default via 172.17.0.1 dev eth0 
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.3

I got the no route errors in the other container on the same network but in the console says QUIC is OK.
But the other node does not even start.
What can I do? Thanks

2

Hello @paveldvorak,
Welcome back!
Since you have this error even from the host, your network on this host doesn’t work properly.
You need to Google the usual networking troubleshooting for Linux, it’s not related to the node, and likely not related to docker.
I may suggest to purge docker from this setup and install it back, using the official docker documentation for your distro. Please do not use snap or flatpack versions of docker, they likely will not work properly.