Minecraft Bedrock NetherNet explained: what changed in 26.60

What is NetherNet?#

Every online game needs a way for a player's device to find a server and exchange game data. Bedrock Edition used RakNet for that since its early days. It is a UDP-only library that has not been maintained for a long time. NetherNet is Mojang's replacement. It is the same system Bedrock already used for Realms and for joining friends, now extended to dedicated servers.

NetherNet works in two steps:

1. Signaling. The player's game asks the server (or a signaling service) how to reach it. For a dedicated server this is a small web request, which is why the port needs TCP.
2. Game traffic. After the handshake, the actual gameplay data flows over UDP, as before.

Timeline#

This is why a server that worked perfectly on Monday could suddenly show "Unable to connect to world" to everyone after the 26.60 update reached their devices.

What server owners must change#

Bedrock Dedicated Server (BDS)#

1. Update the server

   Download the latest Bedrock Dedicated Server from minecraft.net and replace the program files. Keep your worlds folder, server.properties, allowlist.json and permissions.json.

2. Set the transport

   Open server.properties and make sure the line below is present. A leftover transport=raknet line will no longer work.

3. Open the port for TCP and UDP

   In your firewall and router, allow the Bedrock port (19132 by default) for both protocols.

4. Restart and test

   Join from a phone or Windows device with your IP and port.

server-port=19132
transport=nethernet

Geyser (Java server with Bedrock crossplay)#

In Geyser's config.yml set transport: nethernet under bedrock: and give Bedrock its own port that is open for TCP and UDP. Geyser builds from around number 1280 convert an old raknet setting by themselves, but older builds keep it, so update Geyser first. The full walkthrough is in our GeyserMC guide.

What FreeGameHost servers do automatically#

On FreeGameHost the Bedrock server template writes transport=nethernet and the port settings into server.properties every time the server starts, so you can't end up on RakNet by accident. If your server is older, update it:

1. Keep Bedrock Version on latest in the Startup page.
2. Go to Settings and choose Reinstall Server. The installer downloads the newest server files and keeps your server.properties, allowlist.json and permissions.json. Your world stays in the worlds folder.
3. Start the server and share the address and port shown by the Connect button on the Console page.

Crossplay servers (Paper or Fabric with Geyser) get their own second port with NetherNet already switched on when you tick Enable Bedrock Crossplay at creation.

Free Bedrock server Already set up for NetherNet. Start it and share the address.

Create a Bedrock server

Common problems after the switch#

"Unable to connect to world"#

Update the server software, check transport=nethernet, and confirm the player uses the Bedrock port, not the Java port. Also check that the server is actually running.

"Outdated server" or "Outdated client"#

The game version and the server version don't match. Either the server needs the newest Bedrock release, or the player's game needs updating.

Works at home, not for friends#

The port is probably only open for UDP, or only forwarded to the wrong device. NetherNet needs TCP as well as UDP on the same port.

Consoles can't join any more#

Consoles don't have an Add Server button, and the DNS trick many people used for it may not work with NetherNet servers yet. Our console joining guide covers what works right now.

Should server owners worry?#

Not really. For most people the whole change is one config line, one port rule and an update. The real casualties are old tools that only know RakNet. If you rely on a third-party plugin or proxy for Bedrock, check that it has a NetherNet release before the next Minecraft update lands.