Cloning takes an existing server and stamps out a brand-new, separate one that's a copy of it — same files, same setup, its own address. It's how you spin up a second network node, a test copy of your live server, or a fresh start from a configuration you've already dialled in. You start it from the Settings page, under Operations. Cloning is a premium feature.
| At a glance | |
|---|---|
| You need | A premium server to clone from |
| Plan | Premium |
| Time | A few minutes while files copy |
What cloning creates
A clone is a whole new server — its own entry in your server list, its own address, running alongside the original. The original is untouched. This is different from cloning an instance, which makes a second setup inside one server that shares its single port. A server clone is genuinely separate and can run at the same time as the source.
What copies — and what doesn't
This is the part to get right before you clone.
| Copies to the new server | Does not copy |
|---|---|
| All files, worlds, and plugins/mods | The IP address and port (a new allocation) |
| The application, version, and startup command | The subdomain (a new auto-generated one) |
| Startup variables and settings | Managed databases |
| Resource and limit settings | Sub-users |
| Backups | |
| Reverse-proxy and custom domains |
In short: the server itself — everything in its files and configuration — comes across faithfully. The things that are unique to a server — its network address, its subdomain, its databases, its team — are created fresh or left behind, because two servers can't share them.
⚠️ Heads up: Because databases aren't cloned, an app or plugin that expects a database will start against an empty one. If your clone needs the data too, add a database to the clone and import a dump. Anything reading a connection string from a variable will need it repointed at the new database.
The plan cost
A clone is a real, additional server, so it uses real, additional capacity — cloning is not free even though the action has no separate price tag:
- Cloning a plan (billing) server adds the new server to your subscription and charges a pro-rated amount for the rest of the current billing period, so the second server is on the same plan.
- Cloning within your account's resources consumes a new server slot: the clone's RAM and disk have to fit within your remaining plan capacity. If you don't have the headroom, free some up first (or upgrade).
Either way, you end up with two servers to manage — plan for the second one existing, not just appearing for a moment.
How it goes
- Open Settings → Operations → Clone Server and give the new server a name.
- Confirm. The panel reserves a new address and subdomain and starts copying.
- Watch the progress bar — it shows files copying across (
X / Y files) in real time. - When it reaches 100%, the panel drops you into the new server's console. It doesn't auto-start, so review it, then start it when you're ready.
The whole thing runs in the background; you can leave the page and come back.
Good reasons to clone
- A staging copy of your live server — clone production, break things on the copy, and leave the real one alone. (For a lighter version of this that lives on one server, instances do it without a second server.)
- A second server from a proven base — you've spent hours configuring one server; clone it as the starting point for the next region or the next community.
- A safety fork before a risky change — clone, test the scary upgrade on the copy, and only touch the original once you're sure.
Troubleshooting
- The clone option is locked — it's premium; the source server needs a premium plan.
- "Not enough resources" — the clone's RAM/disk doesn't fit your remaining plan capacity. Delete or downsize something, or upgrade, then try again.
- The clone's app can't connect to its database — databases don't clone. Add one to the new server and point its connection variable at it.
- Players can't reach the clone at the old address — it has its own new IP and subdomain by design; share the clone's address from its Network page.