I have a Minecraft server (1.10.2) set up that I'm using for verification of MC accounts for a website of mine. The idea is that I have a script checking the server logs so that when someone joins, it immediately kicks them with an appropriate message (i.e. giving them a verification code or something).
That all seems to work server-side; someone connects, the /kick command is sent, they're kicked. Good. But when my testers try and connect to the server from outside the network, they don't get a /kick message. The server logs say they do, but they report that they're getting a generic "java.IOException: an existing connection was forcibly closed by the remote host". That means they're not getting their verification codes, which is a major problem.
So what would cause them to properly be kicked when they join, but not get the supplied /kick message? Especially since connecting to the server from the same machine works fine, it's only when connecting from outside the local network that this problem happens?
I have a Minecraft server (1.10.2) set up that I'm using for verification of MC accounts for a website of mine. The idea is that I have a script checking the server logs so that when someone joins, it immediately kicks them with an appropriate message (i.e. giving them a verification code or something).
That all seems to work server-side; someone connects, the /kick command is sent, they're kicked. Good. But when my testers try and connect to the server from outside the network, they don't get a /kick message. The server logs say they do, but they report that they're getting a generic "java.IOException: an existing connection was forcibly closed by the remote host". That means they're not getting their verification codes, which is a major problem.
So what would cause them to properly be kicked when they join, but not get the supplied /kick message? Especially since connecting to the server from the same machine works fine, it's only when connecting from outside the local network that this problem happens?