Server IP binding not updating

OS Name/Version: Ubuntu 24.04.1 LTS

Product Name/Version: AMP 2.6.06

Problem Description:
Instances using any available IP despite setting the Server IP Address binding NIC under Configuration > Minecraft > Network.

Goal here is to use a different NIC on two instances in order to use the same port for both since they have different IP addresses. (Both NICs are recognized in the web portal)

Steps to reproduce:

  • Create a new Minecraft Instance
  • Go to Configuration > Minecraft > Network and change the Server IP Address to a NIC with an assigned IP address
  • Return to the Instances screen. IP address still shows as 0.0.0.0:25565

Actions taken to resolve so far:
Restarted the instance, amp, and the host.
Tried changing IP using

ampinstmgr --RebindInstace [Instance Name] [IP Address] [Port]

A bit at a loss here. The second NIC is recognized by AMP, so I figured that by configuring t he instance to use a different IP address would allow me to use the default port for each instance and then create an A record w/ a new subdomain but unless I’m able to change the IP of the instance I cannot do this.

Instances are set to run in docker and host-mode networking are enabled.

Output from CLI:

ampinstmgr --RebindInstance Minecraft02 192.168.1.202 8081
[Info/1] AMP Instance Manager v2.6.0.6 built 20/11/2024 20:58
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[Info/1] Reconfiguring instance Minecraft02…
[Info/1] Stopping instance Minecraft02…
Error response from daemon: cannot kill container: AMP_Minecraft02: Cannot kill container
65c6506883774a23543af428c74635c376608c9fb0a2b2b94749df8b04f05bda: unknown
error after kill: runc did not terminate successfully: exit status 1: unable to signal init:
permission denied
: unknown
[Info/1] Instance Minecraft02 failed to stop.
[Info/10] 11f6a3fca34a51772c31496dab9b627fc54e4dfd85e7a19e57030dc23d9075e8
[Info/6] Done. Use --ShowInstancesList to see your changes.

That’s all just a visual delay, when you change the binding in the instance’s settings, it’s changed.
However, AMP just doesn’t support using the same port on multiple IPs, it’s a known limitation of the networking system. (you can use SRV DNS records to get around adding the port to the end)