Skip to content
Minecraft

Bedrock server and NetherNet: get ready for 26.60

Published on 26 October 2026

Bedrock 26.60 is planned for Tuesday 27 October 2026. After that, Bedrock players no longer connect over RakNet, the old way of connecting. They use NetherNet instead. Do you have a Minecraft Bedrock server? Then you do three things after the release: reinstall your server, check transport and check your UDP ports. Here’s how.

What is NetherNet?

NetherNet is the new way Bedrock connects to a server. First the player and the server find each other over TCP. After that, the game runs over UDP. According to Mojang, NetherNet has been the default for dedicated servers since Bedrock 26.50, and Mojang calls RakNet deprecated. GeyserMC and Open Collaboration write that Bedrock players stop connecting over RakNet from 26.60. No time on 27 October has been given yet.

Step 1: reinstall your server after the release

A Bedrock server doesn’t update itself. A restart doesn’t fetch a new version. That only happens when you reinstall the server. As soon as Mojang releases Bedrock server 26.60, do this:

  1. Make a backup under Backups.
  2. Go to Startup and check that Bedrock Version says latest. Your server then fetches the newest version when it installs.
  3. Go to Settings and choose Reinstall Server.
  4. Start your server.

Your world, your allowlist and player permissions stay. More about versions is in Change your server version.

Step 2: set transport to nethernet

Open the file server.properties in File managers. Check that it contains this line:

transport=nethernet

Does it say transport=raknet? Change that to nethernet, click Save content and restart your server. Don’t use raknet anymore: after 26.60, players can’t connect with it.

Step 3: make sure you have enough UDP ports

With NetherNet, a Bedrock server needs its own UDP port per player. Check under Network how many ports your server has. In server.properties, server-udp-ports must list those extra ports. Too few ports, or not sure it’s set up right? Open a ticket with your server address and we’ll take a look with you.

What do your players see?

  • A question to trust the server. When a player connects through an IP address, Bedrock asks the first time whether they trust the server. That’s normal. Choose to trust it.
  • Consoles. On Xbox, PlayStation and Switch you can’t add a server yourself. The well-known workaround BedrockConnect doesn’t work with NetherNet yet. So we can’t promise that console players will reach your server after 26.60.

Playing with Java players through Geyser?

Does your group run a Java server with Geyser? Then Geyser needs to move to NetherNet too. How that works is in Install Geyser. No server of your own yet? See Minecraft Bedrock server hosting.

Frequently asked questions

Do I need to do anything before 27 October?

Yes, you can already set transport=nethernet in server.properties and check that server-udp-ports lists your extra ports. After the release of Bedrock server 26.60, reinstall your server.

Will my world stay when I reinstall?

Yes. Your world, your allowlist and player permissions stay. Still make a backup under Backups first, just to be safe.

Why does my Bedrock server need more ports?

With NetherNet, a Bedrock server needs its own UDP port per player. You list those extra ports in server-udp-ports. If you have too few, open a ticket.

Can players on a console still connect?

We can’t promise that. Consoles can’t add a server themselves, and BedrockConnect doesn’t work with NetherNet yet.

More questions? See all frequently asked questions

Related articles