Howdy all,
I believe we’re ready to call the new installer beta. It works for us for GPL and Pro installs in testing on Rocky/Alma 8, Debian 11, and Ubuntu 22.04. It is still changing rapidly, but in minor ways at this point. A system installed with this will probably be pretty close to what you’ll get once we call it stable, assuming it works for you.
Please do not treat this like a stable release. If you’re using it on a system that will be put into production, you must test thoroughly first. There will be quirks. Our testing has been limited to confirming it installs fully and runs through all configuration steps correctly. It has had almost no functionality testing beyond that, and these new distro versions (Debian 11 and Ubuntu 22.04) are completely untested beyond installation.
If you are deploying to a distro supported by Virtualmin 6 installer, you should keep using that one for now. If you use this new installer, you are a beta tester, you are not a user. We will try to help with problems, but sometimes our answer will be to “start over” after we reproduce and fix whatever problems you report. Our focus now is on a few more days of a rapid text/fix cycle until we’re happy with it, and helping people use this on a production system is not amenable to going fast, so don’t ask us to do that.
Here’s the link for Virtualmin 7 beta install script.
It’ll probably change regularly during the final few days of development and testing, so be sure to grab the latest before an install.
Once again: If you are not looking to be a beta tester, you should not be using this installer. Install using the Virtualmin 6 installer on a Grade A supported OS.
One other heads up: We’ve found during our testing that Vultr instances in many regions permanently lose network connectivity when Firewalld starts, even a reboot does not restore it. We have no clue why this is so. It simply doesn’t make sense. But, it’s a thing you should be aware of. If you’re using Vultr, you may lose network connectivity during install at the firewalld step. We don’t have a solution or a workaround for this, but we’ve reported it to the Vultr folks. It isn’t us; the firewalld package installation all by itself breaks connectivity at least on Ubuntu and Debian but maybe only in some Vultr instance locations. So, until that’s understood or fixed upstream, we don’t have any ideas. Don’t waste your time or ours with this problem (unless you figure it out and want to tell us about it). It is known, but again, we don’t have solutions and I’m not inclined to workaround a bizarre behavior like this. Use a different provider (we’ve tested at Linode and on local VMs without issue) or try a different location (I have, in the past, been able to make it work on Vultr in some locations, but not others…Dallas consistently fails, Miami worked for me today, I have no clue wtf is going on). If you see this behavior at providers other than Vultr, we do want to know about it, though. It will look like the install freezes during either the “Installing dependencies and system packages” step (on deb-based distros) or the
“Configuring Firewalld” step (on RHEL-based distros).
No changelog or release notes yet. If you’re curious all of the installer and related packages are on our github, so you can see the commit history. Big ones are:
GitHub - virtualmin/virtualmin-install: Shell script to perform a Virtualmin GPL or Professional installation - The install script
GitHub - virtualmin/Virtualmin-Config: A modern rewrite of the Virtualmin postinstall configuration script - The configuration system (called by the install script for Phase 3 of the installation)
Cheers,
Joe
