Been facing the issue since 19 June 2020. Prior, had no connection issues and I own the Realm I am attempting to connect to.
I have checked my firewall settings, internet connection stability and network adapters/drivers, all of which seems in order with no current nor recent abnormalities.
My members are facing the same issue as well.
EDIT: Aside from being unable to connect to my realms, I am also unable to close it nor download world backups. Attempting to do so will result in being stuck on "closing realms" and having a connection timed out respectively.
Linked issues
duplicates 1
Attachments
Comments 5
I have a similar issue as well. Since 20 June, noticed approx 10am Kuala Lumpur time
slightly different error message
io.netty.channel.ConnectTimeoutException: connection timed out
If further clarity helps, I am in Singapore and have received the following excerpt from Microsoft Minecraft Help:
"I'm sorry to hear that you're having trouble with your game. Unfortunately, we are currently limited mostly to account issues and billing and our current tech support is limited at this time.
Unfortunately we don't have any official troubleshooting information, I can link you to at this time, but a quick search around the internet makes it look as though this has something to do with firewall settings on the user side. I can assure you our engineers are working on it." - 'Felix'
Which feels like a total brush off and a quick search around the internet makes it look as though this has something to do with firewall settings on the server side.
Thank you for your report!
We're tracking this issue in REALMS-4006, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki – 📖 FAQs
i face exactly the same issue since 19/6, but not solve yet until today