Bug Report – online-mode=true blocks client login after moving a world to a newer BDS build
Titleonline-mode=true prevents authentication in LAN (Possibly online as well, untested) when a world from an older BDS version is copied to a newer BDS version.
Reproduction Steps (no workaround)
Run an older BDS build (e.g., 1.19.x) and create a world, wait till saved, Shut the server down.
Install a newer BDS build (e.g., 1.20.x or 1.21.x). copy over
server.properties(must have online-mode=true).Copy only the old world directory (the one created in step 1) into the new server’s root folder. IMPORTANT, Do not start the new server beforehand.
Start the new BDS instance.
From a Bedrock client, attempt to join the server.
Observed Result – The client receives an authentication failure (NetherNet/“failed to authenticate” error) and cannot connect.
Troubleshooting:
Logging out of minecraft, launcher, Microsoft store does not help here (Your NetherNet advice) restarts, reboots consistent root folder names, don't help either.
If you turn online-mod=false you can log in via the LAN again. But this will obviously break online authentication which I want. This step points to online authentication and world validation as the issue area.
Expected Result – The server should accept authenticated connections to the migrated world when online-mode=true.
Work‑around
There is a clue in this workaround I found, before you copy your world to the new server, Start the new BDS once to generate a fresh vanilla world, confirm a successful login with
online-mode=true, then stop the server, move your old named world folder into the freshly generated worlds folder and put your server.properties file pointing to it in the root folder and restart. This sequence allows authenticated connections to the migrated world.
hopefully this will help you identify which Auth or validation step causes the issue.
I would like to say your own docs report you should be able to move worlds between versions.
Attachments
Comments 5
In a way, i’m sorry to say this, I tried to recreate the error today as i have previously, and I can not reproduce it, even with the exact same steps, this means the workaround I thought i had found is probably coincidence and it is more likley that I hit a timing issue with my microsoft user auth (although at the time i had logged out and back in on both server and client which should have covered this scenario)
The only other factor i did not try was my childs user account logging in after world move across versions. I will keep this in mind if it happens agai.
Sorry for the hassle, As i can no longer reproduce the error please close this ticket. If it happens again on the next version switch I will open a new ticket and try again to track it down then.
I cannot join my server over the internet with online mode on. However it does work on a local network. I tried the above workaround and it didn’t seem to work. It did work a few months ago. As soon as I disabled online mode, it then works over the internet so it is not a firewall issue.
Edit: it worked that one time, I have not been able to get working again. It works on local network, ipv4 and ipv6. Doesn’t work on wan ipv6, I cannot test ipv4.
Sorry Kanada, my workaround turned out to be coincidence with some background online Auth mechanism. I can't recreate my original issue again.
We know the problem is to do with Microsoft inline authentication, when you switch to online_mode=false, it bypasses Microsoft authentication, which is why you can access your world again. I would love to know if there is some kind of cached record of authentication against new BSD world versions.
I would follow the original advice for the nethernet error. Try logout of Minecraft, launcher, xbox, Microsoft store (try a vanilla BSD world with online-mode=true),.log back in on your client, then if that works try moving your world files over.
Looking through forums ,& past bug reports this issue keeps happening to BSD setups, it's just very hard to pin down exactly what part of the Auth chain is causing this.
Hi!
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response.
Can you upload the server files and share a link? The most suitable options are OneDrive or Google’s Drive.
This ticket will automatically reopen when you reply. Thanks!
Quick Links:
📓 Issue Guidelines –💬 Mojang Support –📧 Suggestions –📖 Minecraft Wiki