Need assistance with your server issue. Please let me know what you're experiencing.

F5F Stay Refreshed Power Users Networks Need assistance with your server issue. Please let me know what you're experiencing.

Pages (2): Previous 1 2

entech
Member

210

12-13-2016, 08:42 PM

#11

I can send a quick message.

entech

12-13-2016, 08:42 PM #11

I can send a quick message.

Neonfluzzycat
Member

199

12-17-2016, 10:17 PM

#12

You run a traceroute to the specific IP address and port number. This will show the path the data takes and indicate where the connection breaks down.

Neonfluzzycat

12-17-2016, 10:17 PM #12

You run a traceroute to the specific IP address and port number. This will show the path the data takes and indicate where the connection breaks down.

zMadeus
Posting Freak

755

12-28-2016, 10:42 AM

#13

Error encountered while trying to locate the intended system name.

zMadeus

12-28-2016, 10:42 AM #13

Error encountered while trying to locate the intended system name.

Ernin
Junior Member

12-29-2016, 06:32 PM

#14

I run a starbound server on port 21026 and it functions properly. I attempted to start a Minecraft server on that port, but the website indicates the port is closed. The server itself isn’t running. When I set up the starbound server, the port appeared open or accessible. Updated August 6, 2018 by EnderGaming

Ernin

12-29-2016, 06:32 PM #14

MavrosGR
Senior Member

579

12-30-2016, 12:27 AM

#15

You have the device/server port forwarded and the server is active. The Linux machine reports the server is listening on the port, but the public side shows it as closed. This issue occurs only with your Minecraft server and not with a Starbound one.

MavrosGR

12-30-2016, 12:27 AM #15

styytyttyy
Junior Member

01-05-2017, 09:11 PM

#16

I discovered the answer to my issue! The issue wasn't with the router; it was adding an exception to the iptables on my Lubuntu machine so it could communicate beyond the local network.

styytyttyy

01-05-2017, 09:11 PM #16

I discovered the answer to my issue! The issue wasn't with the router; it was adding an exception to the iptables on my Lubuntu machine so it could communicate beyond the local network.

Pages (2): Previous 1 2