# Free Plan - NextJS SDK - No Key Found error

**URL:** <https://community.auth0.com/t/free-plan-nextjs-sdk-no-key-found-error/189696>\
**Category:** Get Help\
**Tags:** free-trial, login-experience\
**Created:** [July 25, 2025, 8:22pm UTC](https://community.auth0.com/t/free-plan-nextjs-sdk-no-key-found-error/189696 "2025-07-25T20:22:19Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mohammad2](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/mohammad2/32/72934_2.png) [@mohammad2](https://community.auth0.com/u/mohammad2)\
**Post date:** [July 25, 2025, 8:22pm UTC](https://community.auth0.com/t/free-plan-nextjs-sdk-no-key-found-error/189696/1 "2025-07-25T20:22:19Z")

</div>

Using Free Plan and building a React+NextJS app. Starting today we are getting error below. Even after reseting cookies and localStorage get to login page then after I get this error.

Error: No key found in https://{some-domain-but–itisnot-my-domain}.us.auth0.com/.well-known/jwks.json with kid XXXXXXX

---

<div class="post-metadata">

**Author:** ![remus.ivan](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/remus.ivan/32/68771_2.png) [@remus.ivan](https://community.auth0.com/u/remus.ivan)\
**Post date:** [July 28, 2025, 9:57pm UTC](https://community.auth0.com/t/free-plan-nextjs-sdk-no-key-found-error/189696/2 "2025-07-28T21:57:17Z")

</div>

Hi @mohammad2,

Welcome to the Auth0 Community!

The “No key found” error is related to your application’s ability to fetch and use the correct public key from your Auth0 tenant’s JWKS endpoint, so given that your domain is not the one present, then the first thing to check is to make sure that the `AUTH0_DOMAIN` and `AUTH0_AUDIENCE` is set accordingly in your environment to your Auth0 tenant settings.

It is mentioned in our [Locate JSON Web Key Sets](https://auth0.com/docs/secure/tokens/json-web-tokens/locate-json-web-key-sets) documentation that

> We recommend that you cache your signing keys to improve application performance and avoid running into [rate limits](https://auth0.com/docs/troubleshoot/customer-support/operational-policies/rate-limit-policy)

Auth0 periodically rotates its signing keys for security reasons, so if that is the case and you are indeed caching the existing JWKS and not refreshing it, it might be looking for an old `kid` that is no longer in the current JWKS.

Our [Validate JSON Web Tokens](https://auth0.com/docs/secure/tokens/json-web-tokens/validate-json-web-tokens) documentation ( that i would definitely recommend checking regarding this matter ) outlines that

> All of our [backend API quickstarts](https://auth0.com/docs/quickstart/backend) use SDKs that perform JWT validation and parsing for you

so if you implemented one of our SDK’s this process should be handled automatically. As an extra troubleshooting step i would also recommend going through our quickstart steps once again. Otherwise, so if you are not using one of our SDKs the documentation linked above provides some insightful information on the steps that would have to be considered.

Thanks,  
Remus

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [August 11, 2025, 9:57pm UTC](https://community.auth0.com/t/free-plan-nextjs-sdk-no-key-found-error/189696/4 "2025-08-11T21:57:49Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.