“ git push heroku master”仍在请求身份验证

我已经执行了:

$ heroku login

但是,当我试图推动,我仍然要求认证:

$ git push heroku master
Username for 'https://git.heroku.com': <email>
Password for 'https://<email>@git.heroku.com':

然后我得到一个警告: 不要使用 Git 进行用户名和密码身份验证。

我再次运行 heroku 登录并成功地进行了身份验证,但我仍然得到同样的失败。

我看过遥控器了:

$ git remote -v
heroku https://git@heroku.com/appname.git (fetch)
heroku https://git@heroku.com/appname.git (push)

我还生成了一个新的公钥,并将其传递给 Heroku,然后对其进行验证: https://devcenter.heroku.com/articles/keys

我使用的是 Windows8,Git1.9.5。

46991 次浏览

I got around this by logging in with the following :

username : email used to register to heroku (Also been able to leave this field blank)

password : heroku auth token (API Key)

where the auth token can be retrieved by $ heroku auth:token or via the Account Settings in Heroku

Pardon for the late reply, but I have fixed my problem two months ago. (Just haven't marked the question as answered. /noob)

SSH Fingerprint not authorized on Heroku after git restore

I have exactly the same problem. The reason in my case, I used accidentally window console instead of Git bash

This happens because git and heroku aren't using the same _netrc file. This is something I'm trying to fix, but you can help me out by finding where your _netrc file should be and where the CLI is putting it.

The following will output potential sources of where the _netrc file could be:

> echo %HOME%
> echo %HOMEDRIVE%%HOMEPATH%
> echo %USERPROFILE%

You could try to add the _netrc file into one of them to find the one that matches. Let me know which has the _netrc file, and where you are able to put it and have git pick it up by not asking you for the username/password.

Also check your .gitconfig to see if there are any git credential helpers, that may be causing an issue.

I had the same problem (git couldn't authenticate). It happend that GIT wants to read auth data from %HOME%/_netrc file and on Windows you don't have this variable (only %USERPROFILE% and %HOMEDRIVE% + %HOMEPATH%)

i set HOME to %USERPROFILE% (the place where heroku saved _netrc file) and GIT started working

What I did was open git bash instead of command prompt and type "git push heroku master". It worked :D

Renaming the _netrc file to .netrc on Windows 7 in the userdir worked for me.

..after trying all the steps in many other tutorials.

Run the 3rd command in cmd in your userdir or the whole combo:

setx HOME %USERPROFILE%
cd %HOME%
REN _netrc .netrc

From the Heroku documentation

Enter the following commands:

# Enable SSH authentication
$ heroku create --ssh-git


# Redirect tall HTTPS calls to SSH
$ git config --global url.ssh://git@heroku.com/.insteadOf https://git.heroku.com/

First find the _netrc file that is created by heroku. In windows it can be found in C:\Users\User Name\_netrc.

That file contains credentials for git.heroku.com

machine git.heroku.com
login abcd123@gmail.com
password xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

Use that login and password when ask for authentication after $ git push heroku master command

I fixed this by changing the http address to ssh://git@heroku/...

If anybody else is trying to solve this on cygwin: http://www.railszilla.com/git-push-heroku-master-authentication/start rewriting to SSH transport did the trick for me:

git config --global url.ssh://git@heroku.com/.insteadOf https://git.heroku.com/

You have probably logged into heroku in two terminals, and if you try to run a command on first terminal, it will report such error, as new authentication was made in the second terminal.

Either login again with heroku login and run commands in that terminal, or run commands in that second window (if you have it still open).

Username: the email you used for registering to Heroku
Password: the API key which Heroku provides you with, in your Account Settings on Heroku website

This worked for me

This topic is old, I know.

However, none of the previous solutions worked for me.

My problem was that "Windows Credentials" (os: Windows 10) had another credential previously associated with Heroku (company account) and used this instead of the new one (my personal account).

I had to go to: "Control Panel\All Control Panel Items\Credential Manager" (from Control Panel), and modify all the credentials: https://git.heroku.com (and all those associated with "heroku" word) with the account current.

However, the password I placed the Key API that is displayed in "Dashboard" of the site and the command works: git push heroku master.

7 hours that life will not give me back. :/

My 2 cents.

If someone is still struggling with this, this answer helped me a lot Use Heroku API key.

First, as @Raziza O mentioned in a comment, to get heroku API key

https://dashboard.heroku.com/account. Roll down the screen and hit the reveal button.

Then, just run git push https://heroku:$HEROKU_API_KEY@git.heroku.com/$HEROKU_APP_NAME.git HEAD:master

I had the same problem on windows and get it sorted just using the PSW available on the on _netrc file it can be found in C:\Users\User Name_netrc.

I hope it can help.

Simply write: $heroku login
It will take you to the web login. Enter your credentials there, and you will be logged in via CLI as well.

To generate a long term heroku token use:

heroku authorizations:create

Sample Output:

Creating OAuth Authorization... done
Client:      <none>
ID:          XXXXXXXX-XXXX-4c9c-85f2-554f0f0c14fa
Description: Long-lived user authorization
Scope:       global
Token:       XXXXXXXX-XXXX-4ad5-ac64-44bbc01c2d95
Updated at:  Wed Mar 04 2020 12:00:00 GMT+0000 (Greenwich Mean Time) (less than a minute ago)

Then use the following info for git:

username: blank (type the word blank)
pass: XXXXXXXX-XXXX-4ad5-ac64-44bbc01c2d95

It was possible to log in using Heroku API Key (Account Settings -> API Key) as mentioned by @andy mccullough, however, logging in was needed every time.

git fetch

resolved the issue in my case.

For me it happened in 2 scenarios: when using in the first time or when it goes a long time without using git and it automatically logs out.

In both cases you just need to run heroku login and it will open the browser in order you can start a new session.