This is more specific to the Linux verson of BDS. Many Bedrock servers, inluding my own, automaticly update the server by using shell scripts to check for the latest version of BDS, then download the updated software and update the server if necessary. Since the release of the Preview version of BDS is on the same web page as the current versions, this caused many servers running BDS to inadvertently update to version 1.19.10.20.
Comments 8
Confirmed. My server running on Ubuntu shows 1.19.10.20 while the client version is still 1.18.3.1
Hopefully there's a way to revert this.
I found out that the best work around for this is to comment out the lines of code in your scripts that is responsible for updating the server until the Wild Update releases. You should be able to revert your server back to version 1.18.33 if you still have that version of BDS on your computer. As long as no one joined your server while in version 1.19.10.20, you should not have to roll back your world. If you are using the scripts created by TheRemote on Github, this issue is being tracked in more detail in his Github repository.
Also confirmed.. Server auto updated to 1.19.10.20, Client is unable to update to anything past 1.18.3x. No way to revert without original server files.. Original server files are not available to download.
Also can confirm. Tried installing beta version of clients but no go with connecting to server.
Have created several new servers all 1.19.10.20 some say beta.
Using linux bedrock through docker, my clients were broken too due to 1.19.x. I have fixed it now by selecting the 1.18.x server version.
Note: I'm using docker to run bedrock server and specifying the specific version as an environment variable using:
-e VERSION="1.18.33.02"
If you're not running docker, you need this version of the server for 1.18 clients:
https://minecraft.azureedge.net/bin-linux/bedrock-server-1.18.33.02.zip
Here's the full command in my case:
docker run -d -it --name mc_world3_positano -e EULA=TRUE -e VERSION="1.18.33.02" -p 19132:19132/udp --mount type=bind,source="$(pwd)"/bedrock-server,target=/data mc/world3_positano
I'm happy to show my whole Dockerfile if anyone needs it...
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response
Can you provide more details how to reproduce this issue? Does it occur after updating to 1.19.10?
Video would also be very helpful. You can record it and upload it here as attachment. If your video size exceeds 10 MB, you can use OneDrive or similar file hosting service and share link.
Also, just a reminder, to make your bug report as effective as possible, please try and include the following steps to reproduce the problem:
Steps to Reproduce:
1.
2.
3.Observed Results:
(Briefly describe what happens)Expected Results:
(Briefly describe what should happen)
If your ticket does not look like the example given here, then it's likely to be closed as incomplete.
This ticket will automatically reopen when you reply.
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
I would like to confirm, there is no option to connect to BDS as client is invalid ...