System Information
| Field | Value |
|---|---|
| Operating System | Linux - Debian GNU/Linux 12 on x86_64 |
| Product | AMP ‘Deimos’ v2.7.2.2 (Mainline) |
| Virtualization | QEMU_KVM |
| Application | Application Deployment |
| Module | ADSModule |
| Running in Container | No |
| Current State | Indeterminate |
Problem Description
Issue
After updating AMP, my Minecraft instance “Shader01” no longer starts correctly.
The server now shuts down unexpectedly and scheduled restart tasks and weekly backups no longer work.
The deployment log reports Docker container conflicts, including that the container “AMP_Shader01” already exists. AMP also reports “Connection refused” errors when trying to communicate with the instance and repeatedly shows WebSocket errors.
Another instance (Kingdingaling01) also reports similar connection errors, which suggests that the issue is related to the AMP deployment system or Docker rather than a specific Minecraft server.
The AMP update also does not complete successfully and remains available after the update attempt.
Could you please investigate the AMP deployment system, Docker containers, and repair the installation while preserving all existing Minecraft worlds and server data?
Reproduction Steps
- Updated AMP to the latest available version.
- Restarted the Minecraft instance Shader01.
- The instance fails to start and AMP reports Docker and connection errors.
- Scheduled backups and restart tasks also stopped working.
Existing Minecraft servers continue to run normally. However, any newly created instance cannot be configured or started because it requires AMP version 2.8. Since the AMP update never completes successfully, new instances are effectively unusable.
This appears to be an issue with the AMP/ADS installation rather than with a specific Minecraft instance, because existing servers work while all newly created instances depend on the incomplete AMP update.
I have verified that the CubeCoders AMPTemplates repository is accessible from my local computer. The issue therefore appears to be on the server side. AMP never completes the template synchronization and remains stuck on “Updating remote sources” and “Fetching latest configurations…”. As a result, AMP cannot update to version 2.8 and newly created instances cannot be used.