[BDS-12034] Unable to connect to dedicated server after update Created: 09/Mar/21  Updated: 03/Jan/22  Resolved: 03/Jan/22

Status: Resolved
Project: Bedrock Dedicated Server
Affects Version/s: 1.16.210
Fix Version/s: None

Type: Bug
Reporter: Edward L Platt Assignee: Unassigned
Resolution: Incomplete Votes: 13
Labels: None

Attachments: PNG File Screen Shot 2021-03-09 at 3.44.57 PM.png    
Issue Links:
Duplicate
is duplicated by BDS-12118 Players can not connect to Minecraft ... Resolved
is duplicated by BDS-12155 Unable to connect to world after Bedr... Resolved
is duplicated by BDS-12169 World is not ok Resolved
is duplicated by BDS-12194 Unable to connnect to server when usi... Resolved
is duplicated by BDS-12247 i can't join my server Resolved
is duplicated by BDS-12324 Backup bugs made in previous updates Resolved
is duplicated by MCPE-120167 server bug Resolved
is duplicated by MCPE-120240 Unable to connect to added servers Resolved
is duplicated by MCPE-120407 Unable to connect to world on Bedrock... Resolved
Confirmation Status: Community Consensus

 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.

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.



 Comments   
Comment by Maciej Piornik [ 03/Jan/22 ]

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

Comment by [MCQA] v-weszaj [ 05/Jul/21 ]

Resolving temporarily as Awaiting Response. Could you please attach any of the affected worlds to this ticket?

Comment by Judah Reeves [ 16/Apr/21 ]

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.

Comment by yamen estef [ 17/Mar/21 ]

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

Comment by Daniel Simmons [ 16/Mar/21 ]

I can also confirm that deleting level.dat and level.dat_old and letting the server rebuild them worked for me as well.  

Comment by Tommy Hernandez [ 13/Mar/21 ]

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).

Comment by Mike Parker [ 11/Mar/21 ]

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

 

Comment by Shanny Rachmandani [ 11/Mar/21 ]

Yes can confirm work, as mentioned Jeremy Shaw and Alex Ball. Thanks Guys

Comment by Alexa Ball [ 11/Mar/21 ]

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. 

Comment by Jeremy Shaw [ 11/Mar/21 ]

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.

Comment by Alexa Ball [ 10/Mar/21 ]

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. 

Comment by Shanny Rachmandani [ 10/Mar/21 ]

Same thing happen to me, hosted in apexhosting, update the server and this problem come, Please fix the issue.

Comment by Jeremy Shaw [ 10/Mar/21 ]

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.

Generated at Sat Jan 11 07:57:55 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.