Ustrombase Posted September 22, 2022 Share Posted September 22, 2022 Hi, I changed my default ports for the unraid webui to 280 and 2443 from the default. I checked and these ports are not used for any docker container. After changing the ports I could still access my webUI via the obfuscated myunraid.net url but not via https://IP:NEWPORT. I did an nginx restart and this broke everything as in the myunraid.net url was inaccessible. I did a restart and I went back to being able to access the webui via the myunraid.net url but again no via https://IP:NEWPORT. I have SSL/TLS option in the management settings to be strict. This leads me to believe that when I type the IP:PORT it doesn't recognize the port correct to redirect to the myunraid.net url. Maybe the DNS record needs to be updated? Quote Link to comment
Ustrombase Posted September 22, 2022 Author Share Posted September 22, 2022 OK so it seems that the redirect only happens when you access the http version of the site not the new HTTPS version so since I changed both ports I actually needed to try using http://IP:280 which is my 80 / http port. My bad. Quote Link to comment
trurl Posted September 22, 2022 Share Posted September 22, 2022 17 minutes ago, Ustrombase said: changed my default ports for the unraid webui to 280 and 2443 from the default. I checked and these ports are not used for any docker container. Standard way to deal with this is to leave those default ports alone and map ports in the containers. Quote Link to comment
Solution Ustrombase Posted November 6, 2022 Author Solution Share Posted November 6, 2022 On 9/22/2022 at 8:58 AM, trurl said: Standard way to deal with this is to leave those default ports alone and map ports in the containers. Yea so the reason i couldn't do this is bc I am trying to give https to my internal services and use my domain name to access them for convenience, to do this I needed to establish split DNS and for that, since I use pfsense, I had to use host overrides entries in the DNS Resolver. Well for this you have to link to a rev proxy that is using port 80 and 443 since DNS doesn't let you redirect the host to an IP AND a Port, so I had to remap the unRAID for this very reason. I solved it as I was just dumb and didn't realize I had to use the unRAID IP with the new http port and that would automagically redirect to the https port. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.