Visual studio git failed with a fatal error authentication failed for

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

jasabalete opened this issue

Dec 9, 2015

· 41 comments

bug

Issue identified by VS Code Team member as probable bug

verified

Verification succeeded

Labels

I am using Visual Studio 2017 Community Edition (CE), and I have signed into my Microsoft account and I am connected to VSTS. I can see all my projects and repositories, but when I attempt to pull/fetch/push any changes I get the following error:

Error encountered while pushing to the remote repository: Git failed with a fatal error.
PushCommand.ExecutePushCommand

And accordingly for the fetch and pull commands too.

I installed Git for Windows on the Visual Studio 2017 installer and not only is it failing to work with VSTS, I am unable to work with any of my GitHub repositories too. Has anyone else noticed this? It’s happened on two of my machines so far.

Visual Studio 2015 Enterprise Edition (EE) and CE work completely fine for me.

It seems that this issue has gotten far more recognition that I thought it would which leads me to believe that this is an issue with how Visual Studio is dealing with Git. I have also noticed that every time I update Visual Studio, this problem pops back up, and I have to go through the steps in some of the answers below to get Git working again. I’m not sure why this is happening, and I also don’t know if Microsoft are planning to resolving this issue.

This is the error I was getting:

Git failed with a fatal error.
pull --verbose --progress --no-edit --no-stat --recurse-submodules=no origin

I tried all the previous methods, but they didn’t work. Later I found out that there were some conflicts in the code (see the Visual Studio 2017 output window).

I simply reverted the code and it worked.

answered Oct 26 ’17 at 9:02

answered Jun 5 ’17 at 19:18

I’m using GitKraken and Visual Studio 2017.

When GitKraken clones a repository, it leaves fetch address like «git@github.com:user/Repo.git», instead of «https://github.com/user/Repo.git».

To fix that, go to Team Explorer → Settings → Repository Settings → Remotes → Edit, and change «git@» to «https://» and «:» to «/».

I had this problem after changing the git access password!

I had to reset the credentials through the PowerShell console.

At the git repository folder level, the script was as follows:

git config --system --unset credential.helper

git config --system credential.helper store

git fetch

You will be prompted for the user and then the password.

The next command will no longer request authentication:

git fetch

answered Feb 6 ’19 at 13:20

I had a very similar problem and the instructions from a tech at Microsoft fixed it for me:

• Close all instances of Visual Studio.
• Open the Task Manager and check if any TFS Services are running. Select each of them and click on End Process Tree.
• Browse to the folder below and delete all the contents and folders in %LocalAppData%MicrosoftTeam Foundation{version}Cache
• Go to Control Panel -> User Accounts -> Manage your Credential -> Windows Credential, select the VSTS URL to remove it
• Then go to «C:UsersUSER NAMEAppDataLocalGitCredentialManagertenant.cache» and delete it
• Also go to «C:UsersUSER NAMEAppDataLocal.IdentityService» and delete it

answered Dec 3 ’19 at 22:43

I ran into this issue as well. I had sync’d my code earlier in the day so it made no sense that it suddenly gave this Git error. Restarting Visual Studio did not make any difference. After reviewing the above answers and not finding any clear solution, I decided to try syncing outside of Visual Studio using TortoiseGit which I already had installed. This worked. I was then able to sync within Visual Studio normally. If you don’t already have TortoiseGit, you may download it (free) from tortoisegit.org.

In my case, Windows had ran an update and was waiting to restart the PC. I hadn’t seen any notifications but, well… turning it off and turning it on again fixed the problem.

Try that first before monkeying with any of these Visual Studio directories and applications.

I got it working by removing username@ from http://username@asdf/xxx/yy/zzz.git in the repository settings:

Team Explorer → Settings → Repository Settings → Remotes → Edit

I had the same error pop up in VS 2017 when trying to delete a remote branch. The issue was that the branch was not on the server (using TFS2018 with GIT), but somehow Visual Studio did have it show up in the «remote/origin» section. This meant that I could not delete the remote branch (VS was giving out this error, while the server explorer didn’t show up the branch at all).

Here’s how to fix it (tested in VS 2017):

1. In Visual Studio, double click on your «rogue» remote branch;
2. VS should have now created a local branch from it;
3. Right click on the local branch, select «Unset remote branch»;
4. Right click on the local branch, select «Push branch»;
5. You should now have a true corresponding remote branch;
6. Delete the remote branch, then the local branch.

Hopefully it will help someone who ends up on this thread having the same issue as me.

answered Jun 13 ’19 at 12:43

I opened Credential Manager in Windows (not Visual Studio), selected «Windows Credentials», found my git:https//stash….com Generic Credential, clicked the bubble arrow down to make visible the User name and Password fields with Edit button. Clicked Edit, and put in my correct password there. Then started work right after that, no need to close anything.

AngelBlueSky’s answer worked partially for me. I had to execute these additional lines to clean the Git global configuration after step 4:

git config --global credential.helper wincred
git config http.sslcainfo "C:/Program Files/Git/mingw64/ssl/certs/ca-bundle.crt"
git config --global --unset core.askpass
git config --global --unset mergetool.vsdiffmerge.keepbackup
git config --global --unset mergetool.vsdiffmerge.trustexitcode
git config --global --unset mergetool.vsdiffmerge.cmd
git config --global --unset mergetool.prompt
git config --global --unset merge.tool
git config --global --unset difftool.vsdiffmerge.keepbackup
git config --global --unset difftool.vsdiffmerge.cmd
git config --global --unset difftool.prompt
git config --global --unset diff.tool

Then git config -l (executed from any git repo) should return only this:

core.symlinks=false
core.autocrlf=false
core.fscache=true
color.diff=auto
color.status=auto
color.branch=auto
color.interactive=true
help.format=html
diff.astextplain.textconv=astextplain
rebase.autosquash=true
user.name=xxxxxxxxxxxx
user.email=xxxxx@xxxxxx.xx
credential.helper=wincred
core.bare=false
core.filemode=false
core.symlinks=false
core.ignorecase=true
core.logallrefupdates=true
core.repositoryformatversion=0
remote.origin.url=https://xxxxxx@bitbucket.org/xxx/xxx.git
remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*
branch.master.remote=origin
branch.master.merge=refs/heads/master
branch.identityserver.remote=origin
branch.identityserver.merge=refs/heads/identityserver
http.sslcainfo=C:/Program Files/Git/mingw64/ssl/certs/ca-bundle.crt

Run the git status and git fetch commands to validate that it works from the command line.

Then go to Visual Studio, where your repositories should be back, and all sync/push/pull should work without issues.

After installing the last version of Git for Windows you must to open the configuration file to edit:

git config --global --edit

Click Insert, remove all the settings, click Esc, type :wq and, Enter to save.

Now you can clone the repository by Bash or IDE with a valid user.

I was getting similar issues. In Visual Studio 2017, with Rebase option I solved my issue.

I am having only a master branch. I rebase from master to origin/master (means to the same branch) and clicked Rebase. Before doing Rebase, the status was, I was committed my changes however not able to push/sync as my local branch base and Git code base was not synchronised state.

Compounded the problem by deleting the local repo so I could clone a fresh copy. I was faced with new error «git cannot be found Git failed with a fatal error.fatal: repository ‘xyz’ not found»

I tried everything suggestions i google about with no resolution.
The following simple step worked for me and I am adding it to the growing list of possible resolutions:

git config —get http.proxy result is http://google.com:80

this is not right so i got rid of it.

git config —global —unset http.proxy

answered Jun 26 ’18 at 15:25

answered Aug 7 ’18 at 8:17