These forums are locked and archived, but all topics have been migrated to the new forum. You can search for this topic on the new forum: Search for License Problems with Pro on the new forum.
Web Hosting and Cloud Computing Control Panels
I'll point that out to Joe so he can take a look.
It's a soft error, it's not going to prevent you from doing anything, and only the administrative user can see it.
In regards to the spelling of "licenced" -- that's the British/Australian way of spelling that. While Jamie, the author of Webmin/Virtualmin now resides in California, I believe he was born in Australia. Some of the spellings throughout Virtualmin have a similar Australian accent -- I've also seen "organisation", for example (which in the US is spelled as "organization").
Think of all that as part of Virtualmin's charm :-)
Anyhow, I'll email Joe about your license issue,
-Eric
<b>andreychek wrote:</b>
<div class='quote'>I'll point that out to Joe so he can take a look.
It's a soft error, it's not going to prevent you from doing anything, and only the administrative user can see it.</div>
Thanks. I'm glad it won't stop it from working. That was my main concern.
<div class='quote'>In regards to the spelling of "licenced" -- that's the British/Australian way of spelling that. While Jamie, the author of Webmin/Virtualmin now resides in California, I believe he was born in Australia. Some of the spellings throughout Virtualmin have a similar Australian accent -- I've also seen "organisation", for example (which in the US is spelled as "organization").
Think of all that as part of Virtualmin's charm :-)
Anyhow, I'll email Joe about your license issue,
-Eric</div>
Well that makes sense then. :-) Apparently your site search is in US English. ;-)
You've got an email Joe.
<div class='quote'>The license manager generates a host ID each time it is run...if the system changes hostname, IP address, or hardware, the host ID can change (there are three algorithms for determining the host ID, so it could involve any or all of those things, though it's almost always the same algorithm determining the ID for a particular system).</div>
Makes sense then. I assumed it was tied to the hostname somehow. I did change the name after I installed Virtualmin.
Up to 11 hosts now. Seems to increase each day.
Got it figured out. I uploaded a new version of install.sh a few days ago to add support for FreeBSD 7.1, and I forgot to reset the SERIAL/KEY variables to their template form...so everybody is installing using my development license. Obviously, this is a problem. ;-)
You can fix it with:
virtualmin change-license --serial SERIAL --key KEY
Where SERIAL and KEY should be replaced with the actual serial number and key from the serial numbers page here at Virtualmin.com (which is not effected by this bug).
I've also corrected this in the install script.
Apologies for the inconvenience. That was really dumb of me (it's been so long since I've rolled an update to install.sh that I forgot the steps involved).
--
Check out the forum guidelines!
Oops. That should be change-licence with the British spelling of licence:
virtualmin change-licence --serial SERIAL --key KEY
--
Check out the forum guidelines!
That worked Joe. Thanks.
Could you email me (joe@virtualmin.com) with the serial number or the username used to purchase the license, so I can look it up? Your account has no licenses associated with it.
And, I'll add a few comments just in case anyone else is searching the forums looking for this particular error message:
The license manager generates a host ID each time it is run...if the system changes hostname, IP address, or hardware, the host ID can change (there are three algorithms for determining the host ID, so it could involve any or all of those things, though it's almost always the same algorithm determining the ID for a particular system). If the system goes through a lot of changes, or even if the network is offline during one of the license manager runs, it can look like a lot of different systems. If things settle down for a few days, the error will clear on its own and nobody at Virtualmin will ever hear about it (we're not nosy, and we explicitly allow folks to run additional servers on one license during migrations and for backup purposes).
If it doesn't clear after a few days, you should ping us so we can help you track down the source of the trouble--it could also be a situation where the license information has been compromised (maybe accidentally posted in a forum post, or in a non-private ticket in the tracker) and is being abused. In those cases, we'll cancel the license and issue a new one, and walk you through the simple process of changing the license on your system (it's a single command).
It's never a reason to be alarmed, as long as you're using the license in good faith. It doesn't hinder your use of Virtualmin, will clear on its own in a few days, and we will always get in touch with you via email before taking any action that would impede your use of the product (such as if we suspect the license has been compromised, we'll let you know in advance of killing the old one).
--
Check out the forum guidelines!
Oh, and the spelling issue...yeah, Jamie and I have been at war for years on that one. Wacky British English. But, I think I'm going to build a tool to make an extra translation for Webmin/Virtualmin/Usermin so we can provide a US English language option. It'd be pretty trivial to implement, I think, and would only require a database of English words and their proper American equivalents. ;-)
I'll ping Jamie about that today.
--
Check out the forum guidelines!