heroku / legacy-cli

Heroku CLI
https://cli.heroku.com
MIT License
1.37k stars 380 forks source link

Heroku CLI Authentication Failure #1123

Open ghost opened 10 years ago

ghost commented 10 years ago

I cannot login to heroku through the "heroku login" command in the CLI. I have two accounts, both of which I can login to without trouble online, but not in the command line. Neither account shows any problems in production or development on the heroku support page. I opened a ticket with heroku support (#122936) and the responder asked me to try a few different things. First off he asked me to delete the .netrc file on my computer and try authenticating again, I did that a few times but it didn't help. He then asked me to run this command in git bash: EXCON_DEBUG=true heroku auth:login The output I got from that command was this: output

Finally, this morning I tried installing ruby and the heroku toolbelt onto a computer that had never had either of them, and attempted to authenticate through the command line on that computer but I still got the authentication failed message. The person from Heroku support that had been attempting to help me said that the problem I was having appeared to be with the heroku toolbelt and that I should open an issue here, so here I am.

josmardias commented 10 years ago

I'm running on the same issue. If I enable two factors authentication, I will reach the two facetor step, and my login will fail after it. If I disable it, my login will fail after inserting the password.

$ cat /etc/redhat-release 
Fedora release 20 (Heisenbug)

$ uname -r
3.15.6-200.fc20.x86_64

$ ruby -v
ruby 2.0.0p353 (2013-11-22 revision 43784) [x86_64-linux]

$ heroku version
heroku-toolbelt/3.9.6 (x86_64-linux) ruby/2.0.0
josmardias commented 10 years ago

Worked on a fresh enviroment, running

$ gem install heroku
$ heroku login
silverwind commented 10 years ago

Worked on a fresh enviroment, running

$ gem install heroku $ heroku login

This just worked for me too.

trimble commented 7 years ago

If this is cleared up now, maybe we can close this issue?

/cc @dickeyxxx