Some issues today with a windows node that crashed and corrupted the network.conf file. I uninstalled, deleted the node from the web-ui and rejoined the network. All good, except this node could no longer ping one other remote window server node. In the web-ui I noticed that this node came back listening on port 51822. Traffic is forwarding to it on 51821. After updating the port in the web-ui and pulling configs from the server, the config and conf file the showed 51821 correctly, but wg showconf nm-mat showed it was still listening on 51822. The only way I could find to get wireguard reading the new config was rebooting. Then it worked normally again. This behaviour matches some of the problems I was seeing in the early stages of getting the network setup, and may relate to @User's problems as well. Essentially the window client is pulling the configs but the network isn't resetting properly following a pull command at least in my testing