[BDS-249] "Unable to connect to world" when transfering Realm-Save to BDS Created: 18/Nov/18  Updated: 10/Feb/20  Resolved: 10/Feb/20

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

Type: Bug
Reporter: clarkx86 Assignee: Unassigned
Resolution: Invalid Votes: 3
Labels: None
Environment:

Client: Windows 10 64-bit (running MC Bedrock v1.7.1)

Server: rented dedicated server (running Version 1.7.0.13)


Attachments: PNG File Capture.PNG     PNG File Capture1.PNG     PNG File Capture2.PNG     PNG File Folder1.PNG     PNG File Folder2.PNG     PNG File Folder3.PNG    

 Description   

Me and my friends have been playing on a regular Realm for almost one year now and decided to switch to the Dedicated Server Software when it finally released. I downloaded the world-backup from the expired realm, set up BDS and uploaded the world-backup into the "worlds"-folder and configured my server.properties. Everything works, except when I set the level name to the world-backup. When I let BDS generate a new world it works flawlessly, but when I set the name to the world-backup, it only says "Locating server" and when I try to connect it says "Unable to connect to world". I re-downloaded the backup and re-uploaded it to my dedicated server multiple times, no strange letters or symbols in the world string and no sub-folders. Everything should work correctly, but it doesn't.



 Comments   
Comment by IonicEcko [ 10/Feb/20 ]

Could a mod please close this issue.

Comment by itzkakarot [ 19/Jan/19 ]

Copy your world to Win10 or mobile first.  When you see it in your list of worlds, click on the edit button next to it, click Multiplayer, and turn on "Visible to LAN players".  Should fix the issue.

Just want to confirm that re-enabling Multiplayer and the "Visible to LAN Players" switches on Win10 before copying to my BDS solved this one for me, thanks @FollowThisLogic. I had to toggle both switches because I've noticed that when downloading Realm saves to Win10 the Multiplayer switch is toggled on automatically but the underlying setting is not really enabled. If you don't toggle the Multiplayer switch off/back on, the "Friends" drop down is disabled (which is strange) and no players being able to join the game.

Comment by FollowThisLogic [ 09/Jan/19 ]

Copy your world to Win10 or mobile first.  When you see it in your list of worlds, click on the edit button next to it, click Multiplayer, and turn on "Visible to LAN players".  Should fix the issue.

 

I would understand if this isn't a fixable thing, but it should absolutely be included in the BDS howto HTML.

Comment by clarkx86 [ 05/Jan/19 ]

Unfortunately not. I made sure that the world name definitely matched and tried with other worlds too, which seemed to work. It was only our realm save that I downloaded (unmodified) directly from Minecraft Bedrock Edition Windows 10 which didn't work. I'm currently still using Realms because I still could not get it to work with BDS and our world.

Have a great day,
DigitalClark

Comment by Michael Gill [ 05/Jan/19 ]

Did you ever find a resolution? You do know that the world folder has to match the world name in the properties file?

Comment by clarkx86 [ 28/Nov/18 ]

Thank you for your answer! Yes, I will attach them with this comment!

 

There are 281 .ldb files, counting from 167279.ldb to 215069.ldb. The world is straight downloaded from our realm and pasted into the BDS-worlds-folder.

I actually had success joining the server when renaming the 215070.log and MANIFEST-215068 files to the default names of a freshly generated world using BDS, but it wouldn't show the MOTD and player count in the server browser, and also would move the files into an "old"-folder or something like that after a couple of seconds/ minutes, re-generating the 215070.log and MANIFEST-215068 again and the issue accured all over again. **

 

Thanks so far and have a great day!

Comment by Marek Jablonski [ 28/Nov/18 ]

Do you have a screenshot of the files inside the world folder?

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