Minecraft server firewall port forward issue...

[Quarke]

I am currently running a Minecraft server network on a computer with ports 25565, 25504, and 25563. I can join the server from the ipv4 address on the computer but, with all the necessary ports enabled (Inbound & Outbound) I can't connect from other computers. I have tried uninstalling my security software and disabling the windows firewall.

[Quarke]

yes

[Quarke]

3 minutes ago, wONKEyeYEs said:

Is the computer that you can't join on the same local network?

yes

[Eigenvektor]

1 minute ago, Quarke said:

yes

Start the Minecraft server, then open the command line and enter

netstat -ano | find "LISTEN"

Do the Minecraft server ports show up in that list?

[Quarke]

1 minute ago, wONKEyeYEs said:

The you used the IPv4 address that looks like 10.0.0.xxx?

 

It looks like:  IPv4 Address. . . . . . . . . . . : 172.28.16.1(Preferred)

[Quarke]

Just now, Eigenvektor said:

Start the Minecraft server, then open the command line and enter

netstat -ano | find "LISTEN"

Do the Minecraft server ports show up in that list?

yes

[Eigenvektor]

Just now, Quarke said:

yes

Does it show up as e.g. 0.0.0.0:25565 or 127.0.0.1:25565?

[Quarke]

2 minutes ago, Eigenvektor said:

Does it show up as e.g. 0.0.0.0:25565 or 127.0.0.1:25565?

  TCP    [::]:25563             [::]:0                 LISTENING       16164
  TCP    [::]:25564             [::]:0                 LISTENING       16164
  TCP    [::]:25565             [::]:0                 LISTENING       20556

[Quarke]

2 minutes ago, wONKEyeYEs said:

If your on the same local network open Command Prompt on the server and type ipconfig and choose the IPv4 Address that resembles 10.0.0.xx.

there isnt one?

[Eigenvektor]

Just now, Quarke said:

  TCP    [::]:25563             [::]:0                 LISTENING       16164
  TCP    [::]:25564             [::]:0                 LISTENING       16164
  TCP    [::]:25565             [::]:0                 LISTENING       20556

That would mean it's listening on IPv6, not on IPv4

[Eigenvektor]

9 minutes ago, wONKEyeYEs said:

If your on the same local network open Command Prompt on the server and type ipconfig and choose the IPv4 Address that resembles 10.0.0.xx.

Why would there need to be an IP address in the 10.x.x.x range? You know that there are three different possible private ranges, right?

 

10.x.x.x

172.16.x.x – 172.31.x.x

192.168.x.x

 

~edit: If there are no listening ports for IPv4, then that might explain the issue. You could try disabling the IPv6 stack in Windows, in the hope that forces Minecraft to actually listen on IPv4. Otherwise you could try launching it like this:

java -jar -Djava.net.preferIPv4Stack=true <path-to-minecraft.jar>

 

[Quarke]

14 minutes ago, Eigenvektor said:

Why would there need to be an IP address in the 10.x.x.x range? You know that there are three different possible private ranges, right?

 

10.x.x.x

172.16.x.x – 172.31.x.x

192.168.x.x

 

~edit: If there are no listening ports for IPv4, then that might explain the issue. You could try disabling the IPv6 stack in Windows, in the hope that forces Minecraft to actually listen on IPv4. Otherwise you could try launching it like this:

java -jar -Djava.net.preferIPv4Stack=true <path-to-minecraft.jar>

 

IPv4 Address. . . . . . . . . . . : 192.168.0.30(Preferred)

and for "java -jar -Djava.net.preferIPv4Stack=true <path-to-minecraft.jar>" which jar?

I have a bungeecord jar and two other minecraft jars.

[Eigenvektor]

3 minutes ago, Quarke said:

IPv4 Address. . . . . . . . . . . : 192.168.0.30(Preferred)

and for "java -jar -Djava.net.preferIPv4Stack=true <path-to-minecraft.jar>" which jar?

I have a bungeecord jar and two other minecraft jars.

How are you starting the Minecraft server right now? Continue to use whatever jar you're using for that. The only thing that should change is that you add the "-Djava.net.preferIPv4Stack=true" to it.

[Quarke]

1 hour ago, Eigenvektor said:

How are you starting the Minecraft server right now? Continue to use whatever jar you're using for that. The only thing that should change is that you add the "-Djava.net.preferIPv4Stack=true" to it.

I run the bungeecord jar through terminal. Then I run each docker container (with the two other servers).

[Eigenvektor]

7 hours ago, Quarke said:

I run the bungeecord jar through terminal. Then I run each docker container (with the two other servers).

Oh, you're running the server in Docker. Well that could explain why it's only available on the host. If you run a Docker container you need to configure it to make the port available to others. How are you starting the containers?

[Quarke]

9 hours ago, Eigenvektor said:

Oh, you're running the server in Docker. Well that could explain why it's only available on the host. If you run a Docker container you need to configure it to make the port available to others. How are you starting the containers?

Through the docker desktop app.

Previously I ran this on a mac mini and I had no problem (with the exact same containers)

[Eigenvektor]

4 minutes ago, Quarke said:

Through the docker desktop app.

Previously I ran this on a mac mini and I had no problem (with the exact same containers)

The default network options for Docker containers on a Mac might be different. Not too familiar with the Docker desktop app, I usually run Docker containers using a docker-compose.yml. In any case, you should probably check if there are some type of network settings for the container where you can enable/disable opening ports to the network.

 

But as you said previously, you could see open ports, the only issue was the those ports where only open for IPv6, not IPv4. So you may want to explore disabling the IPv6 stack on Windows, then restarting the Docker container to see if it is now listening on IPv4 instead.

[Quarke]

7 minutes ago, Eigenvektor said:

The default network options for Docker containers on a Mac might be different. Not too familiar with the Docker desktop app, I usually run Docker containers using a docker-compose.yml. In any case, you should probably check if there are some type of network settings for the container where you can enable/disable opening ports to the network.

 

But as you said previously, you could see open ports, the only issue was the those ports where only open for IPv6, not IPv4. So you may want to explore disabling the IPv6 stack on Windows, then restarting the Docker container to see if it is now listening on IPv4 instead.

I'll try that. Should I still run the terminal commend for the bungeecord server? It isn't on docker.

[Quarke]

21 hours ago, Eigenvektor said:

How are you starting the Minecraft server right now? Continue to use whatever jar you're using for that. The only thing that should change is that you add the "-Djava.net.preferIPv4Stack=true" to it.

I tried disabling ipv6 stack on windows and I ran the bungeecord jar with the previous command you sent. It still doesnt work.