Stuck on an old version of Virtualmin


I’ve been trying to get Let’s Encrypt certs set up for my sites but the tab doesn’t appear in ‘Manage SSL Certificates’. It would appear the reason is I’m running an old version of Virtualmin (4.05.gpl to be precise).

I read this old thread ( but my server is running CentOS 6 so a lot of it doesn’t apply. Unfortunately I don’t remember exactly how I installed Webmin/Virtualmin as it was a few years ago but I remember having problems and only when it was too late, realising there was apparently an easier way (the install script).

So VM isn’t installed via yum and I can’t see anywhere within Webmin to update it. Can anyone help?

BTW, Webmin itself is up to date (1.840).



If you’ve got a tarball installation, you can grab the wbm module package from

It’s also possible to setup Webmin to update using wbm modules from the standard repo or from another repo (I think). I haven’t used that feature in well over a decade (we’ve been distributing RPMs in yum repos for the entire existence of Virtualmin, and there’s never any reason to use wbm on a CentOS or Debian/Ubuntu system), though, so I don’t have much to offer in terms of how to set it up. It’s somewhere in Webmin->Webmin->Webmin Configuration, maybe. (Certainly in the Webmin->Webmin category.)

Thanks for this. I’ll have a look at updating via Webmin, but is there any way of switching to using yum, or is it all entwined in using the installer script?

It is not entwined with the install script, at all. That’s just the easiest way to setup a Virtualmin system, and it does it using the best way to install software (which is the native package manager for your OS).

We try to make the packages able to install over tarball installations, but it gets so little testing that I would not recommend it on a production system. I think I’d recommend you stick with what you have until you can install on a fresh system and migrate to it. Just be sure not to do things the hard way in the future! You definitely don’t want to run the install script on a production system; that would be disastrous, especially for a manually installed system that could be completely different from the way our installer sets things up.

Both Webmin and the modules can be upgraded automatically from the wbm repo; it just needs to be configured (though again, I dunno how…you’ll need to poke around in the Webmin configuration pages). So, RPM or deb with yum or apt would be better, but it aint a horrible situation to have a tarball install.

If you do want to brave changing to RPM/yum, you’d want to install the latest virtualmin-release for your distro (browse through to find that), and then use yum to install Webmin and all of the Virtualmin modules you use. And, if you do, please backup your /etc/webmin directory, just in case anything gets overwritten during the install. (Also, do not install the virtualmin-base package!..that performs configuration steps…it’d do all the same stuff as running the does, which would be potentially disastrous).

Thanks. As you say, I think I’ll stick with the current setup until I move servers. I managed to get the new version installed with no problems so I’ll update it manually periodically.

For reference if anyone else has this issue, this is what I did:

  1. Go to Webmin > Webmin Configuration > Webmin Modules
  2. Choose Install from ftp or http URL
  3. Copy the Virtualmin module URL from this page:
  4. Install Module