Minecraft Bedrock Server Problems and How to Fix Them

Bedrock servers behave differently from Java ones. They use a different protocol, different config files and different networking, so Java advice often does not apply.

Players cannot connect

• Bedrock uses UDP, not TCP. The default port is 19132. Confirm the port assigned to you in the panel and use that one.
• Enter the address and port correctly in the Add Server screen.
• Check that the server is online in the Console tab.

Version mismatch

Bedrock clients update automatically, often faster than servers. If players see an outdated server or client message, update the server software to match. If the server is newer than clients, players must update their game.

Allowlist and permissions

• Turn the allowlist on with allow-list=true in server.properties and manage players with the allowlist commands in the Console.
• Permissions such as operator are set in permissions.json or with the op command.
• Use the exact gamertag, as typos are the most common failure.

Consoles

Xbox, PlayStation and Switch have no built-in option to add a custom server address. Common workarounds include a friends list trick or a connection helper service such as BedrockConnect. Support varies by platform, so check the current method before promising it to players.

Crossplay with Java

Java players cannot join Bedrock servers directly. To mix them, run a Java server with Geyser and Floodgate. See our Geyser guide.

Worlds and add-ons

• World data lives in the worlds folder. Back it up before changes.
• Behavior and resource packs go in their matching folders and need to be referenced in the world configuration. Follow the pack's instructions.

Tips

• Keep server and client versions aligned.
• Check the Console for pack errors on startup.
• Open a ticket on Discord if players on one platform fail while others succeed. Include their platform and the error text.