Bedrock players and NetherNet (Minecraft Bedrock 26.60)

Minecraft: Bedrock Edition 26.60 is planned for 27 October 2026. From that update on, Bedrock players can only join servers that use Mojang's new way of connecting, called NetherNet. The old way stops working for them that day. Java players aren't affected at all.

The short version: with NetherNet, a Bedrock player's game first asks the server how to connect, then joins. That first step uses the server's port in a way the Java server already does, so Bedrock players now need a port of their own instead of sharing the Java port. Here's what that means for your server.

Crossplay servers: we're switching them over for you

If you have a Minecraft Crossplay server (Paper with Geyser and Floodgate), you don't need to change any settings. Before 27 October we're giving every crossplay server its own Bedrock port and turning NetherNet on for it.

1. Find your Bedrock port. Open your server in the client area. On the overview, the Bedrock / Console (crossplay) box shows the Server Address and Port that Bedrock players should use. Once your server has been switched over, that port is the new Bedrock port. You'll also see it on the Network tab with the note Bedrock (NetherNet). Please don't remove that port.
2. It starts working at the next restart. We restart each server once, at a time when nobody is online, before 27 October. You can also restart it yourself whenever suits you.
3. Tell your Bedrock players. In Minecraft, they edit your saved server, keep the same address, and change the port to the new Bedrock port. The new port already works with today's Bedrock version. The old port also keeps working for Bedrock until 27 October, so there's no rush on the day.
4. The first join. The first time a player joins on the new port, Minecraft may ask whether they trust the server. That's expected, and they can say yes. It only asks once on each device.

On Paper, Purpur and other Spigot-based servers, Geyser can only use NetherNet when the server runs Minecraft 1.21.9 or newer. If your server is on an older Minecraft version, open a ticket and we'll go through the options with you before 27 October.

A few servers are a little different. If your server already had its own separate Bedrock port, that port stays the same and your players don't change anything. On a dedicated IP, the Bedrock port is usually 19132, which is Bedrock's default, so players only need the address. New crossplay servers get their Bedrock port automatically when they're created.

Please don't edit the bedrock section of Geyser's config.yml on a crossplay server. Our setup resets it on every start, and the NetherNet settings come from the server's startup instead, which takes priority over the file.

The same switch-over also covers our other Minecraft servers that already had Geyser installed when we made the change (Paper, Purpur, Fabric, BungeeCord and similar). Your new Bedrock port is on the Network tab with the note Bedrock (NetherNet), and you don't need to edit any config.

If you install Geyser yourself

If you add Geyser to a Paper, Purpur, Fabric, NeoForge, Velocity or BungeeCord server after our switch-over, or your server doesn't have a Bedrock (NetherNet) port yet, here's how to set it up. Prefer we do it? Open a ticket and we'll set it up for you.

1. Update Geyser. NetherNet needs Geyser build 1237 or newer, and GeyserMC recommends always using the latest build from geysermc.org/download. To see which build you have, type geyser version in the console. On a crossplay server you can update Geyser and Floodgate from the Crossplay tab.
2. Check your Minecraft version. On Paper, Purpur and other Spigot-based servers, Geyser's NetherNet support needs Minecraft 1.21.9 or newer. On older versions the console shows Built-in signaling could not start. If you can't update, open a ticket and we'll look at the options with you.
3. Get a second port. Open the Network tab and select Request Allocation. Leave the port box empty and we'll pick a free one for you. Every port on your server is open for both TCP and UDP, so you don't need to change anything else. This port must not be your Java port.
4. Edit Geyser's config. Stop the server and open Geyser's config file:
   • Paper, Purpur and other Spigot-based servers: plugins/Geyser-Spigot/config.yml
   • Fabric: config/Geyser-Fabric/config.yml
   • NeoForge: config/Geyser-NeoForge/config.yml
   • Velocity: plugins/Geyser-Velocity/config.yml
   • BungeeCord: plugins/Geyser-BungeeCord/config.yml
   In the bedrock section, set these values and leave the rest as they are:

   bedrock:
     address: 0.0.0.0
     port: YOUR_BEDROCK_PORT
     clone-remote-port: false
     transport: nethernet
     signaling:
       advertise-addresses:
         - YOUR_SERVER_IP

   Replace YOUR_BEDROCK_PORT with the port you just got, and YOUR_SERVER_IP with your server's IP address, the numbers before the colon on the Network tab. Your server runs in a container, so Geyser can't work out its public address by itself, and this line tells Bedrock players where to connect. On Geyser builds from before 20 October 2026, advertise-addresses goes one level deeper, under signaling then builtin. Newer builds move it to the place shown above by themselves, so updating Geyser is the easiest fix if you're unsure.
5. Start the server and check the console. You should see a line like Built-in signaling started on http://0.0.0.0:YOUR_BEDROCK_PORT.
6. Tell your Bedrock players to use your server's address with the new port. The first time they join, Minecraft may ask whether they trust the server, and they can say yes.

Geyser can also accept both the old and the new way at once (transport: both), which needs a second UDP port. GeyserMC's setup guide explains it. For almost everyone, nethernet is the simpler choice, because Bedrock 26.50 and newer fully support it.

Vanilla Bedrock and Endstone servers

Bedrock's own server software already supports NetherNet. We'll switch Vanilla Bedrock and Endstone servers over on 27 October, when Bedrock 26.60 is released, restarting each one only when nobody is online. Your address and port stay exactly the same. Players on older Bedrock versions need to update their game to join after that.

If you've pinned your server to an older Bedrock version, switch it back to the latest version once 26.60 is out, so players on 26.60 can join. If you run PocketMine-MP or other Bedrock server software, please open a ticket and we'll check it with you.

After 27 October

When Bedrock 26.60 comes out, Geyser needs an update before players on 26.60 can join, the same as with every Bedrock release. On crossplay servers you can do this from the Crossplay tab as soon as GeyserMC publishes a build that supports it. On other servers, download the latest build from geysermc.org/download. If a player can't connect, make sure their Minecraft is up to date too.

If Bedrock players can't connect

1. Check that NetherNet is answering. In a web browser, open http://YOUR_ADDRESS:YOUR_BEDROCK_PORT/v1/join, using http:// and not https://. If NetherNet is running, you'll see a short line of text with your server's name and version. If the page doesn't load, NetherNet isn't running on that port yet. Restart the server, then check the console.
2. Make sure the Bedrock port isn't the Java port. If the console says Built-in signaling cannot use port … because the Java server already uses it, Geyser is still set to the Java port. Set clone-remote-port: false and port to your Bedrock port, as in the steps above. On a crossplay server, just let us know.
3. Look for the NetherNet warning. If the console still shows NetherNet support is NOT enabled after a restart, Geyser is still using only the old way. Check transport, and check that Geyser is build 1237 or newer.
4. You don't need to open any firewall. Every port on your server is already reachable over both TCP and UDP, so there's nothing to open or forward on our side.
5. Check the player's version. NetherNet works fully from Bedrock 26.50. Players on older versions should update their game.

Still stuck? Open a ticket or message us on Discord with your server's name and what the console shows when Geyser starts, and we'll sort it out with you.