Updated my Ubuntu 24.04.4 LTS servers from 1.26.30.5 to 1.26.31.1 and can no longer connect from my Windows client on the latest version. I get either SILVERFISH error or a connection timeout. I’ve verified that there is bi-directional UDP traffic between the client and server so it’s not a reachability issue. I tried disabling the allowlist and that did not fix it. The server logfile seems fine and shows a “Server started” log entry.
Comments 12
See BDS-23066 . TL;DR - try using raknet and connecting to the IPv6 port. That worked for me and got my 3 servers back to running.
Here’s all the steps I’ve tried. There is definitely something broken here.
Set up new vanilla server 1.26.31.1 with new vanilla world on port 19132. Works fine.
Change port of new vanilla server to 19134. Continues to work fine.
Add transport=raknet to my server.properties for my pre-existing server. Load my server with 1.26.31.1 on port 19134. Server loads but clients cannot connect.
Try changing the port to 19132. Server loads but clients cannot connect.
Tried connecting the IPv6 address and port. Client cannot connect.
I have had ‘Kelp’ and ‘Silverfish’ and ‘Timed Out’ errors. It appears, looking at packets, that when the initial ping is sent, the pong packet will often be terminated (or cut off).
This is starting to smell like a threading issue / race condition. I hope the team takes it seriously so it gets fixed soon.
Hi!
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response.
What settings in server.properties have you changed? Can you upload this file here?
Have you checked your network connection for stability issues that might affect online gameplay?
This ticket will automatically reopen when you reply. Thanks!
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
I was able to resolve this on my installation by setting transport=raknet and enable-lan-visibility=true. (I don’t actually want lan visibility enabled, but unless I set it to true connections can not be made to the server. I use the allowlist to control access so the lan visibility shouldn’t be a problem.)
This is on a commercially hosted bare metal server that I administer with stable networking.
I have same issue. In troubleshooting, if I change the server port back to default 19132 in the server.properties file, I can connect. When I change the port back to a non-default port, I can no longer connect.
Running on default port is not an option for my server.