I’ve got a couple issues, but lets run one thing at a time.
The first is that I created a vanilla 1.11 instance and attempted to connect
Failed to connect to the server
Internal Exception: java.IOException: An existing connection was forcibly closed by the remote host
Thinking it was an iptables issue (Ubuntu 16.04), I cleared out the filters, restarted server and client services, and received the same result.
Here’s my filters:
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT tcp -- anywhere anywhere tcp dpt:ssh
ACCEPT tcp -- anywhere anywhere tcp dpt:http-alt
ACCEPT tcp -- anywhere anywhere tcp dpt:8443
ACCEPT all -- anywhere anywhere
ACCEPT tcp -- anywhere anywhere tcp dpts:25568:25570
ACCEPT icmp -- anywhere anywhere
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
ACCEPT tcp -- anywhere anywhere tcp spt:ssh
ACCEPT udp -- anywhere anywhere udp spt:4445
ACCEPT all -- anywhere anywhere
I also installed vanilla 1.12.2, and was able to connect to it with no problem, even after I reset my iptables. So, I don’t think its a firewall issue since I can run vanilla 1.12.2, SSH, and FTP into the server just fine.
Nothing significant was recorded in the log, and a crash log was not created. I verified the client is running the latest version of 1.11.2, too.
Another odd thing occurred. I found the above issue after I was unable to get an instance of Forge 1.11.2 running. After getting vanilla 1.11.2 run for the first time for EULA and scaffolding, I ran the instance using the 1.11.2-recommended for the install, and then switched over to the -universal release. For some reason, the start button doesn’t want to start the instance.
For Forge, the /var/log/mineos.log shows the events. The error only shows if I don’t assign an IP address in the server.properties.
{"level":"info","message":"[ForgeCraft] 192.168.0.107 issued command : \"start\"","timestamp":"2017-10-03T03:34:17.351Z"}
{"level":"info","message":"[ForgeCraft] received request \"start\"","timestamp":"2017-10-03T03:34:17.354Z"}
{"level":"error","message":"Cannot bind broadcaster to ip ","timestamp":"2017-10-03T03:34:19.491Z"}
{"level":"info","message":"[ForgeCraft] 192.168.0.107 issued command : \"modify_sp\"","timestamp":"2017-10-03T03:36:48.686Z"}
{"level":"info","message":"[ForgeCraft] received request \"modify_sp\"","timestamp":"2017-10-03T03:36:48.691Z"}
{"level":"info","message":"[ForgeCraft] 192.168.0.107 issued command : \"start\"","timestamp":"2017-10-03T03:37:00.381Z"}
{"level":"info","message":"[ForgeCraft] received request \"start\"","timestamp":"2017-10-03T03:37:00.382Z"}
No further logs were created in the server, to include crash logs.
Here’s some system information:
npm: 3.10.10
nodejs: v6.11.3
java: openjdk version "9-internal"
git commit: d529e70
port: 25568 - 1.11.2
port: 25569 - 1.12.2
port: 25570 - Forge 1.11.2
My end state goal is to migrate from my other server to this more robust hardware. Even after failing Forge above, I tried to bring a copy of an archived server over to this instance, but I was presented with the same results.
UPDATE:
I created a Forge server using the latest build, but I still received no response from the start button.
I also compared the file structure and properties between both servers (old and new) /var/games/minecraft. after making the few changes (the MC servers were being built with a custom group on one and the minecraft group on the other), I ran systemctl restart mineos and tested, resulting the same.