How to delete a server on Schokr safely
Delete an Schokr server without losing anything you need: save your files, check snapshots and free its resources for other servers.
Updated · 2 min read
Deleting a server removes it and its files permanently, and gives its memory, CPU, disk and server slot back to your team's pool. Save anything you want to keep before you delete.
Before you delete
- Stop the server so files are not being written while you save them.
- Download what you need. In the file manager, archive the important folders (worlds, configs, databases, your bot's code) and download the archive. See archiving files.
- Do not rely on snapshots or backups. They belong to the server, so plan as if they will be deleted with it.
- Copy settings you might reuse, such as Startup variables and the template you used.
- Tell your players or users if the server is public.
- Rotate secrets you no longer need, such as a bot token, if you are retiring the bot.
Delete the server
- Open the server in the console.
- Go to the Settings section.
- Choose to delete the server and confirm.
Deletion cannot be undone. If you are only freeing resources for a while, consider lowering this server's resources instead of deleting it.
After deleting
- The server's memory, CPU, disk and slot return to your team's pool right away.
- Extra port allocations and snapshot slots you bought with credits were for that server, so think twice before deleting a server you have invested credits in.
- Your port allocation is released, so the address will stop working. If you used your own domain, update or remove the DNS records.
Alternatives to deleting
| Goal | Better option |
|---|---|
| Start fresh with the same template | Delete the files you do not need, or reinstall from Settings if offered |
| Need more resources elsewhere | Lower this server's resources |
| Switch to a different template | Download files, create the new server, then delete this one |
| Move to another location | See choosing a location |
Permissions
Deleting is a powerful action. Keep the settings permission that allows it limited to owners and trusted admins. See team roles and permissions.