tinyaim

The only way I have managed to get a work around for this is to add the search domain to the network interface. Not idea but does actually stop having to use FQDN.

I have an update. Not totally sure I did regarding the Docker networking but it certainly interfered with the web hosting for the Unraid web UI. To recover the UI I had to SSH into the server and initially I ran docker commands to stop all the running containers. To be safe I completely removed the offending container that I changed to cause this to go wrong. Once I had docker stopped the UI started working. To stop getting into issues I have reviewed the Docker networks and reverted back to the the standard Bridge and host networks. I am now in the process of carefully bringing back each of the Docker containers.

Yep I know that but in playing I set it to host and it seems to have taken out the unraid webui. I have no easy way of setting back that I can see. The current acces I have to the server is via SSH.

I have an issue where I was playing with the network settings of a docker container. It was set to a custom "docker" network and was changed to "host". The upshot of that was the server seems to be working but the Web GUI just hangs. I have the USB boot disk backed up to a remote server using this plugin. I have 2 questions. 1) will restoring the boot disk back prior to this change resolve the issue or not ? 2) if 1) is true what is the best way to restore that remote folder backup back to the USB boot disk. I suspect the answer to 1 is no but currently I have a crippled Unrad server that is driving me nuts to get back working properly. I am also struggling to get the diagnostics zip file off the server. I have tried sftp which just hangs but is there any other way to get this off the server so that I can interrogate properly. thanks

On the container that you want to use the OpenVPN container set the network to None and in advanced mode add the following to the extra parameters variable "--net=container:[container_name]" setting the [container name] to the openvpn container name you have chosen eg "--net=container:OpenVPN"

I had this problem. It materialised when I renamed a container (VPN) to a different name. All the containers that had extra parameters using the net parameter to utilise the VPN container went into a recursive rebuild process. Hope this helps someone else having these problems. I rename the offending container back and all reverted to be good. Diagnosed in the system logs for the UNRAID server.