BDS-12034Unable to connect to dedicated server after update
After updating both android client and ubuntu server to 1.16.210, I get an "unable to connect to world" error when trying to connect to my private server. I've tried rebooting with no luck.
Additional info: Creating a new world works, so the problem is only with pre-1.16.210 worlds. My world had originally been imported from realms.
Update 3/11/2021: Based on the comments, I tried deleting level.dat (after backing up) and allowing the server to rebuild. That fixed the problem for me.
Linked Issues
is duplicated by10
BDS-12118Players can not connect to Minecraft Bedrock Edition Server after update.DuplicateBDS-12155Unable to connect to world after Bedrock Server 1.16.210.06 UpdateDuplicateBDS-12169World is not okDuplicateBDS-12194Unable to connnect to server when using map from Old versionsDuplicateBDS-12247i can't join my serverDuplicateBDS-12302Can't join In 1.16.210DuplicateBDS-12324Backup bugs made in previous updatesDuplicateMCPE-120167server bugDuplicateMCPE-120240Unable to connect to added serversDuplicateMCPE-120407Unable to connect to world on Bedrock dedicated server after updating to 1.16.210.05DuplicateAttachments1
Comments13
History21
Changed description:
After updating both android client and ubuntu server to 1.16.210, I get an "unable to connect to world" error when trying to connect to my private server. I've tried rebooting with no luck.
Additional info: Creating a new world works, so the problem is only with pre-1.16.210 worlds. My world had originally been imported from realms.
Changed summary:
Changed description:
After updating both android client and ubuntu server to 1.16.210, I get an "unable to connect to world" error when trying to connect to my private server. I've tried rebooting with no luck.
0Additional info: Creating a new world works, so the problem is only with pre-1.16.210 worlds. My world had originally been imported from realms.
Update 3/11/2021: Based on the comments, I tried deleting level.dat (after backing up) and allowing the server to rebuild. That fixed the problem for me.
Added is duplicated by link: BDS-12118Players can not connect to Minecraft Bedrock Edition Server after update.Duplicate
Added is duplicated by link: BDS-12155Unable to connect to world after Bedrock Server 1.16.210.06 UpdateDuplicate
Added is duplicated by link: BDS-12169World is not okDuplicate
Added is duplicated by link: BDS-12194Unable to connnect to server when using map from Old versionsDuplicate
Added is duplicated by link: BDS-12247i can't join my serverDuplicate
Added is duplicated by link: MCPE-120167server bugDuplicate
Added is duplicated by link: MCPE-120407Unable to connect to world on Bedrock dedicated server after updating to 1.16.210.05Duplicate
Added is duplicated by link: MCPE-120240Unable to connect to added serversDuplicate
Confirmation Status: Unconfirmed → Community Consensus
Added is duplicated by link: BDS-12302Can't join In 1.16.210Duplicate
Added is duplicated by link: BDS-12324Backup bugs made in previous updatesDuplicate
Resolution: Unresolved → Awaiting Response
Resolution: Awaiting Response → Unresolved
Resolution: Unresolved → Incomplete
Same thing is happening to me, on my Windows server. If I wipe out our world and start anew, the server works. It's only if I use our existing world that the server refuses to work.
World was originally a realm, created after the Nether update. I tried zipping the world, renaming the extension, and importing into Minecraft Bedrock client. Playing the world a bit, the exporting it, and extracting the *.mcworld into a new minecraft bedrock server setup. World is currently just under 500MB.
Still doesn't work. Same error, Unable to connect to world. No log shown of any connection attempt - the client is ejected almost instantaneously.
Same thing happen to me, hosted in apexhosting, update the server and this problem come, Please fix the issue.
Same issue with my Windows server. Fresh world file works fine but using my month old server file refuses to let anyone join despite being turned on. Just the same 'Unable to connect to world' almost immediately.
Following up. Someone on a discord recommended deleting the level.dat file and letting the server rebuild it at startup.
I made a copy of the file (and took another backup of the whole world, for that matter), deleted level.dat, and startup up the server. World now works.
Can confirm. Deleting both level.dat and level.dat_old files and letting the server rebuild them made the server work. Make sure to take a backup first though, in case anything goes wrong.
Edit: Make sure you save the seed in the server properties file, otherwise the server will load new chunks on a random seed that isnt the one you started on, causing a strange chunk shuffling effect.
Yes can confirm work, as mentioned Jeremy Shaw and Alex Ball. Thanks Guys
For anyone directed here trying to fix a 1.16.210 Bedrock client being unable to access a Java edition server running the Geyser plugin, a new release of the Geyser plugin (#636) was made on 9th March that fixes the issue:
https://ci.opencollab.dev//job/GeyserMC/job/Geyser/job/master/636/changes
The deleting level.dat and level.dat_old workaround seems not to have worked for me. I still get "Unable to connect to world". My server is linux, and the clients I've tried are both Windows 10 PC and Nintendo Switch (via bedrock connect).
I can also confirm that deleting level.dat and level.dat_old and letting the server rebuild them worked for me as well.
me too , i use the official server software (bedrock) and on windows 10 and deleting the level.dat and level.dat_old files didn't work for me aswell
I have a survival world where deleting level.dat worked.
I have a creative where it doesn't. I copied the world and loaded it into minecraft as a local world. Save and Quit. Copied it to the BDS. Deleted the level*.dat. Started the server. I'm unable to connect to it.
Resolving temporarily as Awaiting Response. Could you please attach any of the affected worlds to this ticket?
Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki