Minecraft verwalten · 6 min read
Start, stop and restart Minecraft server
For a normal start or stop, use dhosty to control your Minecraft instance. Before a scheduled stop you inform the players and then check in the console to see if the process is finished. On the next start, you will register yourself. If you need an instance, you will find the offers under [Minecraft Server].](/minecraft-server/).
Hold the occasion before maintenance
Determine why you want to stop the server. A change to the modpack, a change to the Minecraft version and a backup set different requirements. Write down the active version and the changes you want to make. In addition, when you update, you will notice the last working version. This gives you a starting point if the server starts with an error message after maintenance.
Plan a short maintenance window and let the group know in time. Name the start and what players should do, for example, to complete their ongoing activities and leave the game. If you call it an expected duration, you can update it with new insights. On a private server, usually a message in the shared channel is enough. Check before stopping whether someone is still online and announce the final step briefly.
Stop the server ordered
In the dhosty panel, select the affected game server and trigger the normal stop. If you work directly via the authorized Minecraft console instead, use the regular server command stop. Both should give the server the opportunity to save the world and player data. Use status and protocol to check whether the process is complete before you edit files or trigger the start.
Some worlds need longer when ending, especially when many data are stored. Watch progress and distinguish active storage from a process that no longer delivers new messages. Multiple clicks can mask the cause. If a persistent problem occurs, record the time of the stop attempt and the last console messages. Forced exit carries a risk of unstorped changes and is the last step in a fixed process.
Backup and changes in meaningful order
Secure the last working world with the corresponding configuration before a larger version change. Check which files your backup method includes. A world copy alone may not contain the server settings or all plugins. To return, you also need the appropriate Minecraft version and, in case of a modpack, the versions of the extensions installed at that time. Note this information together with the backup.
Make related changes in small groups. If you update mods at the same time, change settings, and change the world, it's harder to assign a start error. After each group, record what you've changed. If you're maintaining a damaged world or a faulty extension, first check a separate copy if possible. The memory level you last confirmed as working in the game is your reference point for recovery.
Start and verify the operation
Release the start once and watch the protocol. World generation, new extensions or a version migration can lead to a longer start than usual. Once the server has completed its initialization, connect to the address of your instance. Use the same client version as the rest of the group. A status in the panel is helpful, you confirm the successful game operation by an actual accession.
Test the affected part after changes. If you have updated a plugin, try its most important function. If you have a world from a backup, check known places and inventories. Check on a private server whether the approval list works as expected. If the changes work, inform the group about the release and, if necessary, the new client or pack version. Hold on to the tests you have performed so that the next maintenance can build on them.
Limit start error without restart loop
If the server stops immediately, read the messages of the failed start. Indications of a specific extension, an invalid setting or an unsupported version give you a specific track. Compare the message to your list of recent changes. Set a single change as far as possible and check again. If the process runs clean, but the accession fails, compare the address used, the Minecraft version and the approval list.
In case of a recurring error, date and time, instance name, game version and a short log extract help. Specify whether you have made an update or a file change before the problem. This can be used to determine whether the error occurs during startup, loading the world or only when connecting.](/hilfe/) You can get to the contact point. Clean the extract for login data and other private information before copying it into a ticket.
When a restart is worth it
Restarting is useful if a change only takes effect after reloading or if you want to check whether the instance is running up cleanly after maintenance. Treat it as a scheduled interruption with final exam. If an application repeatedly hangs, secure the logs before the next restart and record the trigger. This gives you a basis to narrow down the error and select the correct correction.
For a regularly visited world, a short maintenance protocol is worthwhile. Capture the beginning, end, occasion, active version and test result. If a malfunction is repeated after similar changes, it is easier to compare the cases. If a longer repair is done, a short status message keeps the community informed. You give a new release as soon as the accession and the maintenance-affected functions are tested in the game.
Frequently asked questions
Can I stop the server while playing?
Technically, this is possible. Plan the stop as far as possible at a quiet time, announce it and let the players complete running actions. Then use the ordered stop so that the server can store its data.
How do I know that the server is really out?
Check the instance status and the last messages in the log. Wait until the process is finished before you exchange the world files or start them directly again.
What do I do if it doesn't start after an update?
Secure the first meaningful error message and compare the most recently changed files and versions. Step back to the known working combination. Make sure that the update has changed the format of the world.
Is rebooting the same as resetting the world?
A regular restart will end the process and restart it with the existing configuration. A world will only be created or replaced when the corresponding configuration or world folder has changed.