Summary
Blaze error occurs when trying to rejoin a previously saved world after a multiplayer session (LAN) on Minecraft Bedrock (Android). It works fine before the first multiplayer session, but fails after.
Steps to Reproduce
Create a new world on Android device A.
Join from Android device B via LAN (different Xbox account).
Play together, then exit and save the world.
Reopen the world on device A.
Device B sees the world but gets Blaze error when trying to join.
Additional Info
Occurs on multiple devices with the latest available Android version on each device: Samsung S25 and Samsung S20FE
Each device is online and and logged in with different Xbox accounts
Xbox account settings confirmed to allow multiplayer (At least one of the used accounts is a kids account)
You can play with people outside of Xbox Live
You can join multiplayer games
You can create and join clubs
Multiplayer settings in world confirmed enabled
Deleting cache, restarting app, device or wifi does not fix the issue
Once a world is affected there is no way to fix it, even copying the world does not help
I can always create a new world and am able to join without issues the first time.
Linked issues
is duplicated by 1
Attachments
Comments 7
Hi!
Thank you for your report!
Could you please provide more details or any relevant media files?
Could you try to reproduce the issue on the newest update?
Can you record a video or take a screenshot of the issue and upload it?
Please contact https://help.minecraft.net/hc/en-us for assistance and refer to this ticket by providing a link.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
I have the same issue as identified by the original author. I have Minecraft on two Android phones (both using version 26.23), using different Microsoft accounts, and the first time I create a game on the first device (A), I can connect sucessfully from the second device (B). Device B may disconnect and connect again in the same world, but once the host device (A) closes the world and reopens it, the second device can no longer connect to the same world, and the Blaze error show on device B’s screen.
Error attached (messages in Portuguese)
This issue has been reviewed by our team.
Please add new, relevant information if it helps us understand or reproduce the issue. To show that you’re affected, use the vote feature rather than commenting.
If a fix is implemented, it will be listed in our official changelogs.
For major outages or urgent assistance, visit the Minecraft Help Center.
Hi!
I have a similar issue with my 2-year-old world. Not sure if I need to open a new ticket as this might be similar:
I am getting this error (code: Blaze) when signing into a certain world. The world is ran on a windows machine and I’m trying to log into it with a PS5/iPhone which has a different MS account on it. Through all the suggested troubleshooting on the website, I still cannot join this world. However, when I try to join any other world, I am able to join. I have no idea why the world of interest behaves any differently.
I should note that I did not edit any world settings, LevelDB data or meddled with the world in any way.
I have been in touch with the Minecraft tech support for months now (love you Alfred), since April 2026. Initially, I played with my gf using the same MS account and our gamertags would be “Gamertag” and “Gamertag(2)”. I started experiencing this issue with the release of the Tiny Takeover update. As I was told, the “Gamertag(2)” is no longer accessible and all progress is lost due to the new MS Policy stating that no more than one device may run the MS Account at the same time. Fine, progress lost for one but I wanted to join with the other account to continue playing together. This was impossible even with a different MS acoount that we created after the update.
I tried reinstalling the game, checked all network settings, all account settings, literally all you could think about.
After several game updates, the issue persists.
Please let me know if there is anything else I can do.
Dima
PSS. I was able to join the world when exporting the world and clearing player data. This obviously is sub-optimal since all items and pet ownership are gone. Unfortunately, simply exporting the world and keeping the data did not help. Perhaps, the issue lies within the player data somewhere. No idea
I am experiencing the identical problem and receiving the 'Blaze' error code as well. Despite following all general troubleshooting procedures, I can only successfully connect to multiplayer for the first session. From the second attempt onwards, it no longer works. For context, I am using two iPads on a LAN connection. I would appreciate any advice on how to resolve this!
Actions Taken So Far:
Reinstalled the App: Performed a clean install of Minecraft on both iPads.
Account Refresh: Signed out and signed back into Microsoft accounts.
Network Permission: Confirmed "Local Network" access is enabled in iOS privacy settings.
Privacy Settings: Disabled "Private Wi-Fi Address" on both devices to ensure consistent MAC addresses.
Device Identity: Renamed the iPads to refresh device identification on the network.
Direct Connection Attempt: Tried connecting manually via IP address, but encountered error code "U-000".
Suspected Causes Based on Error Logs:
Session Persistence (Ghost Session): The "Blaze" error with "InitialConnection-44" suggests that the host device is failing to terminate the previous session correctly.
Client ID Conflict: Error logs show that while the WorldSession ID changes with each new world, the Client ID (1BF734A...) remains identical. This indicates the host may be rejecting the guest because it perceives the "new" connection as a duplication of a still-active previous session.
Authentication Handshake Failure: The "Guardian" and "Blaze" codes, specifically under Transport: NetHerNet:898, point to a failure in the peer-to-peer handshake process, likely due to cached authentication tokens that are no longer valid.
Network Protocol Lockdown: It is possible that the router or iPadOS is blocking subsequent peer-to-peer requests after the initial successful connection as a security measure.