When I try to connect with any Realm, it kicks me out after maybe 30 seconds. "Internal Exception: java. net. SocketException: Connection Reset" appears on the screen.
I tried a few fixes, like changing the DNS server and renewing the system's IP. The OpenJDK Platform binary is allowed through the firewall, I don't have Hamachi or any kind of VPN and antiviruses, I also tried reducing render distance. Can't change to the previous release, because the Realms are on 1.18. Reinstalled Java, and Minecraft a couple of times. I have a PC, which doesn't have a wireless network interface card, so can't connect to the hotspot, but my Internet connection is stable: ping 12-17ms, download 89Mb/s, and upload 50Mb/s. Nothing works.
I've seen the MC-227913 issue, did everything, still doesn't work.
Linked issues
duplicates 1
Attachments
Comments 4
Same thing is happening to me, I have approached Community Support and they have also been pointing back to MC-227913. If you have had your issue resolved any and all information would be greatly appreciated.
Unfortunately, I have to resolve this ticket as a duplicate. This isn't an issue specific to Realms, so if none of these tips are working then your best bet would be to contact community support and try to get help there.
Thank you for your report!
We're tracking this issue in MC-227913, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as invalid. Please take a look at the parent ticket (MC-227913) and see if an explanation is provided there in the description of the ticket or in the comments for why this issue is invalid.
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:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki – 📖 FAQs
-- I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Duplicate of MC-227913. If following the provided instructions attached to this ticket didn't fix anything, please approach Community Support.