{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiciumhoxbih5a64pwwcizlqjaaxvckk5nk6gxesvw3n46n3xd6cyi",
    "uri": "at://did:plc:pgryn3ephfd2xgft23qokfzt/app.bsky.feed.post/3mh6kg6y7kqk2"
  },
  "path": "/t/space-stuck-on-starting-badge-despite-app-running-fine-on-port-7860/174315#post_1",
  "publishedAt": "2026-03-16T12:30:22.000Z",
  "site": "https://discuss.huggingface.co",
  "textContent": "Space stuck on “Starting” badge despite app running fine on port 7860\n\nMy 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.\n\nConfig:\n\n  * `sdk: docker`\n\n  * `app_port: 7860`\n\n  * App binds to `0.0.0.0:7860`\n\n  * `demo.launch(server_name=\"0.0.0.0\", server_port=7860)`\n\n\n\n\nThe 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.\n\nIs there a way to force the runtime SHA to update, or reset the health check?\n\nSpace: `juakazike/gender-sensitization-engine`",
  "title": "Space stuck on \"Starting\" badge despite app running fine on port 7860"
}