I've got the UnRAID web interface running on port 9999 and I'm using local DNS and nginx-proxy-manager to have http://example.home route to the UnRAID host IP on port 9999.

 

When I attempt to add a Docker container, the AddContainer page (once clicking Apply to download the images and create the container) takes 10-15 seconds to load/show and only once the container images are fully downloaded and the docker commands have run.  If I browse to http://example.home:9999 and add the same Docker app, the page loads immediately and shows the output of the log where it displays the images being downloaded and the docker command being run.

 

I'm wondering why UnRAID is doing this and how I might fix it so I don't have to go to the specific port in order to see the active log when adding a docker container (and I suspect it's also doing it when updating containers or any other feature that may output information from a log).

 

The main thing I tried, to no avail, is to set the "Server name" value in the "Identification" settings to: example.home (of course, I use something other than "example", but this illustrates the same thing).

 

EDIT>> Also, the VM logs popup won't show data, the page just acts like it's loading forever.  If I add in the port to the URL, the logs show fine.  I suppose something is relying on the port showing in the URL for VM logs (and docker container create/update) to show in the UI and I'm confused as to why it would be necessary.

EDIT 2>> Another quirk I noticed is that the Dashboard won't show the active CPU load when the site loads without the port being in the URL.  Nevermind, I solved this by adding Websocket support on the nginx-proxy-manager proxy for example.home.

Edited March 7, 20224 yr by ulkesh

Second topic I've posted with no replies I guess I just do things people don't do.  Ah well.  If anyone has any insight, it'd be appreciated.  In the meantime, I suppose I'll just have to use the port in the URL.