I did a reboot while back for other reason and ever since then the GUI decided not to work under https. I get a 404 error. 

 

I have tried changing the https port to 10443, 10444,11443. And it just won't work. I do see in the logs that it couldn't allocate the port which is quite strange as nobody is using it. 

 

Last change I did make which didn't affect anything at least from what I could tell was swap port 443 from the unraid to the swag docker container so I can have some split tunnel functionality. 

 

Now my swag docker is 443 and my unraid GUI is 10443. It was working for while 

 

It's weird very. I simply don't know where to look at. At this point I stopped the docker to make sure there's no conflict and what not

I would leave unraid on 80 and 443 its best not to change them. Is it possible you were using 443 for both unraid and Swag?  Try switching swag to an unused port like 180 to container port 80 and 1443 container port 443.  Assuming 180 and 1443 are free.

swag right now is using 443 and unraid well, right now none. i tried switching to unused ports with no avail, is very strange. 

 

As for swag is was recommended from someone at linuxserver to do split tunneling so locally i can hit my nextcloud with the IP of the unraid

It's very weird how my unraid has been behaving regarding the ports. For now I have left it using port 80 and I can come back to it later. Maybe something I can report as a bug to lime tech