OS Name/Version: Ubuntu 24.04.2 (Server)
Product Name/Version: 2.6.1.6
Problem Description: All pre-existing (prior to the host reboot/move) game instances will not progress past “Application Waiting”, however, new game instances do work.
Steps to reproduce:
- Shutdown all server instances.
- Reboot the host (for OS Update), then host shutdown.
- Physically moved the host machine (causing DHCP local IP change)
- Booted the host, ensured datastores mounted properly and permissions intact.
- Accessed AMP panel at new local IP.
- Set “Default AMP IP Binding” and “Default App IP Binding” to new local IP.
- Confirmed AMP permissions to instance directories via AMP File Manager.
Actions taken to resolve so far:
Attempting to start an existing instance results in “Application Waiting” for several seconds, then reverts to “instance not running”.
Attempting to “manage instance” while in “application waiting” status (cube icon) results in no response and no error.
Attempting “Manage in new tab” results in a new tab with error message “AMP was unable to reach its backend at http://192.168.1.XXX:XXXX/remote/9bad854f” that refreshes every five seconds. (Note: The actual IP in the error message is correct)
Updating & Restarting AMP panel did not resolve the issue.
Restarting AMP panel did not resolve the issue.
[Minecraft] Manually editing the “server.properties” file to reflect the new IP had no effect; Additionally (not sure if important), the manual edit was not overwritten by AMP (as normally happens when the properties file does not match the information entered via the web panel),
By default the Default Application Binding is set to 0.0.0.0 (all network interfaces) to avoid issues if/when the IP changes.
You’ll want to press the folder icon on the instance, then read it’s AMP_Logs to see why the instance won’t start. Might be as simple as reactivating it with your licence.
Also note, private IPs are not sensitive info.
Manual edits to the server.properties file weren’t being reverted by AMP because the server wasn’t starting at all.
Thank you for your reply and informing me about the AMP Log folder.
I followed your recommendation to return the Application Binding back to 0.0.0.0 - it did not resolve the issue or change any of the behavior.
I also followed your recommendation to check the AMP Logs, which indicated the IP issue remains and, in part, provided the same advice you did:
[Error] --- End Exception Data ---
[04:18:47] [ErrorReporter Info/1] : ####################################
[04:18:47] [ErrorReporter Info/1] : # Self Diagnostics #
[04:18:47] [ErrorReporter Info/1] : ####################################
[04:18:47] [ErrorReporter Info/1] : AMP tried to listen on an IP address that is does not exist on this system. This may be caused by having AMP or an application bound to a specific IP while using dynamic IPs or DHCP. Try binding to 0.0.0.0, or turning on 'StoreIPAddressesAsMACAddresses' in AMPConfig.conf and re-configuring any network settings for this instance if you're using dynamic IPs or containers.
Regarding the advice provided in the AMP Log, I examined the AMPConfig.conf; all IP-related records were either 0.0.0.0 or localhost.
I did not activate StoreIPAddressesAsMACAddresses because I don’t know how to shut down the AMP instance safely and my search for that answer has not produced straight forward results.
As the Application Binding setting says, it only applies to new instances, anything else must be reconfigured by hand while an instance is stopped.
To stop an instance, press the stop button in the panel, then use the file browser on the left to access it’s .kvp and .conf files.