January 23, 20188 yr I changed the ports for unraid from 80/443 to 81/444 in the identification settings and I lost access to my Webgui. So, I booted up in GUI mode to change back - but I can't even access the webgui via localhost. Server boots fine - I just can't access webgui. Help please Diags attached from shutdown. highlander-diagnostics-20180123-1227.zip Edited January 23, 20188 yr by DZMM corrected ports
January 23, 20188 yr Author ok, realised I could connect to server on SERVER:81, so I changed ports back and all was ok from my VM. I still couldn't access localhost until I rebooted the server though - is this normal?
January 23, 20188 yr Just now, DZMM said: I still couldn't access localhost until I rebooted the server though - is this normal? Did you type in localhost:81? If not, then yes, it's normal not to be able to access a service on port 80 when it's being served on 81.
January 23, 20188 yr Community Expert 1 hour ago, DZMM said: I changed the ports for unraid from 80/443 to 81/444 in the identification settings and I lost access to my Webgui. It is not the best idea to reassign any server port using the range from 0 to 1024. (That range used by most services as the 'standard' ports!) See here in the first post for recommendations: https://lime-technology.com/forums/topic/66327-unraid-os-version-640-stable-release-update-notes/ There you will find: Quote NOTE: If you need to change the defaults, be sure to pick high values over 1000. i.e. 81 and 43 are *not* good options. Try 8080 and 8443
January 23, 20188 yr If I need to host a VM or similar so I need alternative ports, I normally ad 10000 - so the VM might get 10022, 10080 and 10443. And a second VM might get 20022, 20080, 20443. This concept also works well when doing port forwarding using an SSH tunnel. So localhost:100443 on my workstation might tunnel to an https server on the other side of a ssh tunnel. It isn't forbidden to use low port numbers, but in the original TCP design they are treated as system-reserved, and a normal end-user program can't open a listener on a low port. That's to make sure that a user who notices a machine doesn't have a ftp server should not be able to install a fake server to steal passwords and other information. But besides this, there is also a much larger probability of getting compatibility issues at a later stage if using random low-numbered ports. The software designers and the people who package the software will not take into account users who have picked up random low-numbered ports for own use.
Archived
This topic is now archived and is closed to further replies.