- Minor
I maintain Zerotier Docker extension. The extension creates a virtual interface and provides remote access to the server through the private virtual network. Through the years and recent updates of Unraid, the extension experienced several changes / troubles, but the latest one does look like a bug.
Many versions ago, something changed and UI stopped listening on the virtual interface. It wasn't on the Release Notes I believe. However, after some investigation, I found a solution and added one more step to the instructions to manually add the virtual network to the set of the "listening interfaces" in network settings. Unfortunate, but not a big deal. Things worked.
Somewhere in 6.12.x updates, it broke worse.
Now, when you initially add the virtual network to "listening interfaces", UI starts to respond on this interface correctly. However, after the server restart, the connection to port 80 (and 22) is rejected with a "connection reset" if accessed through the virtual network. While the virtual interface is still on the list of the "listening interfaces" in the UI, the server UI doesn't listen on it after restart.
To fix it, after every restart, you need to manually remove the interface and re-add it. What makes matters worse, you need to have local access to do that. This doesn't look right, it does look like a bug.
Users of the extension found a workaround and published a User Script. The script waits for the docker image to start and restarts Nginx after that. This looks like a hack and shouldn't be needed.
Please note that the problem and all these manual steps exist for Unraid UI only, all the docker containers and their ports are available this whole time just fine without manually adding the network interface altogether.
My speculation is Nginx starts first, doesn't see the interface, ignores it, and doesn't pick it up later when the docker that services that network actually starts up.
Could you please help to investigate and fix the recent bug that broke UI ability to listen and respond on an explicitly declared additional interface serviced by a docker image after a server restart? It didn't require a manual Nginx restart before and shouldn't need it now.
Could we also consider reverting the original change from many versions ago and making UI listening on all network interfaces by default again? This was so much easier and it feels like a sensible default.
Related user bug report:
The issue is present on the latest Unraid 6.12.13