It appears one cannot use port 1 as the access point to Web/VirtualMin (i.e. box.website.com:1) and attempting to do so kills VirtualMin. Specifically, after moving my new staging server to port 2, I wanted to move my live site to port 1 and my “lab” (experimental server) to port 3.
Thanks for that…it’s amazing how much damage a bit of courage and a lot of stupidity can cause lol. Is port 11 ok for this intended use, instead? I don’t know which of Yes/Unofficial/Assigned/No/Reserved are open for my use on your Wiki page.
Either way, I’m still down.
I’ve modified miniserv.conf to “port=11” on line 1 and saved the file.
I’ve added port 11 to FirewallD: sudo firewall-cmd --zone=public --add-port=11/tcp --permanent;
There is an official list of ports as used by different services. I wouldn’t put my nose in the first 1000. If you want to set a port for Webmin then somewhere as far as possible up to 65535. Obviously it can be scanned with nmap, but this can also be blocked by an IDS. As far as I’m concerned, in 10 years of Webmin I haven’t changed the default port. Administrators have the right to start the webmin service while working in the interface and then close the service. If the servers restart, the service is by default stopped
One more thing, if you set webmin service to listen on port 1 and a bot finds it out, it attacks your login form and you have to take protective measures. As in the case of moving the SSH port from 22 somewhere as far as possible, so here. If you set it to port 51237 when nmap is scanning the server, you can detect it and block the IP with an IDS.