# Space stuck in ‘Build Queued’
**URL:**
**Author:**  [@keble](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fkeble)%5C
**Post date:** [February 1, 2024, 6:51am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspace-stuck-in-build-queued%2F71431%2F1 "2024-02-01T06:51:05Z")
I have read most threads regarding the same situation “space stucked in build queued.”
Now all my spaces, included any new created spaces, will failed to build. And base on all the previous threads, this is very likely a huggingface issue and require hugging face’ team support.
Can any admin help me to resolve this issue?
-------------------------The ERROR at the build logs-----------------------------------------
→ COPY --link --chown=1000 ./ /home/user/app
DONE 0.0s
→ RUN pip freeze \> /tmp/freeze.txt
DONE 1.0s
→ COPY --from=pipfreeze --link --chown=1000 /tmp/freeze.txt .
DONE 0.0s
→ Pushing image
→ COPY --link --chown=1000 --from=lfs /app /home/user/app
CACHED
→ Restoring cache
→ Pushing image
→ ERROR: failed to push private.docker-builder-registry-s3.internal.huggingface.tech/spaces/65bb3cbe2524c0c9843d12ac:cpu-ff1b92e: failed to copy: operation error S3: GetObject, https response error StatusCode: 404, RequestID: 0SRSN8THY1JDJ13E, HostID: yme3g5zRpSupbkPs9jXoOmb/5GgtJkIEa+UITbIP0vVfpmjJf4IuK7S5JsRYg0424ZjNjpQfC1c=, NoSuchKey:
---
**Author:**  [@Araeynn](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FAraeynn)%5C
**Post date:** [February 1, 2024, 7:05am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspace-stuck-in-build-queued%2F71431%2F2 "2024-02-01T07:05:06Z")
I am having the exact same issue, this is probably because of an internal huggingface update
---
**Author:**  [@keble](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fkeble)%5C
**Post date:** [February 1, 2024, 7:06am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspace-stuck-in-build-queued%2F71431%2F3 "2024-02-01T07:06:35Z")
Are you expecting them to recover after few hours?
---
**Author:**  [@Araeynn](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FAraeynn)%5C
**Post date:** [February 1, 2024, 7:07am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspace-stuck-in-build-queued%2F71431%2F4 "2024-02-01T07:07:59Z")
Probably, as huggingface normally fixes these kind of issues pretty quickly. Might be an issue with AWS though.
---
**Author:**  [@keble](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fkeble)%5C
**Post date:** [February 1, 2024, 7:17am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspace-stuck-in-build-queued%2F71431%2F5 "2024-02-01T07:17:25Z")
> [@keble](#):
>
> Are you expecting them to recover after few hours?
I agree, lets wait
---
**Author:**  [@Araeynn](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FAraeynn)%5C
**Post date:** [February 1, 2024, 8:22am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspace-stuck-in-build-queued%2F71431%2F6 "2024-02-01T08:22:01Z")
The problem is fixed for me, wbu?
---
**Author:**  [@michellehbn](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fmichellehbn)%5C
**Post date:** [February 1, 2024, 9:01am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspace-stuck-in-build-queued%2F71431%2F7 "2024-02-01T09:01:46Z")
Hi @keble @Araeynn, thanks for reporting. We’ve applied a patch and triggering a restart to your Space should do the trick. Let us know though if you continue to see an issue. Thanks again!
---
**Author:**  [@Klein9](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FKlein9)%5C
**Post date:** [July 28, 2024, 2:09pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspace-stuck-in-build-queued%2F71431%2F10 "2024-07-28T14:09:22Z")
Hey, I’m facing the same problem with my spaces. I tried duplicating it, it wroks until I make any edit or restart it.
---
**Author:**  [@hamza09876543](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fhamza09876543)%5C
**Post date:** [August 20, 2024, 10:50am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspace-stuck-in-build-queued%2F71431%2F11 "2024-08-20T10:50:23Z")
hi i am facing the same issue
---
**Author:**  [@cikichen](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fcikichen)%5C
**Post date:** [August 30, 2024, 1:44am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspace-stuck-in-build-queued%2F71431%2F12 "2024-08-30T01:44:21Z")
I’ve been experiencing the same issue for a whole day. Even restarting the space doesn’t help.
---
**Author:**  [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [August 30, 2024, 1:53am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspace-stuck-in-build-queued%2F71431%2F13 "2024-08-30T01:53:06Z")
Try this.
> [@Flowise Space Stuck on Building](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fflowise-space-stuck-on-building%2F103813%2F5)%3A
>
> It was fine until just now, but now I’m probably stuck with the same error. It’s in the build forever. There was no sign of anything, and another private space (also a Zero GPU space) is in the same situation. Restarts and factory rebuilds make no sense. It doesn’t seem to reach the contents of the user’s sources, and it doesn’t seem to make sense to change the sources either. However, the other spaces that are not running builds are all running without any problems. P.S. I had to try to d…
And/or mention or report to victor.
> **[@John6666 on Hugging Face: "@victor
Excuse me.
I would like to report the...](https://huggingface.co/posts/John6666/325819090005748)**
>
> We’re on a journey to advance and democratize artificial intelligence through open source and open science.
---
**Author:**  [@www1q2w3e](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fwww1q2w3e)%5C
**Post date:** [January 26, 2025, 1:49pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspace-stuck-in-build-queued%2F71431%2F14 "2025-01-26T13:49:30Z")
Hi, I meet the same issue now, and I try to restart space but it does not still work : keep building for about 6 hours; Could anyone know how to fix it ?
---
**Author:**  [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [January 26, 2025, 2:02pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspace-stuck-in-build-queued%2F71431%2F15 "2025-01-26T14:02:51Z")
If you get a build error, it’s often because of a mistake on the user’s side, and it can often be resolved by making a few tweaks. However, if it just stops without a build log, it’s probably because HF is stopping the execution for some reason.
For example, if there is a Docker file that contains a library that has been implicitly banned because it has been misused, it will stop. This is particularly common with network-related libraries.
If you have something you got from github, this is probably the case.
Also, if you try to build a Spaces that contains a file larger than 1GB that you were able to upload in the past but can’t upload now, it will also stop. I forget whether a log is output or not. In this case, if you change the specification to place the large file in the model repo and download it when Spaces is started, it will be fine.
---
**Author:**  [@Greums](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FGreums)%5C
**Post date:** [January 27, 2025, 11:58pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspace-stuck-in-build-queued%2F71431%2F16 "2025-01-27T23:58:15Z")
If it stops without a build log, how can we determine the reason for the ban? How can we identify which library is causing the issue?
---
**Author:**  [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [January 28, 2025, 2:45am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspace-stuck-in-build-queued%2F71431%2F17 "2025-01-28T02:45:06Z")
If it is made public, people who misuse it will use the public information, so it is probably not public.
For us, the only way is to eliminate the candidates one by one…
Well, in this case, it is probably caused by one of the network-related libraries, so I think it will be found relatively quickly if it is a build stack due to restrictions.
---
**Author:**  [@Greums](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FGreums)%5C
**Post date:** [February 4, 2025, 5:16am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspace-stuck-in-build-queued%2F71431%2F18 "2025-02-04T05:16:39Z")
I am using the Caddy server. This is probably what is causing the problem in my case.