Skip to main content

​
Before you start

If you want multiple interchangeable servers or automatic scaling, use Server Groups instead. Connect at least one serverhost and make sure it has enough memory for your server.
SimpleCloud does not move or back up a persistent server’s files. Back up worlds and other important files yourself.

​
Create a persistent server

1

Open Persistent Servers

In the dashboard, open Persistent Servers and click Add Server.
2

Choose the server

Enter a name, choose Server or Proxy, and select the serverhost that will run it.Names may contain up to 100 ASCII letters, digits, underscores, and hyphens ([A-Za-z0-9_-]). They are unique within the network regardless of capitalization, so Survival-1 and survival-1 count as the same name.
3

Choose the software

Select the server software, Minecraft version, and Java version.If the software is not listed, choose Custom and fill in the required fields.
4

Set resources

Choose the memory and maximum player count. Proxies also require a starting port.
5

Create the server

Review the configuration and click Create Server. SimpleCloud starts it automatically unless you disabled Activate on creation.
With Activate on creation enabled, the server reaches Available and its console shows the startup logs.

​
Start and manage the server

Open the server in the dashboard to view its status, console, and files. Use its actions menu to enable, disable, or restart it.
  • Enable tells SimpleCloud to keep the server running. If it stops, SimpleCloud starts it again.
  • Disable stops the server and leaves it stopped until you enable it again.
  • Restart stops and starts the server without deleting its files.
You can also enable or disable the server with the Active switch in Settings. Save any other settings you change. If a change affects how the server starts, restart it to apply the new configuration. Use the main Settings page for resources and the Blueprint page for software and startup configuration. The Deployment page changes the assigned serverhost; follow the migration steps below before using it. Use the Files tab to manage its world, configuration, and plugins. These files stay in place when you restart or disable the server.

​
Move the server to another serverhost

Changing the assigned serverhost does not move the server’s files. Back up and copy them before starting the server on the new host.
1

Disable the server

Disable the persistent server and wait for it to stop.
2

Copy its files

The path running/persistent/<server-name> is relative to the SimpleCloud installation on each host. Copy the complete directory while the server is disabled. For example, run rsync from the old host and replace the account, host, installation path, and server name:
Run the copy as the account that owns the SimpleCloud installation so file ownership and permissions remain usable on the destination.
3

Check the destination

On the new serverhost, run ls -ld /srv/simplecloud/running/persistent/survival-1 and inspect several files below it. Confirm that the SimpleCloud service account can read and write the copied directory.
4

Change the serverhost

Open Settings > Deployment, select the new serverhost, and confirm the change.
5

Enable and verify

Enable the server, join it, and confirm that its worlds and configuration are present. Keep the old copy until this check succeeds.
Starting the server on the new serverhost before copying its files can create a new, empty server directory.

​
Delete a persistent server

Open Settings > Danger Zone and follow the deletion prompts. SimpleCloud stops the server if necessary and removes its configuration and any associated blueprint. The server files remain on the serverhost.

​
Troubleshooting

Confirm that the server is enabled, its serverhost is connected, and the host has enough free memory. Then check the server’s console for the error.
Disable the server. Copy its running/persistent/<server-name> directory from the old serverhost to the new one, then enable it and check the world again.
Save the change and restart the server. Check its console if the problem continues.