-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request for meaningful terminus auth login
failure message
#182
Comments
Yes, I think it's reasonable to add a message here based on the http status so that a server busy 504 is not mistaken for a failed authentication. Looking at the code, this message is returned whenever the session cookie is not present, but that clearly doesn't account for all possibilities. Thanks for pointing this out. Will try to get it in eventually. |
@mikevanwinkle I think the best answer is to upgrade to our "real" login functionality that will let us ditch the whole cookie/scrape thing. Let's discuss this week. |
Hey guys, any update on this one? It's giving us some grief... |
So Terminus 2.0 will have abetter login experience. But it's still weeks out from code parity with this version. You can track progress here: https://github.com/pantheon-systems/cli/tree/develop |
OK we will just keep mashing the "update all" button for now :) |
Hey @jeffreywilcox / @jbutkus I believe we also have a specific support thread open with you guys to debug the login issue you are having specifically. While giving you better error messages would be good, even better would be preventing your logins from timing out. My guess is there's something inefficient on our end that's occasionally getting hung up because of the large volume of sites that you have in your account; we should be able to fix this. |
When
terminus auth login
fails it just outputs "Error: Authentication failed. Please check your credentials and try again.".In some cases I know it's not true, because we use a script to do the deployments, which has a configuration file with password, and that one doesn't change.
Please add a meaningful authorization message, like
/Server is overloaded. Please retry in (\d) seconds./
. I provide a regexp-like message, as we would be parsing it and using response as a guideline.The text was updated successfully, but these errors were encountered: