Bedrock players can connect again. The server side of Minecraft's switch to the new Bedrock networking has been done, and this is what changed and why.
What broke, in short ΒΆ
Mojang is replacing RakNet β the UDP transport Bedrock has used since forever β with NetherNet, and the change came in stages:
- 26.40 (2026-08-04): first Bedrock release that can speak NetherNet.
- 26.50 (2026-09-15): NetherNet became the default transport for Bedrock dedicated servers.
- 26.60 (2026-10-27): RakNet was deprecated on the client side, and the dedicated server's "not using NetherNet" warning became a hard error.
That second date is the one that mattered. A Bedrock client on 26.60 no longer speaks RakNet, so a server still serving only RakNet cannot be reached by those clients at all. The server was in exactly that state until this evening.
Geyser had been warning about it since 2026-10-25, printing a banner on every start:
WARNING! NetherNet support is NOT enabled. Players will not be able to connect to your server, starting October 27th, when NetherNet is scheduled to release.
The gap ΒΆ
How long Bedrock players were locked out is hard to pin down exactly, because a client that cannot find a transport never reaches the server β there is no failure on our side to count, only silence.
What the logs do say:
- The last Bedrock player to get in over RakNet was 2026-10-29 18:07 UTC.
- NetherNet was switched on at 2026-10-30 20:45 UTC.
- The first Bedrock player to get in over NetherNet was 2026-10-30 21:01 UTC β 16 minutes later.
So the window where a player on the newest Bedrock client could not get in is roughly a day, probably a bit less. Players on older Bedrock versions kept connecting throughout, because those clients still spoke RakNet β which is why the outage was quiet rather than obvious.
One detail worth keeping in mind: the last RakNet connections on 2026-10-28 were already from a 26.60 client (protocol 2225). The client had NetherNet available but still chose the old transport, because the server only offered that one. That is the switch working as designed on the client side.
What was changed ΒΆ
| Change | Detail |
|---|---|
| Geyser updated | 2.12.1 build 1278 β NetherNet-capable |
| Transport switched | transport: nethernet β RakNet is no longer served |
| Signaling enabled | Geyser's built-in signaling server on port 19132 |
| Public address advertised | STUN discovery resolved the public IP and port on its own |
The port layout is unchanged: 19132 UDP for gameplay, 19132 TCP for signaling. The address players type is still mc.seonbi.lt, port 19132 β no new port to remember.
Why signaling exists ΒΆ
RakNet connected straight to the server over UDP. NetherNet adds a step in front of that: the client first makes an HTTP request to a signaling server, which replies with the details needed to open the game connection over WebRTC (still UDP). The MOTD and player count in the server list are fetched through the same request.
That means a server needs a TCP port as well as the usual UDP one β which is why port 19132 is now open on TCP too.
Update your Bedrock client ΒΆ
This is the part that needs your attention.
The server now speaks NetherNet only β RakNet is no longer served at all. That flips the requirement around: instead of needing a newer client, Bedrock players now need a client that is new enough to speak NetherNet in the first place.
| Bedrock version | Can it connect? |
|---|---|
| Older than 26.40 | No. The client has no NetherNet support and the server no longer offers RakNet. |
| 26.40 β 26.59 | Yes. NetherNet is available and the client uses it. |
| 26.60 and newer | Yes, and this is the version to aim for. RakNet was removed from the client entirely, so there is no old transport left to fall back on. |
Short version: update your Bedrock client to 26.40 or newer, and 26.60 is the safe target.
The server side is finished either way β there is nothing to change in your server entry, and no new port to type. This is purely about the client on your phone, console or tablet.
How to check which version you have ΒΆ
In-game: pause the game, open Options β Resource Packs, and the version string is in the bottom-left corner.
To update the client itself:
- Android β the Play Store updates the game on its own, but a pending update can sit for a while. Open Play Store β your library β Minecraft and check whether an update is waiting.
- iOS / iPadOS β same idea in the App Store β Minecraft.
- Xbox / PlayStation / Switch β the game updates itself over the console's own store; the same in-game Options β Resource Packs screen shows the version.
If you are already on 26.60 or newer, you are done β there is nothing to update and nothing to change about how you join.
What you need to do ΒΆ
- Update your Bedrock client to 26.40 or newer (26.60 recommended). This is the only thing that is actually required.
- Join as you always have β same address, same port, saved entry untouched.
- Accept the "trust on first use" prompt if it appears on your first join after updating. Our signaling currently runs on plain HTTP, and the client remembers the server from then on.
Serving signaling over HTTPS removes that prompt entirely. Geyser can do that with a TLS certificate on the same port, or the signaling port can sit behind a reverse proxy that terminates TLS. Both are covered in Geyser's guide.
If you still get disconnected ΒΆ
The Bedrock client reports transport failures with its own error screen. You may see a screen with the codeword Terracotta and an error code such as ClientDisconnection-66.
Worth knowing before you go searching: Mojang's own help page defines Terracotta as "an unspecified error occurred." It is a generic client-side codeword, not the name of a specific fault, so searching for it on its own will not lead anywhere useful. The two fields that do carry information are the error code and the transport line (it will read NetherNet:19132).
If you land on that screen:
- Check your client version first (above). A client older than 26.40 cannot connect at all, and that is the most likely cause.
- Re-add the server entry if you have been playing since before the switch. The Bedrock client caches connection details per server entry, so a stale entry can keep failing even after the server side is fixed.
- Check your network. The game connection is WebRTC over UDP; a phone on flaky Wi-Fi or mobile data will drop it periodically, and the client will show you this same screen.
More reading ΒΆ
- Geyser's write-up: Preparing Your Geyser Server for NetherNet β the reference this switch was based on, including the troubleshooting table for console errors
- Geyser setup guide β the config changes, with per-host notes
- Geyser: HTTPS for NetherNet β how the trust prompt is removed
- Mojang's NetherNet onboarding guide β the protocol side, for the curious
- Bedrock Edition 26.60 on minecraft.wiki β the release notes