System Information
| Field |
Value |
| Operating System |
Linux - Debian GNU/Linux 13 on x86_64 |
| Product |
AMP ‘Deimos’ v2.7.2.8 (Mainline) |
| Virtualization |
Docker |
| Application |
Astroneer |
| Module |
GenericModule |
| Running in Container |
Yes |
| Current State |
Starting |
Problem Description
Issue
Have an instance with an astroneer server that I haven’t started up in a while.
Tried to start it up today and it won’t start.
I tried updating amp and also all ubuntu packages and restarting my server.
No Matter what I do it just gets stuck saying “Starting Astroneer”, but no matter how long I wait, it never starts.
Reproduction Steps
- Update AMP to 2.7.2.8
- Try to start server
- Astroneer gets stuck just saying “starting astroneer”
Same issue on AMP Release “Proteus” v2.8, built 25/06/2026 23:14. I’ve tried restarting the AMP container, completely removing and reinstalling the Astroneer instance, but the same issue occurs.
After you’re on the latest hotfix, search in the top right of that instance for Remote Admin Password then generate a new one. Restart the instance to see if it is solved
Thanks for the suggestions. I regenerated the Remote Admin password/key and confirmed it was written to the instance configuration, but unfortunately the behavior is unchanged.
Since then I’ve done quite a bit more testing:
-
Fresh AMP 2.8.0 Astroneer instance on Unraid
-
Fresh SteamCMD download each launch (App 728470 validates successfully)
-
Proton GE launches successfully (fsync: up and running)
-
AstroServer-Win64-Shipping.exe starts and remains running under Proton
-
The process loads game assets (verified with lsof)
-
No Astro/Saved/Logs are ever created
-
The server never opens any UDP sockets or binds its configured ports
-
AMP never progresses past Starting
As a comparison, I also have the ghcr.io/ich777/steamcmd:astroneer container running on the same Unraid host. It uses the same Steam app (728470), starts correctly, creates logs, binds UDP 8777, and clients can connect successfully.
That seems to narrow it down to either the way the current AMP Astroneer module launches the server, or an interaction between the current dedicated server build and AMP’s Proton launch method.
The executable stays alive for minutes rather than crashing immediately, but it never reaches the point where it creates logs or initializes networking.
Is there any way to enable more verbose logging for the Astroneer module, or is there anything else you’d like me to collect to help narrow this down?