- Annoyance
I've found that if the NIC reconnects to the network for whatever reason (network goes out, Ethernet unplugged, etc.) and receives a different IP address than when Unraid first booted, then the mDNS and TLS certificate are not bound to the new IP address. This is not usually a problem, as I have DHCP static IP assignment set up on my router. But this can occur if I'm changing that IP assignment, for example, and reboot the router to have it assign the new IP. Or I've also seen it where the NIC failed to get an IP on first boot, resulting in a 169.254.x.x IP address. If I unplug and reconnect the Ethernet cable, when the NIC gets the expected IP, the mDNS (e.g. tower.local) hostname is still bound to the 169.254.x.x IP (which fails to load the web interface). If I go to the new IP address manually I also get a certificate warning, as it's using a self-signed certificate, rather than the myunraid.net certificate, for the fresh IP address. Rebooting the server is required to resolve this.