Restart and update
- Warn players and create a backup before a Bedrock version or world change.
- Stop the server in the panel, wait for it to exit, make one file change, and start it again.
- Confirm the world loads and a Bedrock client on the matching release can join before deleting the recovery point.
Behavior and resource packs
- Use a pack made for Bedrock and the current server version; Java plugins and Java mod JARs do not run here.
- Stop the server and upload the complete behavior or resource pack to the corresponding Bedrock pack directory using Files or SFTP.
- Enable the pack for the intended world using its Bedrock world pack configuration, then restart and check for missing dependencies or pack UUID/version conflicts.
- If a pack breaks the world, restore the backup instead of deleting unknown world data.
A player is rejected
- Check the exact panel address and Bedrock port, the server status and the client release.
- If allow-list is enabled, add the player’s correct gamertag; a matching player cap does not grant access.
- Check Console for a specific authentication, version or pack error before changing network settings.
Wrong world or failed boot
Confirm level-name matches the intended world folder and server.properties is valid. Stop the process before replacing world files. Recover the complete world from the last good backup if a pack or migration corrupted it.