I have my SparkBox installed in a Virtual Proxmox VM. I recently created a unique clone in Proxmox to test some stuff. I noticed when I released the License off my Clone Testing machine, it also released the license for my Production sparkbox. Is there a way to trigger a new identifier for my clone machine?
6 replies
Chris wrote:
Thanks for flagging this — I can see why it's concerning, especially with production affected. I can't verify a supported way to generate a new installation identifier for a clone, so please don't release the license again or change/reset installation files; the clone may share copied activation state, but that's only a possibility, not confirmed. I've recorded this for investigation. As the next check, what SparkBox versions are installed on the production VM and the clone? Please don't post a license key or identifier here.
Leo20 wrote:
Thank you for recording this concern. Prod: Current version v1.6.935 Clone: Current version v1.6.952
Chris wrote:
Thanks, that confirms the versions differ: production is on 1.6.935 and the clone is on 1.6.952. That difference alone doesn't explain why releasing one removed the other's license. A full VM copy made after SparkBox was installed could copy its saved activation identity, making both VMs appear as the same install; I can't confirm that's what happened here. Please don't release either license again or reset installation files. Was the clone made from a full snapshot/copy of production after SparkBox was installed? No key or identifier needed.
Leo20 wrote:
Yes it was made from a snapshot/copy so identical VM, with unique networking mac and hostname details changed with sudo hostnamectl set-hostname new-hostname and updating sudo nano /etc/hosts - otherwise identical copy of Production sparkbox.
Chris wrote:
Thanks, that confirms the clone was copied after SparkBox was installed. It may have inherited the same saved SparkBox installation identity; changing its hostname and network MAC does not by itself confirm that identity is different. Please don't release either activation again for now. As one check, are production and the clone currently showing an active or inactive license? Please share only those statuses, not a key or identifier.
Chris wrote:
I found the cause, and there is a clean way out. Each SparkBox keeps its install ID in its settings file, with a backup copy in its state folder. A Proxmox clone copies the whole disk, so your clone carries production's ID, and the licence server saw the two VMs as one install. Releasing the licence on the clone freed that one shared slot, which is the slot production was using. Nothing on production was damaged. 1. Production: open Settings → General → License and activate again with your key and the email you bought it with. It takes its slot back. 2. Clone only — run these on the clone, never on production. Give it its own machine ID, clear the copied install ID, and let SparkBox make a new one: - sudo rm /etc/machine-id && sudo systemd-machine-id-setup - sudo sed -i '/^SBINSTALLID=/d' /opt/sparkbox/.env && sudo rm -f /opt/sparkbox/state/install-id - sudo sparkbox up Then activate the clone in its own Settings → General → License with the same key and email. It now uses its own slot (one key covers up to 3 boxes), and releasing it later frees only the clone. The clone may also get a different network address after its next reboot, since its machine ID changed. To confirm the two are now different, run sudo grep '^SBINSTALLID=' /opt/sparkbox/.env | cut -c15-22 on each VM and compare them yourself — no need to post them. I've also passed on that a cloned box should get its own ID by itself.