Python server stuck at Starting, then Offline — FREE-EU-RO-40

Hello Wispbyte team, My free Python 3.11 app server (support tag 3f17c5a6, node FREE EU RO 40) stopped starting after a restart today, 13 October. The panel changes to Starting for several minutes, then Offline. CPU and RAM remain at 0, and the public site shows “Web server offline.” The console only shows the Wispbyte startup banner and “Server marked as offline”; there is no pip or Python output. Activity Logs say “Server started successfully” for the power on requests, but the container never becomes Online. The startup command points to /home/container/app.py; the file exists. This server ran successfully earlier today with the same Python image and command. I tried Stop/Start and one forced Kill followed by Start, without improvement. The public node status page lists EU40 RO as Online. Could you check why this specific container does not reach its startup command, and unstick it? Please preserve the server files and data; do not reinstall or wipe it. Thank you.