Move to another server

Migrate a d0pe install to a new box with its data — and rebind the license.

You'll move a d0pe install when you outgrow the disk, change datacenter or provider, or consolidate boxes. It's a backup, a restore, a license rebind, and a DNS change — in that order. Because the license is bound to the machine, the rebind step is the one people forget.

Steps

• On the old server: ./backup.sh, then copy the archive to the new server.
• On the new server: install d0pe (the one-line installer), then ./restore.sh <archive>.
• Stop the old server completely: docker compose down. This is required — two live copies trip clone detection and suspend the license.
• Rebind the license: on the billing admin, open Licenses → your license → Rebind. That clears the old hardware binding so the new server binds on its next activation.
• Re-point DNS: update your domain's A-record to the new server's IP. Changes take effect within a few minutes to a few hours.

Why the rebind

Your license is bound to the first machine's hardware id, and a heartbeat from a different machine is rejected on purpose (it's what stops a copied disk from running two instances). A migration is legitimate, so Rebind clears the binding for you — do it after the old server is down, so the new one binds cleanly.

Restore moves the data. Rebind moves the license. Do both, or the new box comes up read-only.