The specified token is not valid immediately after installing
See original GitHub issueI ran the following:
npm i -g now
now
and got:
> Error! The specified token is not valid
now version 16.3.1
Disclaimer: I had previously tried and uninstalled now.
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
I'm getting the "Your token is invalid [401]" error
This error means that the app has experienced an authentication problem and can't verify your account information. If it occurs, you'll be automatically ......
Read more >The specified token is invalid is Invalid when using Client ...
I am able to get an Access token using Insomnia Rest Client and Client Credentials. But when I call the API with the...
Read more >Troubleshoot Invalid Token Errors - Auth0
Error Message: The ID token cannot be validated because it was signed using the HS256 algorithm and public applications (such as a browser)...
Read more >How to re-issue a token on a NetBackup 8.1.x client ... - Veritas
Solution · Click on Security Management --> Certificate Management · Right click on the host that was reinstalled, select Generate Reissue Token
Read more >What is an 'invalid token' when I try to reset my password?
If you're trying to reset your password and you receive an error citing an “invalid token” or asking you for your token, it's...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi @imyjimmy
This error message could be improved.
You probably need to run
now logout
and thennow login
to generate a new token.Yes, the UX on this error could be much better. I found this via Google, but simply logging me out and re-initiating the log in process would have been a much better experience than some cryptic error message.