Hi all — I could really use some help here.
I’m fairly new to AMP/Linux and a bit in over my head, but I’ve tried to dig into this as much as I can before posting.
This Minecraft instance has been running stable for ~1.5 years with no recent changes on my end, and it suddenly stopped starting.
What’s happening
-
Existing instance: Starting → Waiting → Offline
-
No logs generated at all
-
docker ps shows no containers
-
New test instances fail the same way
Environment
-
Debian 12 (Hostinger VPS, Game Panel / AMP)
-
Minecraft Java instance (container-based)
What I’ve verified
-
Docker is installed and running
-
amp user is in docker group
-
/var/run/docker.sock permissions: root:docker, srw-rw----
-
AMP + ampinstmgr are installed and responding
-
Existing instance data is intact:
/home/amp/.ampdata/instances/Minecraft01/Minecraft
-
Main instance is missing InstanceConfig.json
-
Newly created instance is also incomplete (missing expected config) and fails the same way
Why I’m stuck
Since even a brand new instance fails and no containers are ever created, this doesn’t seem like a Minecraft/world issue — it feels like AMP isn’t initializing containers at all.
Important
This instance contains years of data that isn’t fully backed up, so I’m trying to avoid any destructive or rebuild-type steps unless I fully understand them first.
Ask
What would be the safest way to repair this so AMP can create/start containers again without risking the existing instance data?
Happy to provide any additional command output/logs (as text).
Really appreciate any help — thank you in advance.