# I'm new here. I created a space, but it just stays on "Building." Even new spaces aren't loading **URL:** \ **Category:** Beginners\ **Created:** [February 27, 2026, 6:26pm UTC](https://discuss.huggingface.co/t/im-new-here-i-created-a-space-but-it-just-stays-on-building-even-new-spaces-arent-loading/173864 "2026-02-27T18:26:15Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![ADEasy](https://avatars.discourse-cdn.com/v4/letter/a/d9b06d/32.png) [@ADEasy](https://discuss.huggingface.co/u/ADEasy)\ **Post date:** [February 27, 2026, 6:26pm UTC](https://discuss.huggingface.co/t/im-new-here-i-created-a-space-but-it-just-stays-on-building-even-new-spaces-arent-loading/173864/1 "2026-02-27T18:26:15Z")
I’m new here. I created a space, but it just stays on “Building.” Even new spaces aren’t loading. ---
**Author:** ![Pantsoffski](https://avatars.discourse-cdn.com/v4/letter/p/6f9a4e/32.png) [@Pantsoffski](https://discuss.huggingface.co/u/Pantsoffski)\ **Post date:** [February 27, 2026, 6:48pm UTC](https://discuss.huggingface.co/t/im-new-here-i-created-a-space-but-it-just-stays-on-building-even-new-spaces-arent-loading/173864/2 "2026-02-27T18:48:27Z")
Same here… ---
**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](https://discuss.huggingface.co/u/John6666)\ **Post date:** [February 27, 2026, 10:59pm UTC](https://discuss.huggingface.co/t/im-new-here-i-created-a-space-but-it-just-stays-on-building-even-new-spaces-arent-loading/173864/3 "2026-02-27T22:59:54Z")
Multiple causes are possible, and other factors may also be involved, so without build logs, nothing can be determined: * * * ## What “Building” means on Spaces On Hugging Face, **“Building” is a coarse status** that can cover multiple backend phases: 1. **Build** : install dependencies / build an image 2. **Registry** (mostly Docker): push/pull the image 3. **Scheduling** : allocate hardware and start the container 4. **Health check** : your app must start and **bind to the expected port** ; if it never becomes “healthy,” it may look like it’s still building or it fails after a while ([Hugging Face Forums](https://discuss.huggingface.co/t/launch-timed-out-space-was-not-healthy-after-30-min-space-keeps-on-building/63685 "Launch timed out, space was not healthy after 30 min ...")) So the key is to **classify which phase you’re stuck in** , using logs. * * * ## 5-minute triage playbook ### 0) Confirm it’s not a platform-wide problem (30 seconds) - Check Hugging Face status: **Spaces** and **Spaces Proxy** should be “Operational.” ([Hugging Peace Status](https://status.huggingface.co/ "Hugging Face status")) If there’s an incident, _many_ users see “Building” loops at the same time and your code changes won’t help. * * * ### 1) Reproduce with a “known-good” minimal Space (2 minutes) Create a minimal hello-world Space (e.g., a tiny Gradio demo or template). If **a blank/minimal Space also gets stuck** , your issue is likely **not your repo** but **infra/queue/account-side** (scheduler backlog, proxy, stuck builder). This exact inference is repeatedly used in recent forum triage guidance. ([Hugging Face Forums](https://discuss.huggingface.co/t/my-space-has-been-stuck-in-the-building-state-for-over-an-hour/173473 "My Space has been stuck in the building state for over an ...")) * * * ### 2) Use logs to classify the failure (most important) Open the Space → **Logs** and check **both** : - **Build logs** (dependency install/build steps) - **Container/Runtime logs** (your app starting/crashing) This is the standard first step recommended by HF docs and common support replies. ([Hugging Face Forums](https://discuss.huggingface.co/t/having-error-in-restarting-space/173572 "Having error in restarting space - Beginners")) * * * ## Interpret the result (decision tree) ### A) **Logs are empty / don’t load / show nothing happening** This usually points to **infra/queue/scheduler issues** rather than your code. Similar reports describe “empty logs” during infra problems and recommend retrying later or escalating. ([Hugging Face Forums](https://discuss.huggingface.co/t/empty-log-and-not-building-space/42273 "Empty log and not building space")) **What to do** 1. Space Settings → **Restart** 2. Make a **no-op commit** (edit README) to force a new build 3. Space Settings → **Factory reboot** 4. If minimal new Spaces also have empty logs, escalate (see “What to report” below). ([Hugging Face Forums](https://discuss.huggingface.co/t/my-space-has-been-stuck-in-the-building-state-for-over-an-hour/173473 "My Space has been stuck in the building state for over an ...")) * * * ### B) Build says **“Build Queued”** or runtime shows **“Scheduling failure: not enough hardware capacity / Unable to schedule”** That’s a **capacity/scheduler** bottleneck (common at peak times or for certain hardware). ([Hugging Face Forums](https://discuss.huggingface.co/t/space-is-building-permanently/99740 "Space is Building... permanently")) **What to do** - Retry later (queue clears), or switch to a different hardware tier if possible. - Duplicating/recreating sometimes lands you on a different worker (works as a workaround in several “permanently building” reports). ([Hugging Face Forums](https://discuss.huggingface.co/t/space-is-permanently-building/140495 "Space is permanently "Building"")) * * * ### C) Build fails with registry errors like **`spaces-registry… 401 Unauthorized`** This is typically **HF registry/infra/auth** , not your app code, and is tracked in issues and forum posts. ([GitHub](https://github.com/huggingface/datasets/issues/7530 "How to solve "Spaces stuck in Building" problems #7530")) **What to do** - Retry later; if persistent, report it with logs (see below) and reference that it’s a registry auth failure. * * * ### D) After ~30 minutes you get: **“Launch timed out, space was not healthy after 30 min”** This means the container started, but **HF never saw a healthy web service** (usually wrong **host/port** , app stuck during startup, or server never comes up). HF staff explicitly describe the expectation: your service must bind to the exposed port within the health timeout. ([Hugging Face Forums](https://discuss.huggingface.co/t/launch-timed-out-space-was-not-healthy-after-30-min-space-keeps-on-building/63685 "Launch timed out, space was not healthy after 30 min ...")) **Common fixes** - **Bind to `0.0.0.0`** , not `127.0.0.1` (especially for Flask/FastAPI/custom servers). Forum replies repeatedly show this as the fix. ([Hugging Face Forums](https://discuss.huggingface.co/t/launch-timed-out-space-was-not-healthy-after-30-min/30176 "Launch timed out, space was not healthy after 30 min")) - **Port mismatch** : - App doing heavy work at startup (large downloads/installs) → move to build step / cache, or slim startup. * * * ### E) Build succeeds, but container logs show crashes (imports, missing env vars, etc.) Then it’s your app/runtime configuration. Common culprits: - Missing **Secrets/Variables** - Wrong README YAML (`sdk`, `app_file`, etc.)—the YAML reference is the canonical source. ([Hugging Face](https://huggingface.co/docs/hub/en/spaces-config-reference "Spaces Configuration Reference")) - OS packages: use `packages.txt` for apt dependencies (Gradio/Streamlit SDKs) and `requirements.txt` for Python deps. ([Hugging Face Forums](https://discuss.huggingface.co/t/how-to-apt-install-in-spaces-build/31988 "How to apt install in spaces build")) * * * ## “Even new Spaces aren’t loading” — what that usually implies If **a fresh hello-world Space** also stays on “Building,” the most likely buckets are: - **Platform-side** (Spaces/Spaces Proxy/infra backlog) ([Hugging Peace Status](https://status.huggingface.co/ "Hugging Face status")) - **Account-wide scheduling/build issues** (queue or stuck builder) ([Hugging Face Forums](https://discuss.huggingface.co/t/my-space-has-been-stuck-in-the-building-state-for-over-an-hour/173473 "My Space has been stuck in the building state for over an ...")) In that situation, don’t spend time rewriting your app: focus on **logs + minimal reproduction + reporting**. * * * ## What to collect before posting for help (or contacting support) Include: - Space URL(s) - Whether a **minimal blank Space** reproduces - **Build log tail** + **first runtime error** from container logs - Timestamp and (if you see it) any backend trace identifier (some restart errors show a request/trace ID that staff can use). ([Hugging Face Forums](https://discuss.huggingface.co/t/restart-error-503-factory-reset-no-rebuild-same-with-other-space/173779 "Restart error 503. Factory reset. No rebuild. Same with ..."))