Space stuck on "Starting" badge despite app running fine on port 7860

Spaces
1

Space stuck on “Starting” badge despite app running fine on port 7860

My Docker SDK Space (juakazike/gender-sensitization-engine) has been stuck on “Starting” for several hours. The app is actually running — GET / returns HTTP 200, the Gradio UI loads, and the API responds correctly. But the badge never flips to “Running” and the Space page shows a loading screen to users instead of the app.

Config:

  • sdk: docker

  • app_port: 7860

  • App binds to 0.0.0.0:7860

  • demo.launch(server_name="0.0.0.0", server_port=7860)

The runtime API consistently returns sha: b0d17d5 (an old commit) even though the space SHA is 8a03ae4. Looks like the health check never registers the new container as healthy so HF keeps showing the stale state.

Is there a way to force the runtime SHA to update, or reset the health check?

Space: juakazike/gender-sensitization-engine

3 Likes
All my Spaces stuck in Building with empty logs
Space stuck in broken runtime-control state: build succeeds, but Factory reboot returns 503 and restart API fails
2

Same issue here. It affects all my spaces, maybe good to know in my scenario:

  • all spaces are connected to an organisation

  • all spaces are set to ‘private’

  • nothing changed to my spaces since before the weekend, but after idle time during the weekend none of them are able to boot since today.

1 Like
3

All my spaces are coming back online now while I didn’t change anything in the meantime. Guess it was just a platform issue somewhere

1 Like