In the old Apache server I had these modules active and I wonder if I should also activate them in Virtualmin. Especially proxy_http2 instead of proxy_http.
socache_shmcb, include, cgid, proxy_http2, sysenv, userdir, proxy_wstunnel
Furthermore, mod_sysenv is not even listed and needs to be installed.
Thanks in advance.
| SYSTEM INFORMATION | |
|---|---|
| OS type and version | Debian 12 |
| Webmin version | 2.105 |
| Virtualmin version | 7.10.0 |
| Related packages | Apache |
Up to you really if anything you use needs these modules obviously activate/install them. I see little point activating/installing modules you are never going to use just so it matches a previous setup
You’re right, but I was assuming that that was also a standard configuration.
Never activate or deactivate a module unless explicitly requested.
The Virtualmin installer activates what it needs for all of the configuration it will do in a default install (there are some other Virtualmin plugins that work with non-default modules, but you probably don’t want them at this point in history…old creaky stuff like mod_perl and mod_svn). Anything else is your business, not ours.
I would encourage you to read up on what a module does before enabling it (same goes for packages when installing, services when enabling them, configuration options when changing them, etc.).
This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.