Just recently I updated my Minecraft servers to 1.19.2. The java servers ran just fine after update, but I noticed I was unable to join the bedrock one.
So I tried going back to the previously working version of the bedrock server and tried connecting using my daugthers PC (which hadn't updated the minecraft client yet), but to no avail.
The client shows "connecting to multiplayer game" for a couple of minutes and then it fails showing "Connection timed out" and "Unable to connect to world". Same issue as with 1.19.2.
I even went so far to reinstall the whole VM with a newer Ubuntu version.
The server was initially a Ubuntu 20.04 VM and was updated to 22.04 (were I also had to download an earlier libssl to even get the bds server going).
The BDS server was running fine earlier this year. No issues connecting either PC client or Android clients over the internet or lan. The ports are forwarded correctly (since as I mentioned, it worked previosuly) and the ports are allowed access in UFW.
VM Host is running Windows Server 2016.
I tried installing the BDS server on a Windows 2016 VM instead and moved my world there (had to change the port forwards to that server ofc.) and that worked like a charm directly. Though that VM was not intended for hosting a game server.
Seems like this issue could be traced down to the Ubuntu version of BDS.
Linked issues
Comments 5
There really isn't much to see in the server log.
Dedicated_Server.txt
[2022-08-17 20:00:31:911 INFO] Starting Server
[2022-08-17 20:00:31:911 INFO] Version 1.19.20.02
[2022-08-17 20:00:31:911 INFO] Session ID eb1ca087-d214-431e-8ee5-60b5ef16b1e6
[2022-08-17 20:00:31:911 INFO] Level Name: Bedrock level
[2022-08-17 20:00:31:914 INFO] Game mode: 0 Survival
[2022-08-17 20:00:31:914 INFO] Difficulty: 2 NORMAL
[2022-08-17 20:00:32:999 INFO] Content logging enabled. Writing log to: ContentLog_Wednesday2022_August_17{}_20_00_32
[2022-08-17 20:00:32:999 INFO] opening worlds/Bedrock level/db
[2022-08-17 20:00:32:803 INFO] IPv4 supported, port: 19132
[2022-08-17 20:00:32:803 INFO] IPv6 supported, port: 19133
[2022-08-17 20:00:33:252 INFO] Server started.
[2022-08-17 20:00:33:281 INFO] IPv4 supported, port: 56226
[2022-08-17 20:00:33:281 INFO] IPv6 supported, port: 55911
[2022-08-17 20:04:05:897 INFO] Server stop requested.
[2022-08-17 20:04:05:940 INFO] Stopping server...
I don't know if it helps, but if i run nmap on the Java servers, they appear as "State Open", while the BDS shows as "State Closed". Ports should however be opened in UFW and in my router.
Did some more digging into the RAKNET network traffic based on this: BDS-17401
A traffic comparison between with and without the KB5015807 shows that the MC Client sends an ACK (0xc0), it passes through the Hyper-V HOST/Server, the Ubuntu server sees the ACK and responds with it's own ACK, but that ACK is not passed through the Hyper-V Host back the the client.
Thank you for your report!
We're tracking this issue in BDS-17307, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 BDS Wiki – 📖 FAQs
Hi
Can you copy or make a screenshot of server log and paste/attach it here?
This ticket will automatically reopen when you reply.