I’m working to integrate Webmin current version 2.401 and upgraded to 2.402 in my homelab. I’ve installed Webin on my Debian 12, Rocky 9 and Rocky 10 hosts. I can bring up each instance on the browser and log in individually, so accessibility is no issue. However, when “Broadcast for servers”, I only discover my Debian hosts. The Rocky 9/10 hosts are not discovered. The same result for “Scan for server” option.
The discovered Debian host and the Rocky hosts that are not discovered are Proxmox VMs. Not sure if that provides for some obstacles in network broadcasting/scanning. I do notice that from a Rocky VM performing discovery, only the Debian 12 VM is discovered not the standalone Debian 12 hosts.
Has anyone else dealt with this issue, have advise?
I’ve bumped into the cause. firewalld. When I turn it off, the Rocky instance is discoverable (actually found through the network scan feature). I’m not sure why this would matter since a firewall rule to allow port 10000 was entered and thus I was able to access Webmin directly from a browser.
Thanks. I just read that in the documentation. The setup.sh doesn’t add the firewalld rules (which I would think is appropriate). It also needs 10000/udp as well for discovery.
Installing Webmin does nothing to the system but install Webmin. It definitely does not touch the firewall. Is Webmin actually all you want? Virtualmin does modify the firewall and a bunch of other stuff when installed according to our documentation, and is what you want if you’re looking for a web hosting control panel. Webmin is a general purpose system administration tool, and doesn’t change anything unless/until you tell it to.
Also, you should never use the Webmin setup.sh on a system that has a good supported package manager. You should install Webmin using your package manager (dnf on EL distros, and apt on Debian/Ubuntu) according to the documentation on the Webmin site.