Restart after a change
- Tell players the server is restarting and make a backup before a version, loader or mod change.
- Use Stop in the panel and wait for the process to exit before changing files. Use Start after the edit; avoid Force Stop unless a normal stop is stuck.
- Watch the console until startup completes, then have one player verify the world and connection.
Mods, plugins and data packs
- Choose Vanilla, Paper/Purpur, or Fabric/Forge/NeoForge before installing content: Paper-family plugins are not Fabric or Forge mods.
- Use Mods & Plugins for a compatible Modrinth or CurseForge release when the panel offers one. Check the target Minecraft version, loader and required dependencies before confirming.
- For manual files, stop the server; place plugins in plugins/, loader mods in mods/, and data packs in the world datapacks/ folder. Start and read loader errors before adding another item.
- If an update fails, restore the backup or remove the newly added file and its new dependencies together.
Players cannot join
- Check the server is running and use its assigned address and port.
- Match the client version, loader and mod list to the server. A vanilla client cannot join a server requiring client mods.
- For Minecraft 26.3 and later, inspect the allowlist: fresh servers default to white-list=true. Add the player or deliberately make the server public in Player Access.
- If the EULA prompt appears in Console, accept it there and restart once; do not repeatedly edit unrelated settings.
Crashes, lag and recovery
For a failed boot, read the first relevant error in the console or latest log: unsupported Java, wrong mod version, missing dependency and malformed properties need different fixes. Change one item, then restart and retest.
Low TPS is often world generation, entities or plugin work rather than RAM alone. Lower simulation distance, inspect recent plugins and use the Minecraft lag guide. Restore a known-good backup if the world fails immediately after an upgrade.