-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AnnotatedConnectException: Connection timed out: no further information #129
Comments
Most likely this will be caused by something external to the container. FWIW I have almost an identical setup with microk8s, etc and was also seeing sporadic connection issues. In my case though, the server host itself was a WiFi hop away from ISP router due to physical constraints. I used I have since moved the host onto an Ethernet connection to router and issue went away. Sorry, I don't have solid advice but can commiserate. |
That's not the issue, since the server is connected to ethernet. My desktop, which has the same issue, is connected to the same switch as the server. I agree, I don't think the issue is with the minecraft server specifically, but I've only seen connection issues with the minecraft server. It seems like the messages are not being forwarded through the nodeport or something occasionally, but people who have connection to the server don't have any issues. |
The "TCP Port numbers reused" seems suspicious. I haven't seen that before. |
I believe that is just the TCP message retransmitting because there was no ACK response |
I'm getting the error in the title occasionally when trying to connect to the minecraft server I created using this chart. The server runs fine mostly. The cpu usage is lower than I would expect though, but it runs fine except that people have trouble connecting occasionally.
I am running the deployment on a single node microk8s server that I have port forwarded to a nodeport service. I have 80Mbps internet (though that doesn't seem to matter since I get the error on the same network), and the server has 16 threads with a max frequency of 3.7GHz (though it seems to run around 1.6GHz typically with only 2 mincraft servers on it)
The text was updated successfully, but these errors were encountered: