# Pro Account – ZeroGPU Not Working Despite Subscription

**URL:** <https://discuss.huggingface.co/t/pro-account-zerogpu-not-working-despite-subscription/168446>\
**Category:** Beginners\
**Created:** [September 15, 2025, 1:40pm UTC](https://discuss.huggingface.co/t/pro-account-zerogpu-not-working-despite-subscription/168446 "2025-09-15T13:40:15Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![blublu18](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/blublu18/32/53527_2.png) [@blublu18](https://discuss.huggingface.co/u/blublu18)\
**Post date:** [September 15, 2025, 1:40pm UTC](https://discuss.huggingface.co/t/pro-account-zerogpu-not-working-despite-subscription/168446/1 "2025-09-15T13:40:15Z")

</div>

Hi,

I subscribed to Hugging Face Pro specifically to use ZeroGPU with IDM-VTON in my own Space, but I have not been able to use it at all.

Every attempt gives this error:

“Unlogged user is running out of daily ZeroGPU quotas. Signup for free on [huggingface.co/login](http://huggingface.co/login) to get more ZeroGPU quota now.”

This happens even though:

```
•	My Space shows Running on Zero

•	I still have unused ZeroGPU quota (e.g., 4.1 / 25 minutes used)

•	I am logged in with a Pro account

```

What I already tried:

```
•	Clearing cookies/cache

•	Allowing third-party cookies

•	Restarting / duplicating the Space

•	Switching visibility (Private/Public)

•	Logging out/in and testing in Incognito

```

Nothing works. I’ve also emailed billing to request a refund since the service is unusable, but I’d like to confirm if this is a known bug with ZeroGPU not recognizing Pro users.

Thanks.

---

<div class="post-metadata">

**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:** [September 15, 2025, 10:03pm UTC](https://discuss.huggingface.co/t/pro-account-zerogpu-not-working-despite-subscription/168446/2 "2025-09-15T22:03:30Z")

</div>

> IDM-VTON

This must be the cause.  
There [was a bug in an older version of the Hugging Face library (prior to Gradio 5.12.0), and its effects are still being felt today](https://discuss.huggingface.co/t/virtual-try-on-doesnt-appear-to-work/151913).

---

<div class="post-metadata">

**Author:** ![sebblers](https://avatars.discourse-cdn.com/v4/letter/s/c5a1d2/32.png) [@sebblers](https://discuss.huggingface.co/u/sebblers)\
**Post date:** [September 22, 2025, 4:03pm UTC](https://discuss.huggingface.co/t/pro-account-zerogpu-not-working-despite-subscription/168446/3 "2025-09-22T16:03:18Z")

</div>

I’ve had the same issue for more than 6 months, I just gave up because I can’t use any spaces at all

---

<div class="post-metadata">

**Author:** ![sebblers](https://avatars.discourse-cdn.com/v4/letter/s/c5a1d2/32.png) [@sebblers](https://discuss.huggingface.co/u/sebblers)\
**Post date:** [September 22, 2025, 4:10pm UTC](https://discuss.huggingface.co/t/pro-account-zerogpu-not-working-despite-subscription/168446/4 "2025-09-22T16:10:40Z")

</div>

Duplicating spaces has never ever worked for me, always getting build errors. I wish this website had a subscription system that actually worked and gave you what you paid for. Me and many others have paid multiple times for ZeroGPU yet not been able to use what we paid for. I hate that this is the only website that people posts cool demo spaces to beacause you can never use them even if you pay

---

<div class="post-metadata">

**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:** [September 22, 2025, 9:45pm UTC](https://discuss.huggingface.co/t/pro-account-zerogpu-not-working-despite-subscription/168446/5 "2025-09-22T21:45:26Z")

</div>

Hmm… The cause may sometimes be a specification change by Hugging Face, but more often it occurs because the contents of the “latest version” of libraries specified in `requirements.txt` change over time. Anyone can modify `requirements.txt` in duplicated space, but it requires knowledge or searching…

A feature like “duplicate the space while fixing the library versions to those from the last successful startup” would help a bit… But structurally, this might be difficult.

Well, if it’s a simple error in Zero GPU Spaces, I can probably suggest a fix if you ask me…

User-to-user mutual aid is good, but for paid services, it would be even better if HF had a dedicated support channel.

Edit:  
For the `IDM_VTON` space, [since large files are included in the repository, this scenario might also apply](https://discuss.huggingface.co/t/build-error-error-while-cloning-repository/146725). Essentially, splitting Spaces into Spaces and Models will resolve the issue. However, it requires a few lines of coding.

In any case, the root cause, broadly speaking, is that “the environment has changed since the space was first launched normally, causing behavior change of the code” If adapting code to the current environment manually will make it work. There are few exceptions, but they are rare.

---

<div class="post-metadata">

**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:** [September 23, 2025, 12:33am UTC](https://discuss.huggingface.co/t/pro-account-zerogpu-not-working-despite-subscription/168446/6 "2025-09-23T00:33:25Z")

</div>

I created [an `IDM_VTON` space compatible with Gradio 5](https://huggingface.co/spaces/John6666/IDM-VTON-GRADIO5). Duplicating it into the Zero GPU space should make it work. (There seems to be [a slight bug in the behavior of the `ImageEditor` with example in Gradio 5](https://github.com/gradio-app/gradio/issues/11366)…)
