Space stuck on "Starting" forever

Beginners
1

Hi. My Space has been stuck in “Starting” forever and I honestly don’t know what else to do. It just sits there with the blue “Starting” status, hangs for way over 30 minutes, and then eventually dies with an Error. No useful logs, no clear reason, nothing. I’ve pressed Factory reboot so many times I lost count. Tried switching hardware, tried restarting, tried just waiting it out. Same story every time.

I even nuked the whole thing and rebuilt it from scratch in a fresh Space with the same Dockerfile and it still gets stuck in the same endless “Starting” loop. It’s a simple Python bot that runs fine when it actually manages to start, so there’s something going on with the startup process itself.

I just want to understand what’s happening and if there is anything I can do to get it running again. Is this a known issue on the free tier right now? I’ve been fighting this for days and I’m honestly out of ideas. Any help would mean a lot.

2

Could be that there is something like

While true: 
    print("Most likely kills spaces")
3

I’ve pressed Factory reboot so many times I lost count. Tried switching hardware, tried restarting, tried just waiting it out. Same story every time.

So I think it’s either that a new issue has arisen on the HF runtime side, or simply that the Dockerfile wasn’t configured to start up within 30 minutes.

The latter happens quite often, and the most common cause is a port mismatch between the server process and the frontend. (The port the server is listening on and the port the GUI is looking for don’t match, so it never finds it and 30 minutes pass.)

However, without the code or container logs, it’s impossible to perform detailed troubleshooting…

Separately, there are occasional issues where the container logs are always empty. In that case, it’s likely due to a bug on the HF side.