https://netsuiteprofessionals.com logo
Join SlackCommunities
Powered by
Anybody getting this error today with SDF and WebS...
# sdf
a
Anybody getting this error today with SDF and WebStorm: Invalid login attempt. There was an error when communicating with the server. Check your user credentials. If your login uses token-based authentication, issue a new token.
👍 1
a
It looks like your token was revoked from account or something.
Was it a SB account by any chance?
a
Is happening with any account, any SDF project, manually removed account and add it back and issue new token, still same error.
There is a log file where I can see a verbose log of what is happening?
Im using WebStorm UI and nothing change since last week when everything was working correctly, the only thing that changed is my location. I'm in Mexico this week.
a
No Idea why is this happening, working fine for me. Let's see if someone else is experiencing the same. In meanwhile if you are blocked please do contact Netsuite Technical Support.
@alien4u can you login to your account via UI?
a
Yes I can login to the account through the UI perfectly fine, I can also remove and issue new tokens from WebStorm UI...
@Ali Syed (NS DevTools QA) If I switch to basic authentication using Administrator Role it works properly, the problem is with Token Based Authentication.
a
Okay. Thanks for the info I will check if i can find something related.
a
@Ali Syed (NS DevTools QA) Even with SDF CLI properly configured it does not work: sdfcli authenticate -authid authkey-string
I'm able to login in the Browser and then I get this: Authenticating... The authentication process failed. The server returned an error or could not respond. Review your authentication details and try again.
t
Not sure if it helps but this has happened to me a few times as well. When switching to a project and switching from the sandbox to the production account it gives me this error for one client we have
I always check and it seems to have lost the token. It says it doesn't exist when I try to remove it. I'm able to just add a new one and then connect again.
a
@alien4u still same? or something changed?
a
It was a date/time issue, I manually set the time in my computer to Arizona Time, but I was in a different time zone. Then the token is generated using the timestamp, and that was creating the issue. It was funny to troubleshoot.
Open in Slack
PreviousNext
Powered by