Thanks for the extra info.
Sounds to me as if you box is not connected to the internet!
I assume that some basic checks have been done. When you say it works on other network it seems to be a network connectivity issue rather than Virtualmin. Can the box even do a simple apt install? (I’m not a CentOS user)
I assume the IP pool is not blacklisted. (I am pretty sure that Virtualmin would not blacklist any IP - I cannot see any reason to do that)
I have only had experience of installing on virgin clean boxes not on using any IP pooling. Though I can vaguely understand why that might interfere with Virtualmin handling of IP once it has loaded - I cannot understand why you cannot even load it. I assume that there are no errors with the above commands - as the script is pretty good at throwing messages about problems during install.
I am also a little confused as you implied that Virtualmin has loaded ok on other boxes (presumably in the same IP pool) Is it something about the management of the pool?
We run fail2ban or sshguard on all of our servers. So, it’s possible attacks (i.e. attempts to login via ssh) coming from an IP would lead to it being blocked, but we wouldn’t have blocked a whole network block, AFAIK (I mean, I don’t know how that’d happen unless our provider did it).
That IP doesn’t show up in our fail2ban log for the repo server, nor in the firewall rules, so that’s not the case here.
Without the actual IP, I can’t really do much network testing to see where the disconnect is happening.
Hello there, I can confirm this.
We cannot connect to https://software.virtualmin.com from any of our systems, either. The error message shown in the browser is ERR_SSL_PROTOCOL_ERROR (in latest Chrome), also apt can’t connect.