How to change license?

I have a 50 user license I have been using on a Linux box. I now want to use that on a different system, for testing the Solaris release - so I have purchased a new 250 user license for the Linux system.

How do I get the license installed/changed on the Linux box now? Running the new ‘install.sh’ fails, as virtualmin itself is already installed.

Howdy Phil,

Sorry for the slow reply on this one. It came in while I was traveling, and I missed it while catching up (I guess now I’m catching up on catching up).

Changing licenses is a moderately clunky process, but you definitely don’t want to run install.sh again on an already installed system–that’s why it’s called install.sh and not “run-this-for-changes-or-updates-and-such.sh”. It can actually be dangerous to run install.sh on an already installed system. So don’t do that. :wink:

I’ve just switched your licenses for you in our database. So you can install the new (now 50) license on Solaris, and keep the old (now 250) license on the Linux box. Problem solved.

To make the Linux box pick up the new license details, browse to /virtual-server/licence.pl on the system. For example, I would hit:

https://www.virtualmin.com:10000/virtual-server/licence.pl

If you ever want to upgrade licenses in the future (if the shopping cart doesn’t yet have support–that support is coming soon) drop me a line, and we’ll get it taken care of manually.

Thanks Joe. Why does the serial numbers page show 0 domains and 0 servers used for each of my licenses?

It also seems that I cannot run virtualmin inside of a solaris zone, once it has been installed in the global zone? (I get an error saying ‘invalid serial number’) Do I need an additional license for each instance running inside of a zone??

We haven’t turned up the server and domain counts yet on Virtualmin.com. It’ll happen soon (we’re still in Early Adopter beta, ya know!).

We’re trying to figure out how to handle virtualized host licensing. It will require additional licenses, but they’ll be priced differently. We need to work on the license manager to be a bit smarter about that, and make those licenses available in the shop…BUT that’s not why you’re getting that error. I’m not sure what would cause that, as we also haven’t turned on server limits (we know how many servers you’re running on a given license, but the manager isn’t flagging or imposing restrictions yet). Are you sure the zone is able to make outgoing network connections?

I’m sure the zone can make outgoing connections, yes… it can ping virtualmin.com just fine.

The error displayed is:

A problem was detected with your Virtualmin licence :
An error occurred checking the licence : Missing serial number

And when I click the ‘Re-Check License Status’ button, I get:

… a problem was detected : An error occurred checking the licence : Missing serial number

Snooping the network, I see a call going out from the server to ‘software.virtualmin.com’ :

GET /cgi-bin/vlicence.cgi?id=39c3c162&serial= HTTP/1.0.

And the response:

ERR Missing serial number

So it is checking, but not finding/sending the serial number properly.

I do see what I believe is the proper serial number set as the value of "upuser" in the file /etc/webmin/webmin/config in the zone though…?

Oh, you don’t have a /etc/virtualmin-license file accessible within the zone.

Webmin’s configuration file has nothing to do with Virtualmin licensing.

OK thanks that was it.

You may note that when installing virtualmin on a system with pre-existing zones, that this file is not installed on the zone.

In fact installing it at all on a system with pre-existing zones is pretty much guaranteed to end up with a non-functioning virtualmin environment within the zone, without a lot of follow up manual tweaking…

Yes, Virtualmin isn’t really aware of Zones. We have a new product called VM2 (Virtualmin Machine Manager) that’s specifically for Zones (and Xens, and vservers, and EC2s) that knows how to spin up a Virtualmin on an existing system.

It’s launching really soon for CentOS 5 and Debian 4, and we’ll probably have a Solaris installer soon after.

Nonetheless, pre-existing Zones are probably never going to be friendly to Virtualmin being installed after the fact, since I think they pick up a lot of their stuff from the system on which they’re running. But I’m no Zones expert (I don’t even have a Solaris box handy–Jamie does all of the Solaris work on the servers that Sun gave him a while back for the Webmin Zones development work).

Cool - let me know if you need any Solaris beta testers for VM2…

What I would really love to see is a zone-aware virtualmin that runs out of the global zone, and sets up each virtual domain within it’s own zone. That would be way cool.

Howdy Joe

I installed virtualmin pro a while ago for different hardware.I am not really using just testing and understanding virtualmin before using in production server.I attempted to install on Centos5.0 and run the installation script .But it installed gpl version not pro version and i put license key but it end up with error.My first installation was fine .Is it related with license database if it is what should i do ?

Thank you very much

Joe wrote:

Howdy Phil,

Sorry for the slow reply on this one. It came in while I was traveling, and I missed it while catching up (I guess now I’m catching up on catching up).

Changing licenses is a moderately clunky process, but you definitely don’t want to run install.sh again on an already installed system–that’s why it’s called install.sh and not “run-this-for-changes-or-updates-and-such.sh”. It can actually be dangerous to run install.sh on an already installed system. So don’t do that. :wink:

I’ve just switched your licenses for you in our database. So you can install the new (now 50) license on Solaris, and keep the old (now 250) license on the Linux box. Problem solved.

To make the Linux box pick up the new license details, browse to /virtual-server/licence.pl on the system. For example, I would hit:

https://www.virtualmin.com:10000/virtual-server/licence.pl

If you ever want to upgrade licenses in the future (if the shopping cart doesn’t yet have support–that support is coming soon) drop me a line, and we’ll get it taken care of manually.

I attempted to install on Centos5.0 and run the installation script .But it installed gpl version not pro version and i put license key but it end up with error.

For the first problem, you used the GPL version of install.sh. To install Professional you need to download the correct install.sh for your license from http://www.virtualmin.com/serial/ I’ve removed the direct link to the GPL install.sh from the front page, and replaced it with a link to the download page, that explains where to get the Professional install.sh, as well as provides a link to the GPL install.sh.

For the failed upgrade, file a bug with the exact error you received, and we’ll get it fixed. Ideally, a GPL -> Pro system will now be identical to a freshly installed Pro system.