After updating our Windows VPS to version 1.16.210.05 we're unable to connect to the world that was running. We can connect if we roll back to 1.16.200.02 (the previous version we were using) or if we let the server generate a new world.
Here's a link to our most recent backup of the world data.
Linked issues
Comments 4
I have further tested and identified an oddity. I believe this is related to the fact that my world does not complete a PING or give a number of connected users. I have a creative server running on a non-default port, that instance does respond to PING and gives a number of connected users. I am able to connect to that instance.
If I move too quickly through the client screens so that the PING steps have not completed, the client fails to connect to the world. If I wait until the ping has completed then it will connect successfully.
I am not able to make the primary world respond to a PING, if I move the world to the connectable server instance it no longer responds to PING which indicates that something related to the world makes it unable to respond to PING.
SUCCESS!! I was able to get the world to start responding to PINGs by deleting the directory worlds/<worldname>/db/lost and then copying the remaining files in worlds/<worldname> into a newly created world file, overwriting the contents.
Once the server instance was responding to PINGS and listing the number of connected users the client was able to connect.
This suggests that this ticket should be split into 2 issues.
1) The client doesn't attempt to connect if the server is not responding to pings. This is a change from previous versions where the client would attempt to connect even if the ping didn't succeed.
2) The cause of the server not responding to PING and the correct cleanup steps for the <worldname>/db/lost/ directory contents.
Thank you for your report!
We're tracking this issue in BDS-12034, 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:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
-- I am a bot. This action was performed automatically! Please report any issues on Discord or Reddit
I have the same issue on IOS. I am unable to connect to any dedicated servers.
Additionally the error message appears almost immediately as if there is no waiting for a timeout to occur. In the past attempting to connect to world would take a few seconds, but after the update to 1.16.210.05 the unable to connect to world happens immediately.
I attempted all the normal debugging, I deleted and recreated the additional server entry, I deleted and re-downloaded minecraft and I restarted the ipad several times. I validated the IOS networking permissions to allow all networks.
I was able to connect to the lifeboat game server and create a new local world successfully, but all attempts to connect to all dedicated servers fails.
The device is an IPAD Pro 2019 with the latest updates.