Hi,

i want to use steamcache, so i need to change port for unraid http.

 

i thought maybe ts because i edited it via smb /flash/ but also if i ssh into it, it displays: 

#!/bin/bash
# Start the Management Utility
/usr/local/sbin/emhttp -p 81 &
~

Read /boot/config/go, 3 lines, 74 chars

 

But when it reboots, its still on 80...?? i have the latest "next" branch.

 

Edited December 8, 20178 yr by nuhll

Did you try changing it in the web interface? It's in settings -> identification

Omg, i will try that, thanks.

Hows the standard go file looking?

Thanks, this works. 

1 hour ago, nuhll said:

Thanks, this works. 

 

It is documented in the first post, though buried:

 

Quote

Other notes (-rc8q):

• The /usr/local/sbin/emhttp line in your /boot/config/go file is no longer used to specify the ports where the webGui listens for connections.  Instead you must configure these on the Identification page.  Alternately if you need to set this up prior to server boot, you may add the port settings in /boot/config/ident.cfg.  Please refer to /usr/local/sbin/emhttp script for more information if you care about this.

 

For 'stable' release we will clean up this change log.

Hi, Ive changed my ports in Identification to 82 and 445 (I use 80/443 already) and it is showing in Ident.cfg also but I cannot access my WebUI now at 192.168.0.200:82 as I would expect or at 445 .. Anything silly I have missed?

restart?

38 minutes ago, nuhll said:

restart?

 

If you mean restart the server, yes tried that...

U sure the IP is correct? Can you ping it?

I'm sure.. I can login via Putty and my VM runs fine.. just can't access the web UI :-(

 

Hmm and 80 isnt working eitehr?

 

try

 

netstat -plnt

Edited January 28, 20188 yr by nuhll

Just now, nuhll said:

Hmm and 80 isnt working eitehr?

 

80/443 loads my website that the Apache docker runs...

 

try

 

netstat -plnt

tcp        0      0 0.0.0.0:445             0.0.0.0:*               LISTEN      2549/smbd
 

Nothing for 82 showing...  which is strange... and 445 should not be smb but nginx??

Yeah, thats strange... 

 

Check the logs i guess they are in var log ?

Port numbers under 1024 are reserved for 'well-known' services. It is recommended to use higher numbers, e.g.

 

80 --> 8080

443 --> 8443

 

You have a conflict with SMB because port 445 is used by this service and consequently nginx can not start, explaining why there is no GUI.

Edited January 28, 20188 yr by bonienl

I use 81 and it works fine.

 

But correct, if it cant bind to 445, then the webserer wont start up.

Edited January 28, 20188 yr by nuhll

2 minutes ago, nuhll said:

I use 81 and it works fine.

 

It works under unRAID but is not recommended.

Thanks guys.. moved them to 8480 and 8443 and all good... Had no idea SMB used 445 :-)

17 minutes ago, methanoid said:

Thanks guys.. moved them to 8480 and 8443 and all good... Had no idea SMB used 445 :-)

Me neither.....

2 hours ago, bonienl said:

 

It works under unRAID but is not recommended.

 

Maybe tie an alert to the Apply button on that page that says something like, "Warning: port numbers under 1024 are reserved for 'well known' services." along with Continue or Cancel button.  Maybe same technique for that docker Container Port field, "This changes port inside the container, is that really what you want to do?".

2 minutes ago, limetech said:

 

Maybe tie an alert to the Apply button on that page that says something like, "Warning: port numbers under 1024 are reserved for 'well known' services." along with Continue or Cancel button.  Maybe same technique for that docker Container Port field, "This changes port inside the container, is that really what you want to do?".

 

Woohoo.. I might have found something useful to improve unRAID by my general incompetence :-)  

Eh... i would just show info if u use ports which wont work, like 80, 443, 445, 22, 23.

 

There are also ports above 1024 which could be reserved if you use X app. 

 

Actually, couldnt unraid just CHECK if that port is already used? ANd if so, show a warning.

17 minutes ago, nuhll said:

Eh... i would just show info if u use ports which wont work, like 80, 443, 445, 22, 23.

 

There are also ports above 1024 which could be reserved if you use X app. 

 

Actually, couldnt unraid just CHECK if that port is already used? ANd if so, show a warning.

 

You are illustrating the difficulty faced by any developer.  The perfect is the enemy of the good enough.  To create a warning is X minutes of work.  To design a foolproof method of determining if a port is in use, or will ever become in use, is like X times at least 2 orders of magnitude.  Now if we were getting flooded with support requests and email, saying, "WTF my ports don't work" then it might rise to the level of caring about it.  Everything's a tradeoff.

 

 

The TCP port number convention for well known ports was created to avoid port conflicts between services. Ideally people stick to this convention.

We can go as far as disallowing well known ports to either HTTP or HTTPS or simply give a recommendation warning if the user wants to do this.

 

Think of traffic rules. Crossing a red traffic light you can do, but it is not really recommended.

 

Checking for ports in use isn't foolproof at all, since it depends whether a service or application is started. If not it will give a conflict at a later stage.