Forums Archived

This forum has been archived. No new posts can be made and no new users can sign up. It remains here for reference only.

Find the new forums here

Ubunto 20.04 Minecraft port won't open

  • 483 Views
  • Last Post 06 March 2021
piratemunky posted this 24 December 2020

OS Name/Version: Ubuntu 20.04

Product Name/Version: AMP Release "Europa" / v2.0.8.10, built 15/12/2020 17:08 with Docker enabled.

Problem Description: Minecraft port (25565) is Closed -- can't connect to Minecraft server!

Steps to reproduce:

  • Create and start new Minecraft Java edition.
  • Configure port forwards in external firewall.
  • Try to connect to server, getting "connection refused"

Actions taken to resolve so far:

  • Checked ampinstmgr ports PirateCraft [Info] AMP Instance Manager v2.0.8.10 built 15/12/2020 17:10 [Info] Release spec: Release - built by CUBECODERS/buildbot on CCL-DEV [Info] Port usage for PirateCraft (PirateCraft) [Info] Instance is currently running. [Info] LISTENING 8081 TCP (Core.Webserver.Port) [Info] LISTENING 2224 TCP (FileManagerPlugin.SFTP.SFTPPortNumber) [Info] CLOSED 25565 Both (MinecraftModule.Minecraft.PortNumber)

  • checked ufw status Status: active

To Action From -- ------ ---- 443/tcp ALLOW Anywhere # AMP Reverse Proxy 80/tcp ALLOW Anywhere # AMP Reverse Proxy 2223/tcp ALLOW Anywhere # AMP:ADS01:FileManagerPlugin.SFTP.SFTPPortNumber 12820/udp ALLOW Anywhere # AMP:ADS01:ADSModule.Network.MetricsServerPort 22/tcp ALLOW Anywhere 2224/tcp ALLOW Anywhere # AMP:PirateCraft:FileManagerPlugin.SFTP.SFTPPortNumber 25565/tcp ALLOW Anywhere # AMP:PirateCraft:MinecraftModule.Minecraft.PortNumber 25565/udp ALLOW Anywhere # AMP:PirateCraft:MinecraftModule.Minecraft.PortNumber 443/tcp (v6) ALLOW Anywhere (v6) # AMP Reverse Proxy 80/tcp (v6) ALLOW Anywhere (v6) # AMP Reverse Proxy 2223/tcp (v6) ALLOW Anywhere (v6) # AMP:ADS01:FileManagerPlugin.SFTP.SFTPPortNumber 12820/udp (v6) ALLOW Anywhere (v6) # AMP:ADS01:ADSModule.Network.MetricsServerPort 22/tcp (v6) ALLOW Anywhere (v6) 2224/tcp (v6) ALLOW Anywhere (v6) # AMP:PirateCraft:FileManagerPlugin.SFTP.SFTPPortNumber 25565/tcp (v6) ALLOW Anywhere (v6) # AMP:PirateCraft:MinecraftModule.Minecraft.PortNumber 25565/udp (v6) ALLOW Anywhere (v6) # AMP:PirateCraft:MinecraftModule.Minecraft.PortNumber

  • attempted to telnet to local IP on port 25565 to avoid external firewall. The connection was still refused by server.

  • tried changing the port #

  • tried a new instance with a different port

  • The minecraftmodule port always remains closed!

Please let me know what I am missing in order to get this port open and working! - Thanks in Advance

Order By: Standard | Newest | Votes
piratemunky posted this 24 December 2020

Also checked the following:

  • netstat doesn't show the port

Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 0.0.0.0:2223 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:2224 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:8081 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:2225 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:8082 0.0.0.0:* LISTEN tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:6011 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN tcp6 0 0 :::80 :::* LISTEN tcp6 0 0 :::22 :::* LISTEN tcp6 0 0 ::1:6011 :::* LISTEN tcp6 0 0 :::443 :::* LISTEN udp 0 0 127.0.0.53:53 0.0.0.0:* udp 0 0 0.0.0.0:12820 0.0.0.0:*

  • don't see AMP trying to open the port in the logs

cat .ampdata/instances/PirateCraft/AMPLogs/AMPLOG\ 2020-12-24\ 09-22-55.log [09:22:56] [Core Info]            : Running in a Docker environment. [09:22:56] [Core Info]            : OS: Linux / x8664 [09:22:56] [Core Info]            : CPU: Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz (1C/1T) [09:22:56] [Core Info]            : AMP Instance ID: 9798c6df-2a9f-4493-80db-b812c7119a4a [09:22:58] [ModuleLoader Info]    : Loaded MinecraftModule version 1.0.0.3 by CubeCoders Limited [09:22:58] [Core Info]            : Metrics publishing is enabled at udp://localhost:12820. [09:22:58] [ModuleLoader Info]    : Loaded FileManagerPlugin version 1.0.0.0 by CubeCoders Limited [09:22:58] [ModuleLoader Info]    : Loaded EmailSenderPlugin version 1.0.0.0 by CubeCoders Limited [09:22:58] [ModuleLoader Info]    : Loaded WebRequestPlugin version 1.0.0.0 by CubeCoders Limited [09:22:58] [ModuleLoader Info]    : Loaded LocalFileBackupPlugin version 1.0.0.0 by CubeCoders Limited [09:22:58] [ModuleLoader Info]    : Loaded CommonCorePlugin version 1.0.0.0 by CubeCoders Limited [09:22:58] [Core Info]            : Licence Present: AMP Professional Edition (Licenced to Neil Groulx) [09:22:59] [FileManager Notice]   : Using keypair with fingerprint /3KWiNyLoXywctoeOjXIwBu06Kp6jHVQwaO6d0gj0Mw= [09:22:59] [FileManager Info]     : SFTP Server started on 0.0.0.0:2224 [09:22:59] [WebServer Info]       : Websockets are enabled. [09:22:59] [WebServer Info]       : Webserver started on 127.0.0.1:8081 [09:22:59] [Logger Warning]       : RouterTimer@10Hz with 2 jobs started [09:22:59] [Core Info]            : Checking for AMP updates... [09:22:59] [Core Info]            : AMP is up-to-date.

TimeHunter posted this 04 March 2021

Have opened the ports in ubuntu? You can check this by ssh to your ubuntu server or from a terminal in ubuntu using:- sudo ufw status verbose

If the ports aren't in the rules you can add them via:- sudo ufw allow 25565/tcp and sudo ufw allow 25565/udp

Hope this helps.

Maltazar posted this 06 March 2021

I have the same problem with the Latest update

The Minecraft port is never binded as a TCP, only UDP ports are binded.

[amp@GameServer ~]$ netstat -lntu | grep 21025

udp 0 0 0.0.0.0:21025 0.0.0.0:*

My port is 21025

So I think there is a problem here.

Maltazar posted this 06 March 2021

Firewall rules are these.

sudo firewall-cmd --list-all | grep 21025 ports: 8080/tcp 2223/tcp 12820/udp 2224/tcp 25565/tcp 25565/udp 2225/tcp 34197/udp 7777/tcp 2226/tcp 25566/tcp 25566/udp 8081/tcp 8082/tcp 8083/tcp 8084/tcp 2227/tcp 27020/tcp 27020/udp 27015/tcp 27015/udp 27016/tcp 27016/udp 27017/tcp 27017/udp 2228/tcp 21025/tcp 21025/udp

Maltazar posted this 06 March 2021

One more thing, im on CentOS, So i can manage the firewall part myself, but the binding is still not happening.

Close