{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigfgwiuukrbyohpruzck3p4fsxovwf7aw2igecnqdc2c2tl4ad7ei",
    "uri": "at://did:plc:pgryn3ephfd2xgft23qokfzt/app.bsky.feed.post/3mpgrefcxmnb2"
  },
  "path": "/t/cannot-restart-my-private-space-503-something-went-wrong-when-restarting-this-space/177235#post_2",
  "publishedAt": "2026-06-29T14:52:17.000Z",
  "site": "https://discuss.huggingface.co",
  "tags": [
    "(click for more details)"
  ],
  "textContent": "Hmm… with only a 503 error, it is hard to narrow this down. If you can see a concrete error in the build or container logs, there may be cases where this can be fixed from the user/repo side. But **if no useful logs appear, issues like this often need Hugging Face support to check the Space from their side, e.g. viawebsite@huggingface.co**:\n\n* * *\n\nI would first separate this into two different situations:\n\n  1. **The Space is actually reaching the build/container phase, and the UI logs show a concrete error.**\nIn that case, this may still be fixable from your side: dependency error, missing secret, wrong port, startup timeout, app crash, etc.\n\n  2. **Restart / Factory rebuild fails, but no new Build or Container logs appear at all.**\nIn that case, I would stop treating it as only an application-code problem. It may be stuck before your app code is even reached: Space lifecycle state, scheduling/build dispatch, stale runtime state, or a policy/lock state that only HF staff can inspect.\n\n\n\n\nSince your Space is private, other forum users cannot see the source, app, logs, or settings. So the most useful next step is not more guessing, but checking **what the Space UI shows** and whether the logs actually move.\n\n1. First GUI checks I would do (click for more details) 2. Main split: do the Build or Container logs move? (click for more details) 3. Cases that may still be fixable from your side (click for more details) 4. Cases where editing code may not be enough (click for more details) 5. One branch to check only if the UI explicitly says so: flagged / policy / lock state (click for more details) 6. What I would include if contacting HF support/staff (click for more details) 7. Optional fallback: CLI/API, but I would not make it the first step here (click for more details)\n\nSo my practical suggestion would be:\n\n  1. Use the Space UI first.\n  2. Open **Logs** and check both **Build** and **Container** tabs.\n  3. Note whether either log gets a new timestamp after Restart / Factory rebuild.\n  4. Check Files / `README.md` for SDK/config issues.\n  5. Check Settings and any warning banner.\n  6. If no logs move and both restart actions return 503, collect the Root ID + UTC timestamp + UI state and ask HF support/staff to inspect the Space state from their side.\n\n\n\nThe most important distinction is:\n\n  * **Logs show a concrete error** → likely still worth debugging from the repo/config side.\n  * **No new logs appear at all** → likely not enough evidence for code debugging; HF-side inspection may be needed.\n\n",
  "title": "Cannot restart my private space: \"503. Something went wrong when restarting this Space.\""
}