Bedrock 26.50 and 26.51: why players can't join your server (and how to fix it)
On 15 September 2026 Minecraft Bedrock 26.50 Wilderness Bound shipped, followed a day later by hotfix 26.51. For players that is good news: the dappled forest, poplars and cushions arrive on phones, consoles and Windows at the same time as Java 26.3. For anyone running a Bedrock server it mostly means a week of 'Outdated server', 'Outdated client' and 'Unable to connect to world'. That is not your server or your network. It is one rule that Bedrock enforces far more strictly than Java: server and player have to run exactly the same version.
What shipped on 15 and 16 September
Bedrock went from 26.45 (28 August) to 26.50 and then to 26.51. The rollout differs per platform: Windows and PlayStation got 26.51 on 15 September, Xbox, Android and iOS on 16 September. Nintendo Switch did not get the hotfix and stays on 26.50. That is fine, because 26.50 and 26.51 share the same network protocol (2193) and play together without issues. The matching Bedrock Dedicated Server is 1.26.51.1.
The next major version is already lined up: 26.60 has been in preview since 2 September and is scheduled for 27 October 2026, so expect this story to repeat in six weeks. Content-wise 26.50 brings the same things as Java 26.3; we covered those in Minecraft 26.3: what changes for your server.
Why players suddenly cannot join
Java is forgiving: with ViaVersion a 26.2 server talks to clients that are years old. Bedrock is not. A Bedrock client can only connect to a server that speaks the same protocol, and every release that bumps the protocol locks older clients out. 26.50 bumped the protocol compared to 26.45, so from that moment old and new no longer fit together.
The timing makes it worse. On most hosting panels, ours included, the Bedrock server downloads the newest version on every (re)start as long as the version is set to 'latest'. Restart your server on 15 September and it runs 26.51 while part of your players stay on 26.45 for days: app stores roll out in stages, consoles do not always update automatically, and on Xbox the player sometimes has to go to 'My games & apps' to trigger the update. The reverse happens too: players update on day one while your server has been running on 26.45 for weeks without a restart. Either way the player sees 'Outdated server' or 'Outdated client', and on consoles often just 'Unable to connect to world'.
How to fix it in five minutes
First check which version your server runs: the console prints 'Version: 1.26.51.1' (or another number) on startup. Then ask your players which version they have; it is shown in-game at the bottom of Settings → Profile. That leaves you two choices.
Pin the server to your players' version. In the game panel open the Startup tab and, under Bedrock Version, replace 'latest' with the exact number, for example 1.26.45.1 if your group is still on 26.45, then restart. Once everyone has the update, set it back to latest or to 1.26.51.1. This is the best option when your regular group plays on Switch or Xbox and you do not want half of them locked out for a week.
Have everyone update. If your server already runs 26.51, the fastest route is often for the stragglers to fetch their update: on phones via the app store, on Xbox via My games & apps → Updates, on PlayStation via Options → Check for update. Switch players are on 26.50 and can join as they are.
Two things not to skip. Make a backup before switching versions: a world that has been opened on 26.50 does not reliably go back to 26.45. And go through your resource packs and behavior packs after the update; packs that rely on an old engine version sometimes let the server start but break specific blocks or entities. How to set up backups sensibly is covered in backup strategy for your Minecraft server.
Geyser, PocketMine and other server software
If your Bedrock players join a Java server through Geyser, the story is simpler: Geyser 2.11.3 (17 September) supports Bedrock 26.30 through 26.51, so a Geyser update is enough to let everyone back in. Mind the Java side though: Geyser presents itself as a Java 26.2 client. If your Java server is already on 26.3, Geyser needs ViaVersion 5.12.0 next to it; on a 26.2 server it works without extras.
PocketMine-MP is behind. Its latest release, 5.44.3 from July, supports Bedrock up to 26.30 and therefore cannot accept 26.50 clients until the PocketMine team ships a new version. Nukkit derivatives have the same problem. If you run one of those, your options right now are to wait or to move temporarily to the official Bedrock Dedicated Server with a copy of your world.
What to set up for next time
Pin the version in your panel to a concrete number instead of latest, and raise it deliberately when your players are ready, ideally a week after a release. Put a temporary notice in your server name or Discord as soon as Mojang announces a release, so players know they need to update. And plan the next round already: 26.60 is on the calendar for 27 October.
No Bedrock server of your own yet? At MC-Node a Minecraft Bedrock server starts at €2.50 per month, with the version selectable in the panel and a free subdomain for your players. Further reading: Minecraft Bedrock server: playing together on console, phone and PC and voice chat on a Bedrock server.