-
Notifications
You must be signed in to change notification settings - Fork 7
Open
Description
I've been using Raisely CLI without issues lately.
After I added 2FA to my admin Raisely account, next time I tried to run raisely start I got prompted to log back in.
After entering my credentials, I got this error message:
× https://api.raisely.com/v3/login (401) failed with message: You must login again
√ Updating settings in .raisely.json...
node:internal/process/promises:289
triggerUncaughtException(err, true /* fromPromise */);
^
[UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "https://api.raisely.com/v3/authenticate (401) failed with message: You are not logged in with a valid token".] {
code: 'ERR_UNHANDLED_REJECTION'
}
Node.js v20.13.1
I get a very similar error if I run raisely start again (I'm not asked to log in anymore, just the error directly).
raisely start
******************************
Raisely CLI (1.8.3)
******************************
Could not decode token, is it a JWT?
node:internal/process/promises:289
triggerUncaughtException(err, true /* fromPromise */);
^
[UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "https://api.raisely.com/v3/authenticate (401) failed with message: You are not logged in with a valid token".] {
code: 'ERR_UNHANDLED_REJECTION'
}
Node.js v20.13.1
Thanks!
Metadata
Metadata
Assignees
Labels
No labels