You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The log in method is just there as a backup option if all other methods fail. The best way to handle the log in is to just log in via the Web UI and claim the server and then re-run the script.
While there is a PIN login flow available, it's not worth implementing since it would require you to log in through your browser, at which point you're just back to claiming your server.
If I get time I'll see if we get enough info back from the API call to at least provide an informative error message telling you to log in through the Web UI first.
Hey, I'm just installing this for the first time, and I think I'm running into this issue as well. But I'm already logged into my server, and have been for a while. Everything is good. But I can't log in with the script, so it's not allowing me to automate installing the beta releases. Is there any way around this? I don't want to turn off MFA.
EDIT: So, I just disabled 2FA, then set up the script, the re-enabled 2FA. Seems like that worked. Will that still work moving forward?
No description provided.
The text was updated successfully, but these errors were encountered: