Since the Bedrock support portal has closed its tickets, I'm forced to write this here. If anyone from support could please forward this report to Bedrock, I would be extremely grateful.
Since updating to Bedrock Dedicated Server versions 1.26.30 and later, players are unable to join the server.
The client displays:
"Connection Timed Out"
Expected Result:
Players should successfully connect to the Bedrock Dedicated Server.
Actual Result:
The client attempts to connect for approximately one minute and then displays "Connection Timed Out".
Environment:
Minecraft Bedrock Client 1.26.31.1
Bedrock Dedicated Server 1.26.31.1
Debian Linux VPS
Public dedicated IP address
UDP port accessible from the Internet
Testing Performed:
Bedrock Dedicated Server 1.26.23
Result: Works correctly. Players can join immediately.Bedrock Dedicated Server 1.26.30.5
Result: Connection Timed Out.Bedrock Dedicated Server 1.26.31.1
Result: Connection Timed Out.
Additional Information:
The exact same VPS, network configuration, firewall rules, and server settings were used for all tests.
Multiple ports were tested.
Clean server instances were tested without addons or custom content.
Network packet captures confirm that UDP traffic reaches the server and responses are sent back.
The issue only appears after updating from 1.26.23 to 1.26.30+.
Rolling back to 1.26.23 immediately restores normal connectivity.
Reproduction Steps:
Deploy Bedrock Dedicated Server 1.26.31.1 on Debian Linux.
Connect using Minecraft Bedrock 1.26.31.1.
Wait for connection.
Observe "Connection Timed Out".
Additional Notes:
This issue appears similar to other reports submitted after the 1.26.30 update where external server connections fail despite the server being online and reachable.
Any guidance or confirmation of a known issue would be greatly appreciated.
Comments 10
I am having this issue, setting enable-lan-visibility=true resolves it but only for a single server on a multi server host
Can this please be fixed, I have not been able to connect to my server for months now. Linux host, running an existing world of course. I stopped playing months ago because of this……and it’s still here? Please?
More detailed infos on my Behavior: Server join goes into Timeout (10sec)- no detailed Logs on the server.
Environment: Windows Server + Windows Client
✅Server Version: 1.26.36.1, Client 1.26.33 (GUI) (default server.properties, added allowlist.json)
❌Server Version: 1.26.36.1 Client Windows: 1.26.33 (GUI)
(OLD LEVEL-world DATA from March 2026 - Tested from Backup)
✅copied Server world to Windows Client Bedrock Windows: 1.26.33 (GUI) (without server)
C:\Users\*\AppData\Roaming\Minecraft Bedrock\Users\*\games\com.mojang\minecraftWorlds\
✅ New created World (no level data) - default server.properties
✅ New created World (no level data) - custom server.properties
(seed, servername, difficulty=normal, transport=rakne)
❌Current Version with old Server.properties (03/2026)
❌Current Version with old Server.properties and old worlds data (03/2026)
LEGACY:
✅ Bedrock Server Version: 1.26.10.4 (Tiny Takeover) with matching Client from 03/2026)
Maybe there is a world loading combined with server.properties problem?!?
I’ve also been having this issue for months. Just a few details:
As Josy mentioned, I copied my world back to my local Windows client, and everything worked fine. If I copy that world back from the Windows client to the bedrock server, it still hangs.
The particular Docker container that I use for my bedrock dedicated server has been reading as “unhealthy” since this problem occurred, the server itself seems to be hanging. Logs seems to indicate a successful load and then are basically silent, at least at my log level.
I can provide an example world if needed.
Sounds like we have to file this under the client, not the server. If the UDP packets are getting a response but the client is ignoring non-standard ports…
But then again, who uses non-standard ports to hide their online BDS from trolls and griefers?
i think this two bugs relate MCPE-240610
WORKAOUND FOUND!! What works for me - its nothning network related its “WORLDDATA” data related.
The current Client can update my world metadata and settings that the world is working again!
make sure server.properties work with “fresh/empty world”
copied the world to my lokal computer worlds
C:\Users\#username#\AppData\Roaming\Minecraft Bedrock\Users\#playeridnumber#\games\com.mojang\minecraftWorldsChecked World settings and edited World settings like i wanted it to behave
Loggend in to the World (locally)
copy world back to BDS
now i can successfully login to my >1000 days longtime world again!
Client Version: 26.45, 1.26.45.1)
Server Version 1.26.45.1
INFO: still working in 1.26.50.4 - but needs to Change transport=nethernet
maybe this was all about preparation for this new behaviour.
source:
https://www.minecraft.net/nl-nl/article/minecraft--bedrock-edition-26-50-changelog
Dedicated Server
NetherNet is now the default transport used by dedicated servers
Windows dedicated servers, including EDU, now use the correct application data directory for Bedrock and Education
Bedrock Dedicated Server 1.26.31.1 – Malformed RakNet PONG Responses After World Upgrade
Summary
After upgrading to Bedrock Dedicated Server (BDS) version 1.26.31.1, existing worlds migrated from a previous server version become inaccessible to clients.
The issue appears to be related to malformed RakNet responses generated by the server during connection establishment.
Environment
Server: Bedrock Dedicated Server 1.26.31.1
Host OS:
Windows
Client: Bedrock Edition client 1.26.31.1
Network analysis tool: Wireshark
Description
When an existing world created on a previous BDS version is loaded in BDS 1.26.31.1, clients are unable to connect.
Packet captures show malformed RakNet PONG packets being sent by the server.
Observed behavior:
The client sends an unconnected PING.
The server responds with an unconnected PONG.
The returned PONG packet appears malformed in Wireshark.
Connection establishment does not proceed successfully.
Additionally, malformed RakNet PONG packets can be observed after the world is loaded and the server is running.
Expected Behavior
Server should return a valid RakNet unconnected PONG response.
Clients should be able to complete the RakNet handshake and connect successfully to the server.
Existing worlds should remain accessible after upgrading the server version.
Actual Behavior
RakNet unconnected PONG responses appear malformed.
Clients cannot establish a connection to the server when an upgraded existing world is loaded.
Comparison / Control Test
Using the same BDS 1.26.31.1 server installation:
Let the server to create a vanilla/new world allows clients to connect normally.
Server responds correctly and remains fully accessible.
The issue only occurs when loading an already existing world migrated from a previous version.
Migration Details
Only the following items were copied from the previous server installation:
World folder
server.propertiesNo plugins, extensions, custom server modifications, or additional components were installed.
Additional Notes
The problem appears tied to loading an existing upgraded world
A fresh/vanilla world on the same server version does not exhibit the issue.