OS Name/Version: Ubuntu 24.04
Product Name/Version: AMP Instance Manager v2.6.2.6 built 04/08/2025 23:40
Problem Description:
I updated the AMP Panel using the panel “Update” button, and now the panel will not appear any more. I was accessing the AMP Panel via localhost:8080, but now I get a “This site can’t be reached” error.
Steps to reproduce:
- Fully functional panel and two instances of Minecraft running for 4+ months
- Update the master panel via the “update” (or “upgrade”..?) button
- Nothing is accessible any more
Actions taken to resolve so far:
- Restarted the host machine with
sudo reboot - Followed instructions at: How to update AMP to the latest version
Update 1
AMP doesn’t seem to think that there are any instances, despite there by three: the host, and the two Minecraft instances. Here is what I have tried so far:
sudo su -l amp
cd ~/.ampdata/instances
ls -la
Shows the following:
drwxrwxr-x 5 amp amp 4096 Apr 18 13:33 .
drwxrwxr-x 4 amp amp 4096 Aug 30 16:28 ..
drwx------ 6 amp amp 4096 Aug 30 17:46 ADS01
drwx------ 9 amp amp 4096 Aug 30 17:46 ElderlightGrove01
drwx------ 9 amp amp 4096 Aug 30 16:28 ElderlightGroveCreative01
Then
ampinstmgr --ShowInstancesTable
Produces
[Info/1] AMP Instance Manager v2.6.2.6 built 04/08/2025 23:40
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
No instances to show.
Why is the ampinstmgr not recognising these instances after the update?
Update 2
I have resolved my issue.
It appears that the ~/.ampdata/instances.json file was deleted by the update process. When I ran: ls -la ~/.ampdata/ it only showed the following files:
drwxrwxr-x 5 amp amp 4096 Apr 18 13:33 instances
-rw-rw-r-- 1 amp amp 4107 Apr 15 17:25 instances.json-20250415.bak
-rw-rw-r-- 1 amp amp 6510 Apr 18 13:34 instances.json-20250418.bak
-rw-rw-r-- 1 amp amp 6748 Apr 28 16:22 instances.json-20250428.bak
-rw-r--r-- 1 amp amp 6749 Jul 8 09:24 instances.json-20250708.bak
-rw-r--r-- 1 amp amp 6749 Aug 30 19:16 instances.json-20250830.bak
drwxrwxr-x 3 amp amp 4096 Apr 15 13:12 Versions
I took a wild guess that the .bak files were all just backups, and I needed an actual instances.json file, so I created one by duplicating instances.json-20250830.bak and renaming it instances.json.
Then I ran ampinstmgr --StartInstance ADS01 and it started just fine. Previously, running that command (without the instances.json file) produced the error [Error/1] No such instance matching name: 'ADS01'.
Everything seems fine now!
Lloyd