Server is always stuck on "Starting", it works but never changes to "Started" and then gets killed by wings eventually

[dougmaitelli]

Current Behavior

So, I tried to setup this yesterday and initially my problem was that the setup installation prompts would show in the web terminal without allowing me to type anything.
Eventually I used the host terminal to attach a shell to the container and inputting the configuration there manually, which worked and made installation succeed.
Since then my bot is working perfectly fine, but the status on the panel is always shown as Starting and after a few hours the process just dies, I assume because the panel times out waiting for the status to change to Started.

Expected Behavior

Status should change to Started

Steps to Reproduce

N/A

Bot Version

4.1.0

Installation Method

Egg

Error Logs

No response

Is there an existing issue for this?

• I have searched the existing issues before opening this issue.
• I have checked in the Discord server and believe this is a bug with the bot, and not a configuration issue with my specific system.

[GamingBaeren]

Easy solution on your side
Change in the egg the startup Configuration to
{ "done": [ "PteroStats installed.", "Configuration loaded" ] }

[dougmaitelli]

Hey, yeah, I ended up doing that actually. When I created this issue I was not aware on how the host identified the service was "ready" so I inspected the code and found out about this setting.
It did work, but for some reason after some time running the container for pterostats just stops running still