[MCPE-22228] Realm - Disconnected from Server Created: 02/Jun/17  Updated: 15/Dec/17  Resolved: 15/Dec/17

Status: Resolved
Project: Minecraft (Bedrock codebase)
Component/s: None
Affects Version/s: 1.1.0.55
Fix Version/s: None

Type: Bug
Reporter: Jackie Sasscer
Resolution: Cannot Reproduce Votes: 2
Labels: None

Issue Links:
Duplicate
is duplicated by MCPE-26121 Cannot connect to Realms Resolved
Confirmation Status: Unconfirmed
Platform: Phone - iOS - iPhone 6

 Description   

I have not been able to get into my realm since downloading the new MCPE update yesterday. I keep getting the alert "disconnected from server." After numerous failed attempts to get in, I deleted the MCPE app from my phone and reinstalled it, but this did not fix the problem. I also tried using different wi-fi networks, to no avail. I can get into Worlds fine, it's just Realms that's not working. I'm not the owner of the Realm, if that helps.



 Comments   
Comment by Dean Taylor [ 02/Jun/17 ]

I am having a similar issue. Using the windows 10 version though on my pc. my softwrae updated to 1.1 today when I openned it. Now whenever I try and connect to my friends realm it tries, goes past the syncing part and then "Disconnected from Server" all single worlds etc are fine just the realms are a problem.

Comment by Jackie Sasscer [ 02/Jun/17 ]

Thanks Jonathan and James. I just asked the realm's owner to update the app too. Seems like the logical solution.

Comment by James Hamilton [ 02/Jun/17 ]

I've had a similar issue too, Johnathan Hansel's comment actually makes a lot of sense because I can see how the owner not getting the update could cause this issue.

I made my own report here:
https://bugs.mojang.com/projects/MCPE/issues/MCPE-22157?filter=allopenissues
I would contact the owner of the server to let him/her know that they need to update.

Comment by Jonathan Hanzel [ 02/Jun/17 ]

I would contact the owner of the Realm this issue, but it sounds like the owner has not updated the Realm to 1.1

Generated at Sat Jan 11 15:34:06 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.