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 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.
1 Like
I’ve had the same issue for more than 6 months, I just gave up because I can’t use any spaces at all
1 Like
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
1 Like
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. 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.