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.
kei taniguchi
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.