I assume this is because ports below 1024 can only be bound to by root?
Anyone done this at all?
Want to get away from having to use port 28080/28443 at the end of the URL.
Thanks Craig
This thread was automatically locked due to age.
I assume this is because ports below 1024 can only be bound to by root?
Anyone done this at all?
Want to get away from having to use port 28080/28443 at the end of the URL.
Thanks Craig
Hi Craig,
It looks like you can change the port in: Local Services->HTTPD (RPC/UI)->Configure End User UI
Mine has values of hostname:port
However the docs say this needs to be greater then 1024:
To set the hostname and port of the server that is running the End User Web Interface:
1. In the Background Services table on the Local Services tab, click HTTPD (RPC/UI), and then on the sidebar, click Configure HTTPD Service.
The Configure HTTPD Service page is displayed.
2. Change the text boxes in the Configuration table as required.
The text boxes are:
* Hostname: The hostname must be a fully qualified domain name.
* Port: The default is 28080. This can be changed to any port number greater than 1024.
3. Once you have finished making changes, click Save.
For me, I would make a link on my Intranet that points to the EUI and then give that link to my clients.
From a purely theoretical standpoint, this is just apache and one could probably modify things at the httpd.conf level. I personally wouldn't because where you would likely run into issues is that the init scipt for puremessage checks to see if the user running the command is root or pmx. If it's root, then it gives up it's priveleges. I'm pretty sure this happens before the http daemon is started. This could also royally fubar your puremessage installation...
Another thought is if the EUI has a firewall of some kind sitting between it and your clients. You may be able to use Port Translation to redirect request for hostname:80 -> otherhostname:28080
Erric