EDIT I wanted to add to this thread, since it contains very dangerous advice, and folks are finding it in the archives and acting on it. You should not follow this advice if you aren’t actually wanting to start over. It will break stuff and delete data. It is not intended as a general purpose process for upgrading from GPL to Professional (again, if you use the upgrade form within Virtualmin and it fails, file a ticket: it’s a bug and we’ll fix it or help work around it). Please don’t follow this advice unless you really want to start fresh (probably losing all data in Virtualmin).
So, the first error happens when Virtualmin is not installed using install.sh, but using RPMs. So, a manual installation using RPM packages, which is an odd choice (mostly because it’s really time consuming, and not a lot of folks have all the knowledge necessary to do it without a lot of reading and experimentation).
The fix is to setup the yum repository for Virtualmin GPL before upgrading to Professional.
But, since you’re just starting out, we like the idea of starting from scratch (where “starting from scratch” probably just means getting rid of the Virtualmin and Webmin packages, and any Virtualmin-related yum configuration, and running install.sh from the serial numbers page).
So, I go digging on the server, yep, its not there, and as a matter of fact, why should it be? Why am I trying to install the "GPL" version?
Because you missed something when cleaning up the old installation. 
So, I’m going to rattle off some facts in no particular order, which I believe will make all things clearer:
-
install.sh is for installation only. It cannot upgrade from GPL to Professional. It cannot (without some manual tweaking) convert a manual installation from other sources into a "proper" installation. It cannot fix a broken installation. It is a dumb shell script that looks at the system, makes a ton of assumptions based on the bits of knowledge it has (OS, version, architecture), and then uses yum or apt-get to install the necessary packages. It only knows how to do useful things on a freshly installed OS. Anything else just confuses the poor thing.
-
Systems installed without install.sh are in a state that we cannot predict. You could have configured it in any of millions of possible permutations. Webmin/Virtualmin are smarter than the script, and are working with a bit more knowledge of the system (they know more than OS, version and architecture, anyway), but they still can’t deal with every possible permutation. It tries a little harder, but you probably have to help it along, if you did anything out of the ordinary.
-
yum is the key to everything. Installation, upgrades, and updates. So, the bit at the end where you’ve got GPL being installed instead of Professional…that’s because I guess you’ve added yum configuraton for the GPL repository, and that repo is being used instead of the Professional repo (it’s probably preventing setup of the Pro repo at all, since there’s already a virtualmin-release package installed).
-
We can fix this for you, at no cost. Just drop me an email and I’ll drop in and straighten things out for you.
If you wanted to fix it yourself, I would suggest the following:
Uninstall virtualmin-release (it’s probably where the bum yum repo configuration is coming from):
rpm -e virtualmin-release
Make sure it’s actually cleaned up:
rm /etc/yum.repos.d/virtualmin.repo
If you added yum configuration somewhere in one of your earlier steps, undo it. You don’t want a bunch of crud floating around in your yum configuration. Remember: yum is the key to everything.
And then, make sure you have the Virtualmin Professional install.sh with a valid key and serial number. Look inside install.sh for the SERIAL and KEY variables. You can use extended grep like so:
egrep "(KEY=|SERIAL=)" install.sh
(Note: Careful not to post any copypasta with license details in it to the forums.)
Just for fun, you could also run the uninstall option of the install.sh script.
/bin/sh install.sh --uninstall
Which will rip out all of the Virtualmin specific packages, making for a pretty close to fresh start.
If anything goes wrong, the offer stands for us dropping in and straightening things out for you (at the end of the install.sh run, if it fails, it’ll ask you to open a ticket and make this offer to you).
