Recent Discussions
Server no longer able to be joined after unexpected shutdown.
Unanswered
Polish posted this in #questions
15 messages
0 views
PolishOP
Earlier this week my server computer unexpectedly shut down while I was away. I have no clue what caused it, but at this point I'm only left to assume it was a momentary power issue. Today I was able to start it back up again and was initially worried since the shutdown happened while my MC server was running.
Upon starting the server the logs indicate the server starts and is open, but no one can join it. Every attempt to connect ends in "Connection timed out: getsockopt" error. My first thought was world corruption, but I opened the world in a local version of Minecraft and there was no indication of corruption. I also tried starting the server with the --eraseCache and --forceUpgrade flags to fix any weird issues there but that didn't do it either. I'm pretty sure its not a networking problem since it seems pretty unlikely windows or my ISP changed network protocols on the same weekend my server computer shut down. What else could be the cause of this? Anything else I should be doing to diagnose the problem?
Upon starting the server the logs indicate the server starts and is open, but no one can join it. Every attempt to connect ends in "Connection timed out: getsockopt" error. My first thought was world corruption, but I opened the world in a local version of Minecraft and there was no indication of corruption. I also tried starting the server with the --eraseCache and --forceUpgrade flags to fix any weird issues there but that didn't do it either. I'm pretty sure its not a networking problem since it seems pretty unlikely windows or my ISP changed network protocols on the same weekend my server computer shut down. What else could be the cause of this? Anything else I should be doing to diagnose the problem?
Bluetick Coonhound
can localhost connect
within the same network
PolishOP
No. using the local ip from multiple computers also fails to connect
Bluetick Coonhound
disable windows firewall on the host entirely, then try again
also confirm it is actually the correct ip
your router may have assigned a new dhcp addr upon restoration of power
PolishOP
The host is a linux machine, sorry for the confusion there. My reference to windows was for the clients joining
I've confirmed that the local IP has remained unchanged. I can still ssh into the machine using that local ip
I've confirmed that the local IP has remained unchanged. I can still ssh into the machine using that local ip
Bluetick Coonhound
okay, check ufw if any
are you using a panel/docker?
PolishOP
I dont have ufw, the machine is a pretty much fresh install of rocky linux. It does have firewalld running but no rules have been configured.
I have the server process in a tmux session.
I have the server process in a tmux session.
Bluetick Coonhound
turn it off, I think it drops all by default when unconfigured
you could run a nmap at your server too
@Bluetick Coonhound turn it off, I think it drops all by default when unconfigured
PolishOP
This did it. I guess it must have been off when I setup the server and then turned itself on when I started the machine up today. Thanks for the help!
Bluetick Coonhound
Np
Loading...
Loading...