Authentication failed for https://xxx.visualstudio.com/DefaultCollection/_git/project

Question

I am trying to use git to push my repository to a visual studio team services project, but I get the error:

fatal: Authentication failed for (url of team project)

I am using the commands:

git remote add origin
     https://XXXXXXX.visualstudio.com/DefaultCollection/_git/project

git push -u origin -–all

Any idea of the fix for this?

How are you authenticating? Personal access token? Alternate access credentials? — Daniel Mann, Mar 07 '16 at 00:10
Related post - [git clone: Authentication failed for ](https://stackoverflow.com/q/51424051/465053) — RBT, Feb 11 '19 at 12:28

score 256 · Answer 1 · answered Aug 10 '18 at 16:03

256

I had a same issue recently (visual studio 2017 & Windows 10), and solved it using the following method:

Control Panel --> Credential Manager --> Manage Windows Credentials --> Choose the entry of the git repository, and Edit the user and password.

Done.

answered Aug 10 '18 at 16:03

kxiaocai

2,803
1
12
8

5

I used this method when my Personal Access Token expired. Go to <>/_usersSettings/tokens to create a new one and then set it as the password in Credential Manager. – Even Mien May 24 '19 at 17:23
God.... thank you. This is the only solution that worked for me. – Dominik Sajovic Nov 03 '20 at 16:27
Depending on what version of VS you have, you can go to terminal and type git push and it'll give you option which way to authenticate for git enterprise, I chose 'wincred' and it took it. You need to set the Git Enterprise url in settings first. – Smart Coder Mar 02 '23 at 20:17

score 38 · Answer 2 · edited Jun 20 '20 at 09:12

38

If you wish to use GIT CLI and not interact with the build in GIT wrappers in Visual Studio you need to enable Alternate Authentication Credentials

How?

Open your account (VS Online account) 
-> click on your name on the top right 
-> My Profile
-> Credentials.

and set it up.

edited Jun 20 '20 at 09:12

Community

1
1

answered Mar 07 '16 at 01:18

CodeWizard

128,036
21
144
167

4

Security is a separate item in the menu now. If you click profile, it goes to a very different page. – Lukos Sep 19 '16 at 14:00
2

it may vary between versions. this is why i added screenshot – CodeWizard Sep 19 '16 at 14:45
2

I have not had to do this. Using a PAT for Git Bash seems to be working just fine. – Josh Gust Jan 07 '19 at 21:05
2

Please use a PAT instead of alternate credentials. – Edward Thomson Feb 19 '19 at 10:13
2

Enabling Alternate credential is not recommended: domain credentials transit in clear-text and may ends up in Application Tier IIS logs – Giulio Vian Aug 28 '19 at 09:09
"Alternate credentials have been disabled on this organization" – Enrico Apr 05 '21 at 11:53

score 37 · Answer 3 · edited Feb 19 '19 at 10:50

37

I have faced the same issue. The error output window looks like this: authentication failed Image

Following the steps resolved the issue:

Go to Control Panel --> Credential Manager --> Windows Credentials
Below Generic Credential, choose an entry of the git & update password.
Password should be same as windows(system) login password.

edited Feb 19 '19 at 10:50

Adrian W

4,563
11
38
52

answered Feb 19 '19 at 09:44

Anusha M Shetty

379
3
4

on giving my machine password didn't worked, i generated personal access token (PAT) from VSO and used it. then in VS2019 am able to pull latest. – Pavan N Sep 03 '21 at 08:04

score 18 · Answer 4 · answered Mar 07 '16 at 15:22

18

The best option today is to install https://github.com/Microsoft/Git-Credential-Manager-for-Windows that supports VSO, GitHub and is improving every month.

answered Mar 07 '16 at 15:22

Giulio Vian

8,248
2
33
41

2

@dotnetdev Please accept this answer 'cause this is a recommended way of resolving the issue. – Deilan May 17 '17 at 07:14
1

This is also available for Mac and Linux at https://github.com/Microsoft/Git-Credential-Manager-for-Mac-and-Linux - worked perfectly for me without having to add less-secure "alternative credentials". – Breeno Oct 31 '17 at 13:02
1

This is indeed the "de facto" solution that microsoft provided. Other solutions that indeed work here shall be considered as tweaks. – Stephane Oct 13 '18 at 20:08

score 15 · Answer 5 · answered Dec 12 '18 at 10:53

15

With VSTS the url is, When you copy git clone url from vsts you always get

https://orgname@dev.azure.com/org/project/_git/repo

Replace orgname@ with your alternate username that you would have created in VSTS -> profile -> Security.

final git url -

https://alternateusername@dev.azure.com/org/project/_git/repo

answered Dec 12 '18 at 10:53

Max

589
5
6

I have multiple logged in credentials -- this was the easiest and most direct way to ensure that it uses the correct cached credential. – bryanbcook Dec 18 '20 at 23:35

score 12 · Answer 6 · answered Mar 26 '19 at 18:51

12

I had the same problem, I tried to update my password using windows credential manager, it still didn't fix the issue

Control Panel --> Credential Manager --> Manage Windows Credentials --> Choose the entry of the git repository, and Edit the user and password.

I then deleted all the git related entry in credentials manager and then tried to use Git using visual studio, this time it prompted for new credentials

answered Mar 26 '19 at 18:51

Web Application Developer

337
2
9

This worked for me as well. Good solution. – JKH Jul 07 '21 at 15:03

score 7 · Answer 7 · answered Jun 05 '20 at 00:36

For Linux users who can't use Microsoft Credential Manager. This is the only solution I found aside from using ssh. You need to generate the credentials in the repository view (See images below)

And the result is:

Copy the password!. Azure devops doesn't store it and you won't be able to see it again!

NB: As of 2020 Alternate credentials have been disabled check Microsoft blog

score 6 · Answer 8 · edited Feb 02 '18 at 14:41

6

Delete '.git/config' and try again. Attention this will may reset some git settings too!

I've tried alternative credentials and Personal Access Token for many times with right credential and it kept telling me "fatal: Authentication failed".

Finally, I found there is a file named ".git/config" located at the root of my Repo. I deleted this file and type in my credentials again, it worked.

edited Feb 02 '18 at 14:41

Bruno Bieri

9,724
11
63
92

answered Oct 23 '16 at 09:13

Longfei Wu

815
10
9

score 5 · Answer 9 · answered Sep 25 '20 at 11:43

5

Control Panel --> Credential Manager --> Manage Windows Credentials --> Choose the entry of the git repository, and Edit the user and password. Delete '. git/config' and try again. Attention this will may reset some git settings too!

answered Sep 25 '20 at 11:43

Namitha

81
1
7

1

OP didn't said anything about this being in cpanel. – marcogmonteiro Sep 25 '20 at 13:52
I only had to delete the entry from Windows Credentials to resolve my issue. – Kevin May 11 '21 at 22:05
@Kevin - You have to Edit User name and password in windows credentials, then it will resolve. – Namitha May 13 '21 at 14:06

score 3 · Answer 10 · answered Sep 13 '17 at 10:56

I suddenly started receiving this error when attempting to push changes from VS2017 to a VSTS Git repository. This functionality had worked the day before.

I checked my git.log file and saw a different exception :-

19:43:57.116665 ...zureAuthority.cs:184 trace: [ValidateCredentials] server returned: 'Unable to connect to the remote server.

I downloaded the latest Git CredentialManager source from Gits Credential Manager repo and debugged it.

Once authenticated, the following exception occurred :-

No connection could be made because the target machine actively refused it 127.0.0.1:8888

I then realised that I had recently setup Fiddler to act as a proxy for all services as per the article capturing-traffic-from-.net-services-with-fiddler

Once I ran Fiddler, I was able to successfully connect.

Antonio Buonaiuto · Answer 11 · 2019-02-04T11:42:58.927

My solution was a little bit different and faster :)

Go to Windows Credentials (Start-> Windows Credentials) and remove credentials for your repository (they starts with git:xxx)
Go to VSCode and in Terminal write:

config credential.helper wincred
Go to Visual Studio (no VSCode) and make a git pull. A popup will show asking for credentials. Put your credentials for the repo
Go to VSCode and make a git pull. Credentials were automatically fetched from wincred store

Credentials are automatically created and stored in wincredentials, so the next time you cannot be asked for credentials. (also a Personal Access Token will be provided from visualstudio.com if you are using DevOps hosted git repo).

Start-> Windows Credentials works like a charm! Thanks! – Highriser Aug 08 '19 at 06:57 — Highriser, Aug 08 '19 at 06:57

score 3 · Answer 12 · answered Jul 20 '20 at 15:47

3

Go to Windows Credentials Manager and update the credentials for GIT.

answered Jul 20 '20 at 15:47

Avinash Prabhakar

39
3

score 2 · Answer 13 · answered Dec 03 '19 at 22:30

I had this 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%\Microsoft\Team 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:\Users\USER NAME\AppData\Local\GitCredentialManager\tenant.cache" and delete it
Also go to "C:\Users\USER NAME\AppData\Local.IdentityService" and delete it

score 2 · Answer 14 · answered Aug 26 '21 at 20:47

Deleting the token from the Windows Credential Manager worked. Visual studio asked to reenter the credenial.

Go to Control Panel>Credential Manager
Locate the git credential
Click the down arrow to expand the credential and hit "Remove"
Reopen Visual Studio. Go to Team Explorer and "Connect". It will ask for you to re-enter your credential

score 1 · Answer 15 · answered Dec 15 '18 at 11:20

I've tried lots of options, but the one that worked for me was to:

Download the Git Password Manager from its Releases section
Try to do simple git fetch which will automatically bring the window(alternate to default windows one for example) and ask to enter username and password but with more elegant way than the standard one.

After correctly entering the credentials it worked, though I was getting an error before.

P.S. If you are getting "Wrong Credentials" kind of errors always check if the repository username and password are correct. If you hesitate just reset the password and try to use the same one in the Git Password manager window.

score 1 · Answer 16 · answered Mar 14 '20 at 06:21

1

2 to 5 minutes to setup!

Create your SSH keys (~/.ssh/)

ssh-keygen -C "jamal@fabrikam.com"

Add the public key to Azure DevOps Services/TFS
Clone the Git repository with SSH

Source

answered Mar 14 '20 at 06:21

jnermano

51
5

score 1 · Answer 17 · edited Apr 12 '21 at 17:22

I was using Azure Personal Access Token, so my steps to resolve it were:

Create a new one (PAT) and copy the password generated.
Go to Control Panel -> Windows Credential Manager
Search for those git url: git:https://dev.azure.com/{site} and git:https://{site}@dev.azure.com/{site} (both url could be different in your case, but they should start with "git:")
In both credentials, edit user as "PersonalAccessToken" and paste the password of the PAT that you'd generated before.

That resolved my issue.

Hope this helps someone!

score 1 · Answer 18 · answered Aug 11 '22 at 03:10

For me, this happened out of nowhere. Turns out my token expired without me noticing. Just had to go to settings -> Personal Access Tokens -> On the drop-down select expired -> Regenerate -> Grab the new token and store it -> When VS Code asked for pass used it and voila, problem solved. Hopefully this help someone, took me a few minutes to figure out.

score 0 · Answer 19 · answered May 04 '19 at 09:03

All i needed were the correct credentials. while deploying to a web app, i had to go to Deployment Center, Deployment Credentials. And then use either the App Credentials or create User Credentials. After this, delete the cached credentials on the local machine (windows: Control Panel\User Accounts\Credential Manager). run "git push webapp master:master" again, enter either of the Deployment Credentials. This worked for me.

score 0 · Answer 20 · answered Oct 07 '19 at 08:21

In the case you are on something else then windows and your boss is forcing you to use azure devops, and you don't want to use SSH, and you want to use to plain old way, do the following.

You have to enable 'Alternate credentials' (I know it's annoying) or you need to create an access token. Creating an access token in this case is more like a temporary random password. If you use the windows tooling it is done for you.

Any way, go to Security in the profile context menu in the right upper corner.

Then if your boss/manager/dude that has the admin rights is favoring you the 'Alternate credentials' are enabled. Otherwise accept your fate and generate a 'Personal access token'.

score 0 · Answer 21 · answered May 27 '20 at 06:25

After struggling with git authentication and azure devops server and trying other answers this tip here worked for me.

Using Visual Studio? Team Explorer handles authentication with Azure Repos for you.

Once I connected to the repo using Team Explorer I could use command line to execute git commands.

score 0 · Answer 22 · answered Nov 21 '20 at 21:39

If you are entering your credentials into the Visual Studio popup you might see an error that says "Login was not successful". However, this might not be true. Studio will open a browser window saying that it was in fact successful. There is then a dance between the browser and Studio where you need to accept / allow the authentication at certain points.

osynavets · Answer 23 · 2021-07-19T08:20:59.287

0

Removing git origin and adding again helped me.

Looking at the origin url I found that url contained some hash value (it looked like some auth value). Therefore, removing origin and adding again fixed the problem.

edited Jul 19 '21 at 08:20

answered Jul 16 '21 at 11:41

osynavets

1,199
1
12
22

1

The answer needs to be improved, to include explanations. – Slavik N Jul 17 '21 at 15:11

score 0 · Answer 24 · answered Feb 09 '22 at 17:52

0

09-02-2022

Windows 10 Pro PC

My issue was the outdated Git for Windows package. So I got the latest version from here and no issues now.

answered Feb 09 '22 at 17:52

Sampath

63,341
64
307
441

whatever · Answer 25 · 2023-06-18T10:10:00.423

Today I was also facing a "fatal: Authentication failed for [REPO-URL]" when trying to push updates from my local repo to the remote Azure DevOps repo. Since for the initial clone of the remote repository I had used a personal access token generated in the Azure DevOps website (git clone -b [BRANCH-NAME] https://[USERNAME]:[TOKEN]@dev.azure.com/[ORG]/[PROJECT]/_git/[REPO]) and since it had expired, I first generated a new access token from the ADO website, I then opened the local "config" file inside the local .git folder and in it I updated the token in the url to the remote repository. I re-executed my push and everything worked as expected.

Authentication failed for https://xxx.visualstudio.com/DefaultCollection/_git/project

25 Answers25

How?

Linked