Expected action: With my dedicated MC Java Server up and running with the new 1.18 release, as noted in the startup logs, when I go to connect to the server via my client on a separate machine, I expect to click on the link to the server, wait a moment while it connects, and then land in the world. As happened last night, while still on 1.17.
Actual action: ...when I click on my private server listed in my client, the connection screen loads, waits a few moments as it tries to connect, and then returns this error:
"Failed to connect to server
Connection timed out: no further information"
Is reproducible: Yes. This problem is reproducible on two different laptops.
Attempts to resolve: I have already searched and found the "fixed for 1.17" thread that people are being pointed to, and like the comments from today after trying all of Mojangs tips, no, it is not fixed. This is not a firewall issue. This is not a JDK issue. This is something else...
Comments 2
Thank You, will do that.
But, the issue is not "invalid", it is most very valid and has been reported by how many people? The problem here is, which channel it was reported to. Proper terminology is key to a successful Jira ticket, or at least that's what've I've been trying to do at work, for years.
Thank you for your report!
However, this issue is Invalid.
This is a technical support issue; this site is for bug reports only. We do not have the resources to provide you with technical support.
Please contact Community Support for assistance and refer to this ticket (e.g. "I have reported this issue on Mojira as MC-XYZ.").
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki