Open scottyeager opened 1 year ago
Yeah, this means probably the node did not get ipv6 after reboot. Can be issue with the router again. When that happened the workloads failed to reconfigure.
I see. It would be nice if the Wireguard and Yggdrasil interfaces could survive in this case.
I've had a VM running on node 426, and noticed today that it wasn't functioning as expected. When I pull up its details in the Playground, I see a couple of networking related errors:
could not get public ip config: public ip workload is not okay
could not look up ipv6 prefix: no public ipv6 found
When I try to ssh to the yggdrasil IP, it hangs.
Checking the node's logs, I do see that it was recently rebooted. The timing seems coincident with the failure.
Here is the full JSON output from the Playground regarding the contract: