Connectivity Problem with Minecraft - certain ports not exported and recognised

Technical Support
,
1

System Information

Field Value
Operating System Linux - Debian GNU/Linux 11 on x86_64
Product AMP ‘Decadeus’ v2.4.5.0 (Mainline)
Virtualization QEMU_KVM
Application Minecraft
Module MinecraftModule
Running in Container No
Current State Ready

Problem Description

Issue

$ sudo -u amp ampinstmgr ports
[Info] AMP Instance Manager v2.4.5 built 19/06/2023 22:49
[Info] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
Please enter value for Instance Name
>[x]

[Info] Port usage for [x] ([x])
[Info] Instance is currently running.
[Info] LISTENING        8082    TCP     (Core.Webserver.Port)
[Info] LISTENING        19132   UDP     (CustomPort.a7e7fc35-2535-479b-8cde-f106f14a40b5)
[Info] LISTENING        8066    TCP     (CustomPort.0a032b74-ff12-48f8-9715-c4ff9d5a8584)
[Info] LISTENING        1025    Both    (CustomPort.070e96b9-c0de-4da4-baa2-0fd002a12a3b)

not present in ufw, so manually needed to create applicable firewall rule for external access (but is listening and does work)

Reproduction Steps

  • checked application running
  • FileManagerPlugin.SFTP.SFTPPortNumber, MinecraftModule.Minecraft.PortNumber in web ui, but not ampinstmgr ports
  • fixed connectivity issue by manually adding firewall rule, but the ports still not shown in ampinstmgr
2

There’s a bug in the current version that prevents it from syncing the firewall. Fix due in the next update.

3

This has been fixed, updating AMP will resolve this :slight_smile:

4

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