System Information
| Field | Value |
|---|---|
| Operating System | Linux - Ubuntu 24.04.3 on x86_64 |
| Product | AMP ‘Phobos’ v2.6.3.2 (Mainline) |
| Virtualization | None |
| Application | Application Deployment |
| Module | ADSModule |
| Running in Container | No |
| Current State | Indeterminate |
Problem Description
Issue
I want to provisioning Minecraft instances via the ADSModule API with a custom port (e.g. 25567).
Before the first start, we set all Minecraft configuration nodes (PortNumber, ServerType, EULA, Java 21, etc.), apply the configuration, and call SetInstanceNetworkInfo with the correct port mapping.
However, on the very first startup, the container still binds to 0.0.0.0:25565, even though the configuration clearly shows 25567 before launch.
Subsequent manual restarts after the first failure correctly use the expected port.
Reproduction Steps
- Moving the order of ApplyInstanceConfiguration and SetInstanceNetworkInfo.
- Including/excluding MustStop or ApplicationIP in the payload.
- Using both InstanceId (GUID) and InstanceName (string).
- Verified config file reflects 25567 before start.