Ports not openning

Technical Support
1

OS Name/Version: Ubuntu 22.04.5

Product Name/Version: AMP 2.6.1.2 - 20250325.1

Problem Description:

I have been trying to get a Java Minecraft server to run Geyser for cross-platform play. However, I can open the port on the instance through the web GUI, and it claims it’s listening on that port, but when I try to connect, it fails. The odd thing is that when signed into the default user and I run sudo ampinstmgr dumpfirewall it prints out using iptables (output shown below); however, when signed into the AMP user, it shows nothing other than that it is using ufw instead. (not sure if that is intended). I think it’s worth noting that this is running on Oracle Cloud, and the UDP port is added to the security list.

Steps to reproduce:

  • Step 1 Create Java Minecraft instance with Geyser (for UDP 19132 port).
  • Step 2 Add port in the instance settings.
  • Step 3 Try to connect (and fail).

Actions taken to resolve so far:

  1. Tried sudo ampinstmgr dumpfirewall while logged into default user not the AMP user and can’t find the port.
ubuntu@instance-20240822-2310:~$ sudo ampinstmgr dumpfirewall
[Info/1] AMP Instance Manager v2.6.1.2 built 25/03/2025 13:10
[Info/1] Stream: Mainline / Release (aarch64) - built by CUBECODERS/buildbot on                                                                                                          CCL-DEV
[Info/1] Using iptables firewall.
[Info/1] TCP/2223 (AMP:ADS01:FileManagerPlugin.SFTP.SFTPPortNumber)
[Info/1] UDP/12820 (AMP:ADS01:ADSModule.Network.MetricsServerPort)
[Info/1] TCP/8080 (AMP:ADS01:Core.Webserver.Port)
[Info/1] TCP/2228 (AMP:Minecraft01:FileManagerPlugin.SFTP.SFTPPortNumber)
[Info/1] TCP/25569 (AMP:Minecraft01:MinecraftModule.Minecraft.PortNumber)
[Info/1] UDP/25569 (AMP:Minecraft01:MinecraftModule.Minecraft.PortNumber)

It should have [Info/1] UDP/19132 (AMP:Minecraft01:someIdThing)

  1. Searched the forums for a similar situation. This is the closest one: AMP Port not working - #4 by Mike

Any help is appreciated, thanks! <3

2

Try running sudo ampinstmgr updatefirewall (not as the amp user)

1 Like
3

Here’s the result:

ubuntu@instance-20240822-2310:~$ sudo ampinstmgr updatefirewall
[Info/1] AMP Instance Manager v2.6.1.2 built 25/03/2025 13:10
[Info/1] Stream: Mainline / Release (aarch64) - built by CUBECODERS/buildbot on CCL-DEV
[Info/1] Using iptables firewall.
[Info/1] No new firewall rules to add
[Info/1] No existing firewall rules to remove
[Info/1] Firewall is already up-to-date, no changes necessary.
ubuntu@instance-20240822-2310:~$
4

Show your port settings in AMP for that instance?

5

Yeah, and here in lies the problem.

image
image1283×889 120 KB

6

Yeah, there is a major bug atm

7

Good to know, thank you! However, is there any way to open them manually in the meantime?

8

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.