.members
is the one the node name resolves too, and if you don't have an internal DNS infrastructure this is most likely coming from /etc/hosts
on the affected node itself.Understood, it seems logical to meThe IP shown in.members
is the one the node name resolves too, and if you don't have an internal DNS infrastructure this is most likely coming from/etc/hosts
on the affected node itself.
So, if you edit that (directly or via the API) to its IP from the 192.168.x.y/z network and reboot the node you should be good again.
Edit Thread
button above your initial post at the right.Connection error 595: No route to host
errors in the web UI). I also fixed it by editing /etc/hosts.systemctl restart pve-cluster
), so I'm leaving that comment in case that helps anyone else.We use essential cookies to make this site work, and optional cookies to enhance your experience.