Hi folks!
LTDR: How to shake this annoying “Cloning a cloned machine is nicht permitted”?
Story so far. Very first try of CHR as Virtual box guest. Screwed config and roll back to snapshot. Generate New ID and try to renew. Now with this new lovely message and super low speed.
Have you tried transferring the license to a new id in your personal account?
if I understand the problem correctly…
At least there is a message now.
I lost 4 hours once trying to understand why my restored CHR was limited.
Hi, Sorry to reply to an old thread, but I can’t see anywhere else here where someone had this error?
I’ve never seen this before. Did Mikrotik start a new license check? Why am I getting this cloned not permitted?
I am trying to use a new paid P1 license.
There is no new issue with reusing cloned VM images with unique licenses, is there?
I started seeing this a number of weeks ago too. I’d like to be able to build a CHR on one host, get it working, then convert it to a template for deployment across multiple identical hosts. I tried cloning one that was working and, even after changing its system ID, I couldn’t register it with a new license (or transfer an existing one) because of the same error. I don’t recall having seen it before.
Are you trying to restore backup from another CHR? Are you trying to license a CHR that was used for free longer than 60 days?
yup - I’ve seen this CHR License Error many times. !!!
There is some pattern of restoring a clone from a clone from a clone that triggers it.
Once you get the message , just erase and delete the CHR and rebuild it from scratch and reapply the chr license.
It seems like it happens at the worst of times when you are replacing a hypervisor or crashed physical server both that runs a hypervisor ( VmWare and Proxmox ) during a late-night O-dark-30 when you are tired and just want to go home. It rather #isses me off when it happens.
IMO , I am guessing the Miktorik CHR ROS licensing software is soooooo aggressive that it will kill a CHR if it even thinks it’s a non-legitimized copy of a CHR. Possibly triggered from changing to many things at the same time such as disk , cpu and network cards all at the same time when restoring/moving to a different hypervisor about 3 or so times.
This issue / problem is one of the reasons I purchased extra spare CHR P-Unlimited licenses. I have a pool of ready to use CHR licenses I can use to activate/build a replacement CHR when it does what you are describing.
North Idaho Tom Jones
Is using an extra/different license actually any faster than simply blowing the original one away, spinning up a virgin one, and applying the original license back to it & restoring config from backup?
For me I had built the CHR in Proxmox using the raw image converted to qcow (as per MikroTik’s documentation). I had it check out a license (which was free, because it was new). Once I was happy with how it was configured and working on the first host, I migrated and/or cloned it to the second host. When I went to licensing to generate a new license for the cloned VM, it gave the error. Even after changing the system ID (so I could get a new license), it gave the error.
My workflow is to spin up the VM, ensure it’s working correctly, then clone it to all the other hosts. This has worked fine on VMware in the past, so I don’t know what extra step(s) I may have done in Proxmox to cause it to complain. I would happily buy licenses for them, but in this particular scenario, it wouldn’t even check in so I could assign a paid license to the newly generated system-ID.