Server Error / Failed to Start
Diagnose why a Bedrock server fails to start.
On this page
A Bedrock server that fails to start usually prints an error in the Console and then stops immediately. This guide helps pinpoint the common causes from the log.
First Steps#
- Open the Console tab and read the last lines of the log before the server stopped.
- Look for keywords:
Error,Failed,Unable, or a filename. - Match it with the common causes below.
Common Causes & Fixes#
Version Mismatch#
The log mentions a mismatch or the bedrock_server file is missing.
Fix: see the Update Bedrock Version guide and make sure Server Version = latest.
Corrupt Configuration File#
The error points to an invalid server.properties or permissions.json (bad JSON).
Fix: correct the JSON format, or delete the file and let the server recreate it.
Port Already in Use#
A "Failed to bind" or "address already in use" message. Fix: stop the other server using the same port, check the Network tab, then restart.
Out of RAM#
The server dies while loading a large world. Fix: reduce the load (world/plugins) or upgrade RAM via the client area. See Upgrade Server.
Corrupt World#
An error while opening the world folder. Fix: restore from a backup. See Backup & Restore.
If It Still Fails#
Copy the entire console log, then open a support ticket. Attach the log and mention the steps already tried.