I have a situation where login for a protected element of my website works fine on the preview site and production but locally is erroring with the unknown client error. I’ve tried multiple browsers; Firefoc, Brave, Duck Duck Go, ToR, multiple ports; 3000, 5173, 8888 react sdk and raw auth0 requests. I’ve tried a fresh NPM install, I’ve tried npm dev and netlify dev but all produce the same error. What is even more bizarre is the error summary on the logs page provides the application id and the unknown client and they’re identical. The only difference from between when it worked locally and now is I’m using a different Macbook. That’s it.
Anyone else experienced this and does anyone know how the heck I can get it working locally again?
I am sorry about the delayed response to your question!
Could you let me know if the issue persists when using an incognito window or after clearing the cache of the browsers? Did you use these browsers to access the production environment previously?
Also, I would suggest to double check if you are not using the client ID from the production environment instead of the one in the development.
For additional troubleshooting, can you share with me the tenant name via a DM to check out the errors you are receiving and the configuration of the application/tenant?
The whole thing was working fine locally on my old MacBook. The trouble only started when I tried to locally on my new MacBook. The same tenant worked across local host, my preview environment and my production environment. Since upgrading, local host no longer works. I tried all browsers in incognito mode, VPN on, VPN off, netlify dev and nothing works. The odd thing is, nothing about by Auth0 tenant changed. The only thing that did was my MacBook.
It’s got me stumped. Any pointers would be greatly appreciated.
Thanks for the extra information on the matter. As far as I have double checked regarding the error you are receiving, it could only be caused by a misconfiguration in your new environment where it is using a different client id then the one you have set before/have been provided by the Dashboard.
My suggestion would be to check if you are using the proper grant on your new device and also check your environment’s cache/ .env file configuration inside it.
Have you double checked if the client id mentioned inside the error exists in the tenant used for local testing and it is not pointing to a different one?
If you can provide the name of the tenant inside a DM I would gladly check the errors and configuration myself for additional insight.