Reputation: 67213
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?
Upvotes: 143
Views: 243065
Reputation: 3617
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.
Upvotes: 0
Reputation: 554
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.
Upvotes: 1
Reputation: 65860
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.
Upvotes: 0
Reputation: 21
Deleting the token from the Windows Credential Manager worked. Visual studio asked to reenter the credenial.
Upvotes: 2
Reputation: 1520
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.
Upvotes: 0
Reputation: 64
I was using Azure Personal Access Token
, so my steps to resolve it were:
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:")That resolved my issue.
Hope this helps someone!
Upvotes: 1
Reputation: 301
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.
Upvotes: 0
Reputation: 91
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!
Upvotes: 5
Reputation: 41
Go to Windows Credentials Manager and update the credentials for GIT.
Upvotes: 3
Reputation: 24224
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)
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
Upvotes: 8
Reputation: 2488
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.
Upvotes: 0
Reputation: 51
2 to 5 minutes to setup!
ssh-keygen -C "[email protected]"
Upvotes: 1
Reputation: 81
I had this problem and the instructions from a tech at Microsoft fixed it for me:
Upvotes: 2
Reputation: 4432
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'.
Upvotes: 0
Reputation: 237
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.
Upvotes: 0
Reputation: 347
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
Upvotes: 12
Reputation: 379
I have faced the same issue. The error output window looks like this:
Following the steps resolved the issue:
Below Generic Credential, choose an entry of the git & update password.
Password should be same as windows(system) login password.
Upvotes: 37
Reputation: 155
My solution was a little bit different and faster :)
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).
Upvotes: 3
Reputation: 8320
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.
Upvotes: 1
Reputation: 599
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
Upvotes: 15
Reputation: 2803
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.
Upvotes: 256
Reputation: 845
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.
Upvotes: 6
Reputation: 1468
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.
Upvotes: 3
Reputation: 8343
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.
Upvotes: 18
Reputation: 141946
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
Open your account (VS Online account)
-> click on your name on the top right
-> My Profile
-> Credentials.
and set it up.
Upvotes: 38