Configuring Firewalld freezes

SYSTEM INFORMATION
OS type and version Red Hat 8.5.0-20
Webmin version 2.105
Virtualmin version 7.9.0
Related packages SUGGESTED

Good day,

I am installing Virtualmin on a server that is managed by my organization’s IT department (and probably has some firewall settings that I do not know all the details of). All woks well up to “Phase 4 of 4: Configuration”, specifically “[7/21] Configuring Firewalld”. At this point the install script simply freezes. All the steps above have green checks, but the three blue loading bars stopped moving. There are no error logs generated. Any advice on how I can trouble shoot this please?

Regards, JC

I see now that I can no longer SSH into the server, so some firewall rules were probably triggered. I will first follow up with my IT department and then revisit this post once resolved.

So that is not a clean OS install !
The box (OS) has had a firewall installed - Virtualmin attempts to install and configure Firewalld which it is in conflict with something your IT department has pre installed.

You need to find out what firewall and why. (ie is it really needed before you install Virtualmin or can Firewalld be set up with the those settings - it probably can - after the installation.

Is this being used on intranet? (you are possibly going to have future issues)

1 Like

Thank you, much appreciated. I will follow up with them. The current plan is to only have the server visible from within our network, yes. If this does not work we will have to look at other options, one of which is to make the server visible from outside the network as well. What issues to you anticipate exactly?

Webmin/Virtualmin has multiple cron jobs that are set up (there may well be other processes) that checks the package management of the OS to look for and make system updates - although optional and could be ignored inside Virtualmin eventually they will be a problem unless you/your IT manage this from root access. (do not forget that there are also updates to the software itself they will all require internet access or the whole system will rapidly become stale.

It is not that they are insurmountable - just that it is extra work.
For example how are you going to maintain certs? but again do you even need external certs for an intranet?

Also what about DNS ?

I am sure there are many other potential issues I have not thought of.

I have only set up one VS as an intranet but it has internet access (albeit slow/intermittent) and it requires pretty constant monitoring.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.