After upgrading BDS (Ubuntu Server) to 26.30, android users have been crashing after the text “Connecting to external server” is displayed, presumably where “Locating server” happens. iOS, Switch and Windows users are not affected in my case.

For me, I updated the BDS and then tried to connect but it would not, then I updated the managing software and again it would not connect.
I connect from my PC to a standalone NAS and not through the LAN network.
(Why was the vanilla server comment section added to the startup? That makes no sense, it’s there even when it’s a modified server)

I also encountered this issue, and I found that I could resolve the connection timeout by setting `enable-lan-visibility=true` in the server properties. Despite the servers running in containers with nonstandard ports exposed, that setting made the difference for me. Your mileage may vary.

Enabling lan-visibility=true worked on one windows based server PC, but only for the instance on 19132. On another windows based server PC I could not even get this to work. Seems hit and miss.

I checked and lan-visibility is set to true on mine, and I still have the issue.

This has something to do with the allowlist…. I can only connect to my server after disabling it and enabling the LAN. It’s quite frustrating not knowing how to fix this so it runs like before….WITH THE ALLOWLIST WORKING.

For the record, none of the listed potential fixes here are working universally. While it may be related to changes made to the way clients are interacting with variables like lan-visibility or allow-list, changing these is not a universal fix.

Seems like for now, we can just play on worlds, friends' worlds, realms and somehow on our own LAN BDS server(s) with having the lan visibility true in server.properties file and joining it as a LAN player.

Well, I guess, minecraft pocket edition game has got a kind of reverse code things…

so whenever we are requesting the game to let us connect to our desired minecraft external servers, the game executes the “Quit” game function (for my case, thus my game closes everytime), “leave or quit server” function (for others case, thus they got the “saved” menu appeared and returned back to the main game menu instead of joining the servers)

and since we all aren't getting the exact same game entirely closes itself issue, um I guess it just because of our devices' OS version or architecture things.

same problem here

It seems like I’ve been able to resolve my problem. I believe that the key was refreshing level.dat. There are probably multiple ways to go about it but here’s what I did. I have a baremetal ubuntu 24 host (not docker or other container, or vm) hereafter referred to as BDS, and a separate windows machine I connect from to play minecraft, hereafter referred to as CLIENT.

1) On BDS, stop the server software, save off a copy of the world directory somewhere as a backup. Go into the world directory and zip everything into a file called myworld.mcworld:
$) cd world_dir
$) zip myworld.mcworld *
It’s important that the zip is created from inside world_dir so that the archived file paths are relative to that directory.

2) Move myworld.mcworld to CLIENT and double-click it to import it to minecraft.

3) Once imported, open the world. This step normalizes the level.dat file. You’ll notice that you’re not at your last x,y,z and your inventory is wrong, even if you’re logged into your normal minecraft account. That’s expected since you’re using local player data. Save and quit.

4) In the worlds menu in Minecraft, open the edit menu (pencil icon) on the world and export the world. This creates a new .mcworld file.

5) Move the newly exported .mcworld (which contains a normalized level.dat) to BDS

6) On BDS rename the file so it ends in .zip instead of .mcworld. Create the world directory that matches level-name in server.properties and unzip into there.

7) Start the server software.

Again, the high level goal is to sanitize any irregularity with the level.dat file. I also notice that now I get a ping measurement for my bds in the server list, which I did not before. This particular world was originally generated on a Switch, uploaded to Realms, downloaded and put onto a dedicated server. So, the level.dat file was perhaps already a bit traumatized though it was working before 26.30.

Good luck.

And, just to clarify about player data - when you put the world back onto the server and connect to it with your normal account, your position and inventory will be correct again. That information seems to be stored in the database rather than the level.dat file.

I've also been having this issue doing the same steps I even have made sure to turn on mobile data online play to see if that would work as well as make sure other settings are set to where not a lot of data packets could possibly be overwhelming my phone's system but no luck on getting it to work this issue started after the chaos cubed update got applied I was able to join just fine before that

You absolute legend amorelli. This worked for me.

A similar problem is currently affecting Windows clients joining BDS servers with LAN visibility turned off.
The fixes in other comments did not work for me.

I also can’t use any of my Dedicated Bedrock Servers. I run multiple on 1 PC. Only thing that works is to change custom port numbers to default, enable LAN visibility, and then obviously only run 1 instance. Worked fine before 26.30.5. Please fix Mojang!

I tried amorelli’s steps, didn’t work.

Hi. I’ve tried everything, but I can't get it to work with the new version. I even tried refreshing the .dat file twice, just as Amorelli suggested.
I’ve tried moving my Bedrock server to a different host, modifying server.properties, disabling add-ons, and even using much older backups. For now, the only thing that works is running it locally and inviting players who were already on the whitelist to join online.
My server runs in a Pterodactyl Docker container on Ubuntu, and it won't allow connections from any device (iOS, Android, PC, or PS5).
I hope this information is helpful.

Same issue on a PC running Windows 11 Pro. No issues connecting from inside or outside of the network before the update. I’ve tried all of the suggestions above with no success. A couple of observations. I can connect to a brand new world with no trouble. I can connect to a smaller world (~62 mb) with no problem. It’s my larger 380 mb world that I can’t connect to. Near as I can tell the only difference is the size of the world folder.

The hotfix seems to have made the problem worse… can’t even join a server with default ports, no allowlist, and LAN visibility anymore. That was the only workaround i found worked before and 26.31 broke it.

Same thing happening on my phone realme C65

I'm on Android open Minecraft app i have joining server “ Connecting to external server “ wait joining has closed automatically whatever, update hotfix coming soon will be can joining server better version v26.23

My theory for the root cause: The client sends an HTTP request to https://<ip>:<port>/v1/join when joining a server to check for NetherNet support, but due to a bug uses the raw IP and not the domain name. This results in the certificate having to be for the direct IP. This is causing the crash because if the DNS server responds with an AAAA record (IPv6), the address will not be formatted correctly when it sends the request (ex: https://xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx/v1/join instead of https://[xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx]/v1/join). This is causing a crash on Android because the URL format is invalid. This affects primarily mobile data players because some mobile carriers use DNS64, resulting in IPv4 addresses being wrapped in IPv6 addresses, which results in the invalid URL format and the crash. The proper way to fix this would be by using the domain name instead of the direct IP when making the request (see BDS-23060).

Still unable to join bedrock external servers on 6/21/26 ever since the sulfur cube update. Sometimes it crashes really quickly after being “done” generating world. Sometime it gives the “silverfish” error code. All looks good on server host’s end and we are all updated.

In troubleshooting, if I change the server port back to default 19132 in the server.properties file, I can connect. When I change the port back to a non-default port, I can no longer connect. It doesn’t matter if I connect via IP/Port or DNS/Port, the client (I’m using Windows) times out. A port scan shows the port as closed.
Running on default port is not an option for my server.

Same issue with one of my servers that was converted from a pc bedrock “single player” via realms (uploaded and then downloaded). My other two server created via crafty controller don’t have this issue. I am running the sever via crafter controller in docker on zimaos.

The issue with BDS is still happening. This bug is causing a long-term outage in multiple servers I host, and people are complaining. Please fix!

I may have found a fix for some (only tested on Bedrock). If you are upgrading an existing server and suddenly cannot connect (I tried updating from 1.26.23.1 to 1.26.30.5 and then again to 1.26.31.1), the issue may be caused by the hidden LANBroadcast flag in your world's level.dat file. Apparently older files often have this set to 0, which triggers a bug in the new server version that prevents it from broadcasting to clients.

As noted by @amorelli , you can open the world in a local single-player game which then flips the flag to 1. Alternatively you can edit the flag directly in an NBT editor. Here are the steps I used:

1. Download and extract1.26.31.1 files to a your desired directory.

2. Copy your entire existing world folder including your level.dat and your db folder) and paste it into the new server's worlds folder.

3. Do standard setup (I only know the basics like replace your allowlist, replace permissions, and configure server.properties and update level-name to match your world folder name.

   • Optional: You can temporarily change online-mode=false and allow-list=false... not sure if it’s need to bypass the bug, but it may help eliminate authentication roadblocks during a first test boot.

4. Use a bedrock NBT editor (or Java if applicable… not sure if this bug applies there). I used w1zardz Bedrock NBT Editor in a web browser so as to now have to download anything.

5. Upload your previously working level.dat which should (according to my steps) be located inside your newly copied world folder in the new server directory.

6. Scroll until you find the LANBroadcast variable. Double-click its value and change it from 0 to 1.

7. Click save/download to get the updated level.dat file. Now replace your new server's level.dat file with the new one you just downloaded.

8. Boot up the server. You should now be able to connect successfully from your local network!

9. If you did the optional online-mode and allow-list disabling, you can now open server.properties and change online-mode and allow-list back to true, and restart. Your server should now fully updated and accessible externally.

I checked @Droid Number 3 's fix, but my worlds have LANBroadcast set to 1 already.

Still the same issue on Bedrock 1.26.31.1 with both Android and Windows clients showing “locating server“ and “loading ping“ indefinitely.

I even restored the worlds' backups from before 1.26.30 to see whether that upgrade messed up the worlds, but no luck.

Update there's been a update but my still unable to join external servers when the app closes I now get the message the app has a bug and to update the app when there's a fix

I followed Droid Number 3’s exact same procedure to flip the LANBroadcast bit, and it worked like a charm! Thank you, Droid Number 3, for solving the mystery! 😂 🙏 🎉

Server: Windows 11, Bedrock 1.26.31.1

Client: Windows 11, Bedrock 26.31

Droid Number 3’s procedure also worked for me.

Server: Windows 11, Bedrock 1.26.31.1

Client: Windows 11, Bedrock 26.31

I am facing this problem after the latest update

I’ve been experiencing this since 2026/06/21 around 20:00 GMT. I’ve confirmed that the suggestion from Droid Number 3 does not work for me, my level.dat shows LANBroadcast was already set for my world.

I started experiencing it after the latest update and one of my friend too. He had this solved by using a Wi-Fi, but mine has not.

Can someone test if this still happens on 26.32?

Oh yes!

I have tested it on 26.32 and I can now join external servers as normally and the game doesn't close itself anymore (on this update).

my attached video below does have some servers joining issue and I think it is just because my internet. otherwise the game and server joining is working fine.

Thank you so much Mojang and the Bug fixing team(s)!

I have tried this on the 26.32 update just now, tried connecting to my friends server where we generally play in, but still, it doesn't work. It crashes again. It hasn't been fully fixed

Yep, I installed the new update, it still isn't working in 26.32, still crashes when I try to join a server

Public servers always worked for me, but others didn't.

1.26.32.2 no change for me. Still cannot run BDS with custom ports and LAN visibility false

I updated the server and the client and too was unable to connect. Tried Wi-Fi and mobile

My game crashs if I use mobile data

I’ve updated my server to 26.32 and now I can connect from my playstation, but still not Android.

The same thing is happening here.

It's fixed now ( on Android 15 atleast, for me ) in the latest update!!!

I've updated the game to 26.32, but it has not solved yet. My android version is 14.0.2.

I've just started experiencing this after i updated my Minecraft to the chaos cube. Still not solved.

Hello, I'm on OPPO K11 5G, Android 15. I'm using the latest 26.32 bug fix update (as of now I'm writing this comment), I am also experiencing this issue. It normally works on public experience servers. But on some custom external servers. And especially BDS which I tried to join in this video I attached. The game just closes too as described by other people.

I have the same issue, exactly like this, can't play with my friends, 4 of my friends aslo have the same issue.

a kid on YouTube found a solution

connect to a vpn (preferably a region in your own continent for the best ping)

now you should be able to join your desired server but if the server you're trying to join blocks the vpn

simply click play, wait 2-3 sec then go to app tabs and again into Minecraft, this will somehow trick the server into letting you in

!!has only been tried with CubeCraft and Lifeboat!!

nevermind, on the update 26.32 I thought it is fixed (as I recorded and sent a video already about it and that day it worked but not anymore 🙁 ) but I am having the issue again when I don't use vpn

and when using vpn and it works fine. but I can't understand this

simply click play, wait 2-3 sec then go to app tabs and again into Minecraft, this will somehow trick the server into letting you in

@crypt would you explain it a bit more more if possible?

Android Bug Report Findings

A native crash was captured from the Android bug report.

Relevant information:

Signal: SIGABRT (signal 6)

Abort message: JNI DETECTED ERROR IN APPLICATION: obj == null in call to CallVoidMethodV

The native stack trace includes:

libminecraftpe.so

Xal::Platform::Android::Sha256Java::AddBytes()

Xal::Auth::RequestSigner::HashRequest()

Xal::Auth::RequestSigner::SignRequest()

Xal::Auth::Operations::GetTokenAndSignature()

This suggests the crash occurs inside Minecraft's Xbox Authentication Library (XAL) while generating the authentication/signature request for external Bedrock servers.

Notes

This issue appears reproducible and does not seem to be caused by:

Server configuration

Network connection

DNS configuration

Resource packs

Aternos

Microsoft account credentials

The evidence suggests a client-side regression affecting external Bedrock server authentication on this device.

It has been almost 2 weeks now that my friends and I have been unable to join our dedicated external server on bedrock PC. Connection times out when we try to connect to it. Ever since the sulfur cube update 26.30.

I don’t understand how adding a biome can completely break the ability to join in dedicated servers, or how this did not affect realms. There have been 2 patches since the update where we keep thinking it is surely fixed, but neither have addressed our inability to play the game.

I hope our Mojang overlords have not abandoned us and working on this!

Just to add some more information. I am connecting to a local server via the Windows bedrock client, same issue on all three PCs. I can’t access with the local IP address but I can access it via the playit_dot_gg service I have setup for remote access.

This same issue is happening in entire south Asian or South east Asian region I have discussed from some of my friends according to me it’s a regional bug

no it's not a regional bug. I'm in the US and it's happening here too. It's happening EVERYWHERE. WHEN WILL THIS GET FIXED?? ITS BEEN SO LONG

But, it's not happening with my friends. It was happening with one friend, but he can still join with Wi-Fi.

I encountered the same problem on July 5th. After logging out of my Microsoft account, I couldn't log in again and my friends list couldn't be loaded.

It's probably because you have a teen Microsoft account. Just login with an adult account, and invite it to your family, and then allow the permission from it.

A century of votes is already done, but we are getting absolutely no response, are we? Just show us a sign to confirm that you are working on it actively.

Is everyone having problems using a self host server that was downloaded/transferred from Realms?

I’m not, I have a self hosted server that was created locally and never on Realms and we cannot connect unless I turn turn off `online-mode`, and then, obviously, it’s only LAN games that can connect.

Interesting, I have three servers, the two I created locally with crafty controller work fine but the one I downloaded from realms doesn’t.

Thank you

Droid Number 3!!!

Weirdly enough, this doesn't happen to me when joining the Hive. Only when joining my friend’s server and CubeCraft. I haven't tried other servers.

Things Ive Tried but to no Avail.

Redownloading minecraft

Clearing cache.

After downloading the bug fix update today I still cannot get on the servers the app just closes whenever I try are they ever going to fix this cuz I'd really like to play on servers again.

I play on the mobile app on Android. And yes I have uninstalled and reinstalled cleared the cache and all the other suggested fixes. My wife is on the same phone as me and cannot get on servers either.

They still didn't fix it guess the issue is deeper🫠

I FOUND A TEMPORARY FIX, you can use a vpn and it somehow fixes it. Im on Android and using Proton VPN (free).

I would like to provide additional reproducible test results, as this issue is still affecting my environment even after updating to 1.26.33.1.

Environment

• Bedrock Dedicated Server (Official)

• Ubuntu Server (also reproduced on Windows)

• Local family server (no proxies, no Docker, no VPN)

• Clean installation

• Fresh world also tested

• Default port (19132) and custom ports tested

• LAN Visibility tested both enabled and disabled

• Allow List tested enabled and disabled

• Online Mode tested enabled and disabled

Test Matrix

This means that introducing either the new client OR the new dedicated server is sufficient to reproduce the failure.

Platforms tested

Clients tested:

• Android

• iPhone (iOS)

Servers tested:

• Ubuntu

• Windows

The behavior is identical on both operating systems.

Error Details

The new diagnostic screen shows different internal error codes depending on the client:

Android:

Prerequisites-32

iPhone:

InitialConnection-13

Older client versions connect successfully to older servers without any issues.

Additional observations

• Fresh world does not solve the issue.

• Existing world does not solve the issue.

• Network configuration has been verified.

• Firewall has been verified.

• Same hardware, same router and same environment work perfectly with version 1.26.23.

• The problem started with the 1.26.30 series and is still reproducible on 1.26.33.1.

This strongly suggests a regression in the Bedrock Dedicated Server connection or handshake process rather than a configuration issue.

Hopefully these reproducible results help identify the remaining cases that were not resolved by previous fixes.

Thank you.

There is a high probability that this is a client-side issue, as the server is functioning normally. The exact same issue occurs even when connecting to the Java server using plugins like Geyser and Floodgate on a Paper server.

Personally, I was able to bypass the problem by using an IPv4 connection to my dedicated server

are you all still getting this issue 🤔 by the way, I use mobile data internet with having the allow mobile data option enabled in Minecraft game settings. I can join external servers and my game idk how isn't crashing or closing itself like I got before.

But the officials didn't stated this issue as solved, so maybe it is currently being solved for a lot of more devices.

I still can not get on servers, neither can my wife or multiple other ppl I know that use mobile like us. When we try to get on server the app just closes after a sec

nevermind. I have noticed it carefully now and the bug is available still on 1.26.33.1 MCPE game too 😞

But this time I have noticed something very different.

for both vpn off and on and with using mobile data internet, I still can't join external servers as my game crashes like before and can only join featured minecraft servers (the one minecraft pocket or bedrock edition game gives by default automatically) with using Wi-Fi internet ISP (no sim card) and vpn off,

I can join both external and featured servers and the game doesn't crashes.

But the twist is, with using Wi-Fi (no matter vpn on or off), the game never crashes while joining both already running servers and already stopped servers (I am not taking about the online-mode=true or false things)

And with using mobile data (no matter vpn on or off), the game only crashes while joining already stopped servers only, on the other hand I can join already running servers very well.

I guess if the bug fixer team focus on this twist, the bug can be solved more accurate.

Vpn and mobile data never worked for me either. Not a single workaround found so far spanning from 26.30 to 26.33 has ever worked for me. Still crashes like it did

I think the issue might be related to LAN visibility settings. All other settings left unchanged, turning off LAN visibility is the single change that leads to this problem.

I run multiple servers on one host at home. In past versions, I had each server on a custom port and LAN visibility off.

In these bugged versions of Bedrock, the above settings prevent client connections even when running only one server on the host. This is also true when using the default port and keeping the LAN visibility off. Using tcpdump, it appears the initial game ping packets are exchanged, but no gameplay connection is ever up and running.

However, gameplay works on the default or a custom port if LAN visibility is turned on.

Gameplay also works when running multiple hosts with LAN visibility on, even though only one host will actually be visible in the LAN list. The other servers can be connected directly from the server tab. Both servers successfully use custom ports for gameplay and will attempt to use 19132 for lan visibility. However, only the first world will be automatically detected and listed as a lan world on the Worlds tab. The other world(s) can be added in the Servers tab. All will play.

In short, it seems we are unable to turn LAN visibility off without simultaneously breaking gameplay.

For you guys the twist can work but for many others like me, it doesn't. They should look into fixing the entire thing. No workaround works for me and my friends at all.

I tried vpn and it is working. I am at the same position as when I was when the servers showed “Disconnected from Server”.

I would like to add a simple IPv4/IPv6 comparison that I reproduced on my own device.

Environment:

• Device: [device model]

• Operating system: HarmonyOS [6.1.0]

• Minecraft version: [v26.33]

• Minecraft package: Android version of Minecraft

• The same server and UDP port were used for the direct IPv4 and IPv6 tests.

Results:

• Direct IPv4 connection over mobile data: [X/Y] attempts worked.

• Direct IPv6 connection over mobile data: [X/Y] attempts caused the Minecraft client to close/crash.

I repeated these tests under the same conditions. In my environment, the direct IPv4 address works, while attempting to connect to the direct IPv6 address consistently or frequently causes the client to crash.

The device runs HarmonyOS rather than standard Android, although I am using the Android version of Minecraft.

I do not know the underlying technical cause, and I am not claiming that IPv6 explains every case in this report. I am only reporting the reproducible behavior observed on my device. The expected behavior for a failed or unreachable IPv6 connection would be a connection error or timeout, not termination of the application.

Update: Issue Still Reproducible in Bedrock 1.26.40

I tested the issue again after the release of Minecraft Bedrock 1.26.40.

Unfortunately, the connectivity issue is still present.

I performed a controlled comparison using the same Android device, same Wi-Fi connection, same network, and same server environment, changing only the Bedrock Dedicated Server version.

The important finding is that the error stage changes depending on the BDS version.

Environment

Test Results

Test A — Older Client + Older BDS

Result: WORKS

The older Minecraft client can still connect successfully to the older Bedrock Dedicated Server in the same network/server environment.

This is the known working combination and is being used as the baseline for comparison.

Test B — Client 1.26.40 + Older BDS

Result: FAILS

Error details:

When the 1.26.40 client attempts to connect to the older BDS, the connection reaches the InitialConnection stage and fails with:

InitialConnection-34

Test C — Client 1.26.40 + BDS 1.26.40

Result: FAILS

Error details:

When both the client and Bedrock Dedicated Server are updated to 1.26.40, the failure changes to:

Prerequisites-32

Key Finding

The same client device and network produce two different connection failures depending only on the Bedrock Dedicated Server version:

1.26.40 Client + Older BDS → InitialConnection-34

1.26.40 Client + 1.26.40 BDS → Prerequisites-32

Meanwhile:

Older Client + Older BDS → Works normally

This suggests that the failure is occurring at different stages of the Bedrock connection/handshake process depending on the server version.

Previous Testing

This issue has remained reproducible across multiple Bedrock releases.

Previous troubleshooting has already included:

• Fresh server/world testing

• Existing world testing

• Windows BDS

• Ubuntu BDS

• Default UDP port 19132

• Alternative ports

• Firewall verification

• Port forwarding verification

• enable-lan-visibility=true

• transport=raknet

These changes did not resolve the issue.

Current Status

The issue is therefore still reproducible with Minecraft Bedrock 1.26.40.

The most important comparison is:

I am attaching screenshots showing both error details.

The difference between InitialConnection-34 and Prerequisites-32 may help identify exactly where the newer Bedrock networking/handshake process is failing.

Please investigate whether this is a regression or compatibility issue introduced in the newer Bedrock networking stack / Dedicated Server connection process.

After the new update me, my wife and some friends are still having this problem. Try to join a server and the game just closes out. Haven't been able to access any server since sulfur update.

Same here as the comment immediately above. Weirdly, I have been unable to connect at all, my wife was able to connect for a couple of hours yesterday right before the 26.40 rollout, but now no luck for either of us.

This has been a truly monumental failure, the ‘Sulfur’ update. 😖

I had the same connection problem with my server since the ‘Sulfur’ update. It resolve when i set 'enable-lan-visibility=true'. I can now connect even when my server is not on my LAN. Really weird

Yea I also have this issue, everytime I join most servers (excluding new servers) on mobile data it just crashes and closes my game, and on wifi its fine, it is extremely annoying and I think I also have this problem on some realms too.

I should say its a similar issue as it happens on external and featured servers exept bran new featured servers

As I mentioned before, I am getting this problem specifically with the LAN visibility setting on my servers. I have reproduced this today in Version 1.26.43.1.

All other settings unchanged, setting LAN visibility to false results in clients not being able to connect. This result is the same with either default or custom port settings.

I found out this specific error log on my android phone when it crashed

I wanted to add that my iPhone iOS has been having various similar issues plus a few more.

• your device: iPhone, iOS 26.6.1

• Minecraft Bedrock version 1.26.44

• the specific errors I am getting (Bat, NetherNet, InitialConnection-41)

• that it happens on wifi AND cellular

• that it even happens on single-player worlds with no add-ons or experiments and with add ons.

  please let this be fixed soon cause all I want is to play.

THIS IS RESOLVED NOW in the latest version 26.44

This is not resolved in 26.44. There is no change in the details of this issue. Mojang when will you address this? You’re pos update broke my servers over 2 months ago.

Hmm… guys the servers are you trying to join and still getting the game closes itself issue, do the servers have playit.gg ip?

I don't know if this is important in 26.44 HOTFIX, I have tried to join every servers I have added in my game that aren't running online. The servers that has numerical ip or dns ip and probably not a playit.gg ip, shows nethernet error ( which is normal behaviour as the server isn't running ) but now only for joining the servers that have playit.gg ip , the game closes itself without showing nethernet error.

Update – Issue Still Reproducible on Bedrock 1.26.45.1

I tested the issue again using Minecraft Bedrock 1.26.45.1.

Unfortunately, the connectivity issue is still present.

However, the behavior has changed compared with previous versions.

Current Test

New Behavior in 1.26.45.1

When attempting to join the Bedrock Dedicated Server:

1. The client starts the connection attempt.

2. The connection/loading screen appears normally.

3. After a short period, the connection attempt stops.

4. The game returns directly to the main screen.

5. No error message or Error Detail screen is displayed.

This differs from the behavior observed in previous versions.

Previous Error Behavior

In earlier tests, the failure produced explicit error details:

Important Observation

The underlying connectivity problem therefore still appears to exist in 1.26.45.1, but the client no longer exposes the same diagnostic error information.

Previously, the failure was visible as:

• InitialConnection-34

• Prerequisites-32

In 1.26.45.1, the connection simply terminates and returns to the main screen without displaying an error.

This may indicate that the failure path or error handling has changed, rather than the underlying connectivity issue being resolved.

The issue has already been reproduced across multiple Bedrock client and Bedrock Dedicated Server versions, as documented in my previous comments on this ticket.

Please investigate whether the networking/handshake failure is still occurring internally in 1.26.45.1 and whether the diagnostic error screen is now being suppressed.

I can provide additional testing or logs if required.

## Update – Reproduced Again on 1.26.45 Using Default Port and zlib

I performed another controlled test using the latest Bedrock client and a more default-like Bedrock Dedicated Server network configuration.

The issue is still reproducible.

### Client

| Item | Details |

|---|---|

| Minecraft Bedrock | **1.26.45** |

| Device | **iPhone 12,5** |

| OS | **iOS 26.6.1** |

| Connection | **Wi-Fi** |

### Server Network Configuration Used for This Test

| Setting | Value |

|---|---|

| IPv4 Port | **19132** |

| IPv6 Port | **19133** |

| LAN Visibility | **true** |

| Compression Threshold | **1** |

| Compression Algorithm | **zlib** |

These settings were used specifically to rule out my previous custom port and Snappy compression configuration as possible causes.

### Result

The connection still fails.

The client now reports:

| Field | Value |

|---|---|

| Error Detail | **InitialConnection-13** |

| Transport | **RakNet:2169** |

| Result | **FAILED** |

So the problem is still reproducible even when using:

- the default Bedrock port **19132**

- default-style IPv6 port **19133**

- `enable-lan-visibility=true`

- `compression-algorithm=zlib`

- `compression-threshold=1`

This makes it unlikely that the issue is caused by my previous custom port or Snappy compression settings.

The failure is again occurring during the **InitialConnection** stage.

For comparison, previous tests produced:

| Test | Result |

|---|---|

| Older client + older BDS | **WORKS** |

| 1.26.40 client + older BDS | **InitialConnection-34 / RakNet:2168** |

| 1.26.40 client + newer BDS | **Prerequisites-32** |

| 1.26.45 client + default port/configuration | **InitialConnection-13 / RakNet:2169** |

I am attaching the screenshot showing the full `InitialConnection-13` error details.

This latest test further suggests that the issue is occurring inside the newer Bedrock connection/handshake path rather than being caused by a custom server port or compression configuration.

Yes in 26.45 HOTFIX update, I still get my game closes itself when I tried to join external servers that isn't running currently and are using playitgg dns ip

please someone tell me if this issue is happening to others and for playitgg dns ip servers or all types of dns ip servers that aren't running?

Additional Finding That May Help With MCPE-239705

I would like to share one finding from troubleshooting this issue that may be useful to developers and other affected users.

I was able to reproduce an InitialConnection failure even though the Bedrock Dedicated Server itself appeared to start normally.

The server reached:

Server started.

The UDP game port was open and the Bedrock server process was listening normally.

However, Bedrock/RakNet status requests were returning an empty response, and clients were still unable to complete the connection.

Finding in the Existing World

I inspected the affected world's level.dat and found:

LANBroadcast = 0

At the same time, the dedicated server configuration already contained:

enable-lan-visibility=true

This means the value stored inside the world did not match the server's LAN visibility configuration.

Before testing anything, I stopped the server and created a backup of level.dat.

I then changed only:

LANBroadcast = 0

to:

LANBroadcast = 1

After restarting the same dedicated server with the same world, the behavior changed immediately.

Before the Change

After the Change

No changes were made to the world database, gameplay settings, router configuration, firewall rules, or server port during this comparison.

The only change was the LANBroadcast value inside level.dat.

Why This May Be Relevant

This suggests that enable-lan-visibility=true in server.properties may not be sufficient in every affected world.

An existing world can apparently retain:

LANBroadcast = 0

inside level.dat, and in my test this affected the Bedrock/RakNet response even though the dedicated server reported that it had started successfully.

This may be worth checking in other reports of MCPE-239705, particularly when all of the following are true:

1. Bedrock Dedicated Server reaches Server started.

2. UDP 19132 is listening normally.

3. The client still fails during InitialConnection.

4. Bedrock/RakNet status requests receive no valid response.

5. enable-lan-visibility=true is already configured.

For affected users, it may be useful to inspect the world's level.dat and compare the stored LANBroadcast value.

A backup should always be created before modifying level.dat.

Additional Observation

During troubleshooting I also found that, on a system with more than one IPv4 address, the same Bedrock server could respond correctly through one local address while another address produced an InitialConnection failure.

This may be a separate networking behavior rather than the same root cause, but it may be useful for affected users to test each available server IP independently instead of assuming that all addresses will behave identically just because Bedrock is listening on 0.0.0.0:19132.

Conclusion

I am not claiming this is a universal fix for MCPE-239705.

I am sharing it because the before/after result was reproducible:

LANBroadcast = 0 → Bedrock/RakNet did not respond correctly

LANBroadcast = 1 → Bedrock/RakNet response started working

The most interesting part is that this occurred while:

enable-lan-visibility=true

was already set in server.properties.

Hopefully this provides another data point for investigating why some affected Bedrock Dedicated Servers report Server started while clients still fail during the InitialConnection stage.

I am not owner of every single minecraft servers (either bedrock only or geysermc, floodgateMc plugged in papermc servers) that I have added to my game. moreover, I have reached to a specific issue with new version of MCPE 26.45 hotfix.

I can't join servers that is hosted through playitgg service and connecting with its dns ip. But if I use numerical ip instead, the game doesn't crash, otherwise it crashes still (now it doesn't matter if it's running online or offline ;-; )