# Signed up for pro - pro tokens not working

**URL:** </static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsigned-up-for-pro-pro-tokens-not-working%2F141679%3E%5C
**Category:** Site Feedback\
**Created:** [February 18, 2025, 9:22pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsigned-up-for-pro-pro-tokens-not-working%2F141679 "2025-02-18T21:22:25Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![modeLIMINAL](https://avatars.discourse-cdn.com/v4/letter/m/67e7ee/32.png) [@modeLIMINAL](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FmodeLIMINAL)%5C
**Post date:** [February 18, 2025, 9:22pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsigned-up-for-pro-pro-tokens-not-working%2F141679%2F1 "2025-02-18T21:22:25Z")

</div>

Maybe I’m mistaken in understanding your pro account, but after paying for the membership, I still get hit with the same notifications that I’m on a free account when inferencing in spaces. I still seem to have the 5 minute limitation. What gives?

-Z

---

<div class="post-metadata">

**Author:** ![meganariley](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/meganariley/32/56966_2.png) [@meganariley](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fmeganariley)%5C
**Post date:** [February 19, 2025, 1:59am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsigned-up-for-pro-pro-tokens-not-working%2F141679%2F2 "2025-02-19T01:59:07Z")

</div>

Hi @modeLIMINAL As a PRO user you have the option to duplicate the Space into your own account/namespace. To start to see your PRO GPU limits applied, we recommend:

- Making sure you have the latest version of Gradio in the README.md file
- Add your HF\_TOKEN as a secret in your Spaces settings. The token can be created in your user settings. Once it’s been added, you should start to see the usage increase for ZeroGPU here: [Hugging Face – The AI community building the future.](https://huggingface.co/settings/billing).

If you’re still running into issues, can you please link the Space? We can investigate.

---

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [February 19, 2025, 5:01am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsigned-up-for-pro-pro-tokens-not-working%2F141679%2F3 "2025-02-19T05:01:16Z")

</div>

If we’re talking about Zero GPU space, this bug may be having an effect. Updating Gradio in Spaces to the latest version will definitely fix the problem, but even if you don’t do that, I think the HF side is improving things a little.

> **[@sebblers on Hugging Face: "Subscribed to pro a month ago because I wanted to...](https://huggingface.co/posts/sebblers/435374151447195)**
>
> We’re on a journey to advance and democratize artificial intelligence through open source and open science.

---

<div class="post-metadata">

**Author:** ![modeLIMINAL](https://avatars.discourse-cdn.com/v4/letter/m/67e7ee/32.png) [@modeLIMINAL](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FmodeLIMINAL)%5C
**Post date:** [February 19, 2025, 7:08pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsigned-up-for-pro-pro-tokens-not-working%2F141679%2F4 "2025-02-19T19:08:34Z")

</div>

This is happening on every single space. Spaces thinks I do not have a paid pro account. Today, I tried duplicating a space to see if that might resolve the issue and it did not. The space I tried specifically was [chheplo/DeepSeek-R1-Distill-Llama-8B](https://huggingface.co/spaces/chheplo/DeepSeek-R1-Distill-Llama-8B). I also created a new token with what I would assume to be plenty of access to my account and added that as a secret as you suggest but that also did not appear to change anything.

---

<div class="post-metadata">

**Author:** ![modeLIMINAL](https://avatars.discourse-cdn.com/v4/letter/m/67e7ee/32.png) [@modeLIMINAL](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FmodeLIMINAL)%5C
**Post date:** [February 19, 2025, 7:10pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsigned-up-for-pro-pro-tokens-not-working%2F141679%2F5 "2025-02-19T19:10:21Z")

</div>

This seems to be the exact same issue I am experiencing. Can you elaborate on updating Gradio in this situation? Are you meaning specifically within the app requirements or is there something globally on my profile you are referring to?

---

<div class="post-metadata">

**Author:** ![meganariley](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/meganariley/32/56966_2.png) [@meganariley](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fmeganariley)%5C
**Post date:** [February 19, 2025, 7:12pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsigned-up-for-pro-pro-tokens-not-working%2F141679%2F6 "2025-02-19T19:12:18Z")

</div>

Hi @modeLIMINAL Make sure you add your hf\_token as a secret, not a variable. Please also update the version of Gradio for your duplicated Space - you can do that in the README.md file of your Space. Head to your Files \> README.md and click ‘Upgrade’ and commit the changes.

Please let me know if you still run into issues after updating both.

---

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [February 19, 2025, 9:44pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsigned-up-for-pro-pro-tokens-not-working%2F141679%2F7 "2025-02-19T21:44:59Z")

</div>

megan is right. If you get an error when upgrading Gradio, please contact us by email or on the forum. Sometimes the syntax changes when the version is upgraded, which can cause errors.😅
