Git push results in "Authentication Failed"

Question

I have been using GitHub for a little while, and I have been fine with git add, git commit, and git push, so far without any problems. Suddenly I am having an error that says:

fatal: Authentication Failed

In the terminal I cloned a repository, worked on a file and then I used git add to add the file to the commit log and when I did git commit, it worked fine. Finally, git push asks for username and password. I put those in correctly and every time I do this, it says the same error.

What is the cause of this problem and how can I fix it?

The contents of .git/config are:

[core]
        repositoryformatversion = 0
        filemode = true
        bare = false
        logallrefupdates = true
[remote "origin"]
        url = http://www.github.com/######/Random-Python-Tests
        fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
        remote = origin
        merge = refs/heads/master
[user]
        name = #####
        email = ############

Isobath

what is your username on github and what are the contents of .git/config? – Concupiscent

add it to the question, comments dont cope with long text – Concupiscent

Yeah sorry, I started the comment out of habit then changed it. – Isobath

Your url doesn't look right. I think it should start with https://, not http://. – Geyserite

Changed to https... didn't work. – Isobath

erm...you should really delete your username and password out of this question.... – Morgue

I will delete my username. I didn't put my password on here. – Isobath

Did you do a two factor authentication? – Canonist

if your using androidstudio 2.1 beta then its bug , upgrade to beta 2 (3 mb update file) , this worked for me – Pyromania

if you encounter the same error but for git pull, then one option is to try switch from HTTPS to SSH protocol. – Fournier

I got problem resolved with the help of - click here – Drucill

@Drucill Good point. This actually comes from my answer: https://mcmap.net/q/19885/-git-push-missing-or-invalid-credentials-fatal-authentication-failed-for-39-https-github-com-username-repo-git-39 – Wallie

Related post - git clone: Authentication failed for <URL> – Scout

It would be very useful if the question indicated what Operating System you are working on. I found an answer below for Windows very useful to me. But I have no idea if it is a useful answer to the original question. – Abernathy

Answer 1

If you enabled two-factor authentication in your GitHub account you won't be able to push via HTTPS using your accounts password. Instead you need to generate a personal access token. This can be done in the application settings of your GitHub account. Using this token as your password should allow you to push to your remote repository via HTTPS. Use your username as usual.

Creating a personal access token

You may also need to update the origin for your repository if it is set to HTTPS. Do this to switch to SSH:

git remote -v
git remote set-url origin [email protected]:USERNAME/REPONAME.git

Tsosie

Indeed. +1. I present PAT here https://mcmap.net/q/19886/-github-https-and-mac-application and detail the process there: https://mcmap.net/q/13188/-configure-git-clients-like-github-for-windows-to-not-ask-for-authentication – Wallie

I needed to freshly generate my rsa keys for normal Git operations to work after enabling 2FA. – Lilithe

Thank you! Just had this error and this helped, just to point out. Once you've created your personal access token you copy that then when your pushing the repo, it'll ask for your username and password. Paste the Access Token in the Password – Andonis

you can also do git remote add origin https://username:[email protected]/username/repo.git to store your personal access token. – Circumflex

It works! However I am a bit surprised that my ssh key was not being picked up. – Educatory

For me, all I had to do was enable SSH authentication from my local machine on my GitHub account, and then switch to the ssh git remote address; help.github.com/articles/changing-a-remote-s-url – Mavilia

Thanks @Mavilia - switching to ssh worked for me help.github.com/articles/… – Huonghupeh

Documentation is here: help.github.com/articles/… – Bearer

updated the remote from https to ssh in the steps to this solution and it worked perfectly. Thanks! – Equi

The mistake I made was thinking the Personal Access Token was the friendly name. After regenerating the PAT I realised it was actually a GUID - Doh! – Larghetto

This answer does not explain what to do in case two-factor authentication is not enabled (which it isn't by default). – Quesada

They must notify people who have enabled TFA about this! How am I supposed to know that without intentionally scrolling to Github Help, what I don't usually do even when something happens. – Isolative

What happens if we want multiple users to do that? git remote add origin will not work as there can only be one oriigin – Stonework

anyway to automate the method @Circumflex posted ? thanks. – Antithesis

And the token will be remembered for future pushes! – Scarron

Now, I am getting a new error: Git: Host key verification failed. – Fabe

This answer is plagiarised at GitHub by John Mifsud. There isn't any attribution whatsoever. – Egyptian

So eveyrone who collaborates need you to generate a personal access token every time they want to commit or clone? – Platelet

only solution when there is credentials in he remote url! thanks. – Newsmagazine

2022/23 suggestion — Git Credential Manager. Github docs – Meal

Answer 2

On Windows, try the below steps to edit or remove the saved credentials:

1. Click Start
2. Type: Credential Manager (on Windows 10, this is under "Start → Settings". Then search for "Credential Manager")
3. See the Windows Credentials Manager shortcut and double-click it to open the application.
4. Once the application is open, click on the Windows Credentials tab.
5. Locate the credentials that you want to remove/update. They will start with "git:" and might begin with "ada:"
6. Click on the credential entry. It will open a details view of the entry.
7. Click Edit or Remove as required and confirm.
8. Later rinse and repeat as necessary.

Able

In my case it is not in "Windows Credentials" but is on "Generic Credentials". Remove the credential do the trick. – Testudo

You can open the above window by (windows + R) -> "control /name Microsoft.CredentialManager" – Vague

The credentials may be there, but without 'git:' in front of it. That is not going to work. It needs to start with 'git:' – Frisk

My employer set windows authentication to Git Hub, so every time I changed my windows credentials I had to update it for source control. Your answer worked. – Delfinadelfine

Fantastic answer. We maintain an internal BitBucket repository, where each of our account credentials are authenticated to our organization. Recently all of my repositories became unavailable for pushing code changes. While I had been able to change credentials on a case per case basis, I really did not want to do this for every project. @Pradeep's approach allowed me to solve the underlying cause, which was more than simply a password change. Our organization recently changed the name of the internal domain, so by editing the credentials centrally, I was able to fix all of my projects. – Latin

Yes, that was the issue for me...needed to update the password to access TFS – Lind

Thank you Although the Edit did not fix it. I had to remove the entry under Generic Credentials and then issuing git clone on git cmd app prompted to enter user crendentials. – Farewell

I had to add new entry into Windows Credential Manager (generic credentials) manually despite there was an existing entry already. The URL looks like: git:https://192.168.1.10 (TFS Server). – Congruency

This should be the selected answer. – Excommunicatory

sometimes, the git entry doesn't show up in "windows credential manager". It didn't show up for me in my win11 laptop. So, I went and edited my %userprofile%\.gitconfig file and saved it. then windows prompted me for the password when I executed "git pull" command. This time, after I entered the correct new password, I saw that "windows credential manager" had created an entry for git! – Charleencharlemagne

This definitely should be the selected answer. – Aeolis

Answer 3

Maybe you have changed the password recently for you Git account. You could try the git push line with the -u option:

git push -u origin branch_name_that_you_want_to_push

After executing the above command, it will ask for a password. Provide your updated password.

Simoneaux

this works, which my environment need be https only – Suspension

Certainly a lot easier than most answers. (And changing passwords should be the most common reason to get an authentication error ;-) ) – Hunch

if you are experiencing this on a existing clone - then just do a git push -u – Judgemade

I deleted my credentials from Windows Credential Manager and this command triggered the login dialog. Thanks! – Lepley

This solution is no longer valid: Git will notify with "Support for password authentication was removed on August 13, 2021. Please use a personal access token instead." and recommend to follow this link: github.blog/… – Thomasina

Best answer. Very easy solution. – Stgermain

Answer 4

It happens if you change your login or password of git service account (Git). You need to change it in Windows Credentials Manager too. type "Credential Manager" in Windows Search menu open it.

Windows Credentials Manager->Windows Credential and under Generic Credentials edit your git password.

Lion

This saved me when working with GitLab (when pretty much nothing else helped). Thanks! – Evasion

I had never heard of this windows credentials manager.... Thanks ! – Pardoner

I gave wrong credentials when Git prompted me for user id and password while pushing new files to remote repository. When I ran push command again git did not prompt me for credentials but instead it was only throwing authentication failed error. I realised after reading this answer that git uses credentials stored in credential manager and that should be the reason git does not prompt for password everytime we push into remote respository. I deleted the git password in credential manager after which git again prompted me for user id and password. – Conoid

You can open the above window by (windows + R) -> "control /name Microsoft.CredentialManager" – Lion

Simplest and fastest fix IMO. – Wrestling

Answer 5

On Windows, this worked for me, and it also remembers my credentials:

1. Run Git Bash

2. Point to the repository directory

3. Run git config --global credential.helper wincred

Cromlech

Took me a while to find out what that does -- it uses the Credential Manager in the Windows Control Panel. To stop using it: git config –global credential.helper unset Source, and more details in this answer. – Lumbering

@IanW Do you mean git config --global --unset credential.helper? That's what worked for me in Git Bash. – Benedicto

Be careful with this command it will replace the real path to your credential helper with simply "wincred" which apparently not what you need. – Nitty

I ran this command to find out it's not what i wanted, the proper way to unset is git config --global --unset credential.helper. Ultimately, I restored my correct setting with git config credential.helper store. – Timothea

On a Mac, after answering the web capcha, this worked for me: git config --global credential.helper osxkeychain – Fancied

Answer 6

Basically my credential was expired, and I was facing the issue.

The following two commands helped me:

git config --global --unset credential.helper

git config credential.helper store

It will ask you for credentials next time when you try to push.

Follow the below guidelines for more details for secured and unsecured storage of the user name and passwords:

• git-credential-store

• git-credential-cache

Tierell

This works great on Mac after a password expiration. – Henceforth

I did that and it still does not prompt for the credentials. I also removed the user credentials from Windows password manager. I went through almost all answers here, but didn't help any suggestions? it only works when I put credentials in the address e.g. git push https://<user>:<pwd>@<bitbucketaddress> – Grapher

For me and Windows 10, it worked perfectly. – Caiman

This answer pointed me towards looking into my .gitconfig file, which is what I ended up needing to do. – Almanac

Answer 7

First, you can make sure to use the proper URL:

git remote set-url origin https://github.com/zkirkland/Random-Python-Tests.git

Then, if it was working before, and if it wasn't asking for your username, it must be because you had stored your credentials (login/password) in a $HOME/.netrc file, as explained here. You can double check those settings, and make sure that your proxy, if you have one, hasn't changed.

Check the output of git config --global credential.helper.
And make sure the credentials are your GitHub user account, and a PAT (Personal Access token).

You can update your credentials using the Git credential helper, as in here.

---

If that still doesn't work, you can switch to an SSH URL:

git remote set-url origin [email protected]:zkirkland/Random-Python-Tests.git

But that means you have published your SSH public key in your Account settings.

---

For Visual Studio Code specifically, see also "git push: Missing or invalid credentials. fatal: Authentication failed for 'https://github.com/username/repo.git'"

You can unselect the setting git.terminalAuthentication to avoid the error message.

Wallie

Switching from HTTPS to SSH solved the problem for me. – Ceaseless

I had enabled 2-factor authentication for my GH account and switching the remote url to SSH from HTTPS resolved the "authentication failed" issue for me. Makes sense. Thanks! – Resultant

This also solved the problem for me. After I switched to two-factor authentication, I set up a public key in my GitHub account. – Peptonize

Having incorrect URL was indeed my issue, I mistakenly changed https:// to git://, while I needed [email protected]:user.repo.git. Strange that git didn't report the issue somehow, just silent hanging – Mightily

@AlexeyLarionov Since git:// is a valid (albeit obsolete) protocol, it simply tried and use it, waiting for a remote server to listen on port 9418. – Wallie

Answer 8

On Windows, if you found an authentication error problem when you entered the correct password and username, it's a Git problem. To solve this problem, when you are installing the Git in your machine, uncheck the Enable Git Credential Manager option.

Hammonds

I don't find this type of solution. I have re installed the git – Hammonds

Fixed my trouble too (git was installed, just reinstalled it wich unchecking this : and it's ok !) – Hamza

I had to check "Use the native Windows Secure Channel library" too. It isn't checked by default. – Swiger

Reinstalling git works fine for me. Download the newest installer. Enable newest feature of git credential manager during installation. Before you push the repo. A window will pop-up and you will be able to login via browser. – Hardecanute

Answer 9

I was getting the same error. I tried all the solutions whichever mentioned in this page, but they didn't work. Finally, I found the solution.

These kinds of error comes if sometimes your system password has changed recently anytime. It will try to validate from the old password. So, follow these steps:

1. Go to Control Panel
2. Click on User Accounts
3. Under Credentials manager
4. Go to Manage Windows Credentials
5. Go to Generic Credentials
6. Expand the Git server tab
7. Click on Remove from vault

• Also, you can click Edit and change your password stored here directly.

Guillemette

This is an exact duplicate of what user Sherlock posted more than a year prior and deleted 3 minutes before this answer was posted. – Egyptian

I don't have a Credentials Manager under User Accounts. I am running Manjaro. – Sakovich

Answer 10

I think that for some reason GitHub is expecting the URL to NOT have subdomain www. When I use (for example)

git remote set-url origin https://www.github.com/name/repo.git

it gives the following messages:

remote: Anonymous access to name/repo.git denied
fatal: Authentication failed for https://www.github.com/name/repo.git

However, if I use

git remote set-url origin https://github.com/name/repo.git

it works perfectly fine. Doesn't make too much sense to me... but I guess remember not to put www in the remote URL for GitHub repositories.

Also notice the clone URLs provided on the GitHub repository webpage doesn't include the www.

Pictograph

Not putting "www" on "github.com" works. Since that matters, Github should fix their site so you can't clone using "www". – Remodel

Thank you : ) My url was missing the .git, and this comment got me to take a look at it and figure it out. – Vesuvianite

Answer 11

Before you try everything above, try to git push again, yes it works on me.

Bayles

It asks for username and password when you do 'git push' again atleast in my case, enter your credentials and you are good to go – Scrutineer

You saved my time! Thanks! This worked for me. – Minoan

Yes on Visual Studio code it asks for password when you try again. Thanks for the solution. – Willardwillcox

Too bad this answer is so low. Definitely the simplest step to take first. Thanks. – Sochi

Answer 12

The same error (Windows, Git Bash command line). Using https which should prompt for login credentials but instead errors:

$ git pull origin master
fatal: Authentication failed for 'https://github.com/frmbelz/my_git_project.git'

$ git config -l
...
credential.helper=manager
...

$ git config --global --unset credential.helper
$ git config --system --unset credential.helper

git pull now prompted for username/password prompts.

Forrester

I feel compelled to comment because I was starting to lose hope, none of these answers were working for me, but those last two commands ensured git asked me for my new credentials. Thank you. – West

Answer 13

I'm not really sure what I did to get this error, but doing:

git remote set-url origin https://...

didn't work for me. However:

git remote set-url origin [email protected]:user/repo

somehow worked.

Regretful

You switched from https to ssh – Cimbri

It works for me as well. This is not magic, it is because I have stored configuration for ssh access (with a public key configured), which are not picked up for https access (which is user/pass + MFA). – Conlen

Answer 14

I was adding to Bitbucket linked with Git and had to remove the stored keys, as this was causing the fatal error.

To resolve, I opened the command prompt and ran

 rundll32.exe keymgr.dll, KRShowKeyMgr

I removed the key that was responsible for signing in and next time I pushed the files to the repo, I was prompted for credentials and entered the correct ones, resulting in a successful push.

Takeo

Perfect! This is a quick and short solution, worked for me in an instant for bitbucket. If this issue repeats after editing the password, remove the logon. New creds for git are prompted when doing a git operation like pull or push. – Thumping

Answer 15

I've ran into

git fetch

fatal: Authentication failed for 'http://...."

after my Windows password had expired and was changed. Multiple fetches, reboot and even reinstall of Git with Windows Credential Manager didn't help.

Surprisingly the right answer is somewhere here in comments, but not in answers (and some of them are really weird!).

You need to go to Control Panel → Credential Manager → Windows Credentials and update you password for git:http://your_repository_address

Nitty

Answer 16

In my case, I recently changed my windows password and I have SSH key configured for git related actions (pull, push, fetch etc.,), after I encountered the "fatal: Authentication failed" error, I updated my password in the windows credential manager (Control Panel\User Accounts\Credential Manager)for all items starting with git:..., and tried again, worked this time!

Integumentary

Answer 17

I had the same problem. I set the URL in this way:

git remote set-url origin https://github.com/zkirkland/Random-Python-Tests.git

I also removed this entry from the configuration file: askpass = /bin/echo.

Then "git push" asked me for username and password and this time it worked.

Fraught

I didn't need to remove from config file this entry: askpass = /bin/echo. – Cardiology

Answer 18

If you have enabled the two-factor authentication on your GitHub account, then sign in to your GitHub account and go to

New personal access token

to generate a new access token, copy that token, and paste as a password for authentication in the terminal.

Slaw

Answer 19

Just from your .config file change:

url = http://www.github.com/###user###/Random-Python-Tests

To:

url = http://###user###@github.com/###user###/Random-Python-Tests

Tailgate

Answer 20

I started experiencing this issue on Visual Studio Code in Ubuntu 20.04 yesterday.

I did not make any changes to my GitHub credentials, neither did I change anything in the project, but I run any git command to communicate with my remote branch like:

git pull origin dev

I get the error below:

remote: Repository not found. fatal: Authentication failed for 'https://github.com/MyUsername/my-project.git/'

Here's what worked for me:

I tried recloning the project and then running the git pull command but it did not work.

git clone https://my-git-url

I tried setting my credentials again using the below commands but still no luck:

git config --global user.email "[email protected]"
git config --global user.name "John King"

I tried removing the remote repository and re-adding it using the below commands, but still no luck:

git remote remove origin
git remote add origin https://my-git-url

Finally, I decided to try using my default Ubuntu terminal and it worked fine. My big guess is that it's a bug from Visual Studio Code from the last update that was made some few hours before then (See the screenshot that shows that a Release was done on the same day that I was having the issue). I mean I set up Visual Studio Code using snap, so probably it might have been updated in the background a few hours before then.

Hopefully, they will get it fixed and git remote operations will be fine again.

Hinckley

Having the same issues, VScode on ubuntu 20.04. Did you find a solution to make the integrated terminal to work? (I'm using bash) – Anesthesiologist

Thanks, same issue here. Luckily I found your post right away – Cremator

Answer 21

If you are on Windows and trying to push to a Windows server which has domain users working as repository users (TFS), try getting into the TFS URL (i.e. http:\\tfs) with Internet Explorer. Enter your domain account credentials and let the page appear.

Caution: Only use Internet Explorer! Other browsers won’t change your system credentials.

Now go to Git Bash and change your remote user for the repository like below:

git config user.name "domainName\userName"

And done. Now you can push!

Deandeana

Answer 22

Got the above error message when I updated my computer password. Reset my git credentials using the following steps:

Go to Control Panel > User Accounts > Credential Manager > Windows Credentials. You will see Git credentials in the list (e.g. git:https://). Click on it, update the password, and execute git pull/push command from your Git bash and it won't throw any more error messages.

Ozenfant

You're a lifesaver, I was just about to give up and send an email to Support when I saw this answer, since the same thing was happening to me (no clue why windows credentials didn't update automatically like the last time I had to change my computer password, but oh well). – Multitude

Answer 23

For me, I forgot that I had changed the password on github.com, and my keychain for shell authentication never updated to that new password.

Deleting everything Git from my keychain and then rerunning the Git request helped solve the issue, prompting me again for the new password.

Armorial

Answer 24

If you are using SSH and cloned with HTTPS, this will not work.

Clone with SSH and then push and pulls should work as expected!

Chibchan

Answer 25

I tried the token verification method and got it to work ~3 times and wasted around 2 hours of time for that. For some reason it does not work very well for our company.

My solution was to change the authentication method from HTTPS to SSH. Here is a Github guide (https://help.github.com/en/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent).

After you have created the SSH key, remember to change the SSH address origin:

git remote add origin [email protected]:user/repo.git

Carissacarita

Answer 26

I was getting below error when trying to push to github remote

[email protected]: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Solution SSH Keys were missing on github account

1. Copy local public ssh keys from ~/.ssh directory

2. Paste to Github > Settings > SSH and GPG Keys > New SSH Key

3. Try ssh -T [email protected] This should output

   Hi xxxxx! You've successfully authenticated, but GitHub does not provide shell access.

Vituline

What does option -T do in ssh? And why is it not listed here ssh.com/academy/ssh/command#ssh-command-line-options? – Crocodile

The -T option will disable pseudo terminal allocation while connecting to a Git remote server over SSH. Git server will respond to SSH request having -T option. – Vituline

Answer 27

the quick GUI way of doing is:

1. Firstly generate an access token via create app access token.
2. then goto sourceTree's Settings(placed under the close button of the Source tree)
3. A prompt will appear named "Repository Settings".
4. There add/edit your repository path with https://USER_NAME:[email protected]/REPO_NAME/PROJECT_NAME.git

or for github account

https://username:[email protected]/username/repo.git

Here the only change to mention is adding the additional accessToken generated by the above shared create app access token link into existing path url.

Boman

In my case, I was using the password for DevOps login when Git request password after user has ben entered; I was wrong since I needed to enter password provided with the creation of Personal Access Token (PAT) - that password shows a warning that it must be copied, since won't be shown again -. In summary, provide Git credentials as user and pwd showed in that creation step. – Gliwice

Answer 28

The question was asked way before Two-Factor Authentication was introduced by GitHub, however, many people are encountering this error ever since GitHub introduced 2FA.

GitHub asks for authentication every time you try to push, if you want to avoid getting prompted repeatedly, you should use github-cli which is very lightweight and you can install with apt, yum, dnf and pacman.

after installing github-cli,

1. Type this command

gh auth login

2. Select the account type to authenticate
3. Select HTTPS or SSH (as desired)
4. Login with a web browser or authenticate with access tokens as per your ease.

Access tokens can be generated from GitHub > Settings > Developer-settings > Generate Access token, copy the token, and paste it into the terminal, It is a one-time code so ensure that you do not lose the code before authenticating it on the terminal

Witch

This worked for me and seems like the easiest solution in 2023. – Propylene

Answer 29

In Sourcetree Go to Tools -> Options -> Authentication

On Your Email Id click on Edit and click on Refresh OAuth Token.

Santo

Answer 30

Just to chime in here, what fixed the issue for me was I simply canceled out of the initial prompt, the SSH one opened up with my Bitbucket account, I entered the password there and everything worked as expected.

Neurilemma

Answer 31

I was facing the same issue on Windows. Most of the time, I normally face the issue due to using multiple Git accounts. If you are on Windows, please do open the terminal as an administrator and try running the commands again. Make sure that you have the administrator access rights.

Triennial

Answer 32

In Android Studio Canary build 3.1+, if you are using the Android Studio Git tool, then you can use following:

• Click on Android Studio
• Click on Preferences...
• Go in Version Control → GitHub
• Here change Auth type to Password
• This step will require you to enter login and password. Enter your GitHub user name as the login and GitHub password as the password.
• Click on the Test button.

If the connection is successful, then you are done and you can use the Android Studio GitHub GUI client.

Recount

Answer 33

THIS IS MY SOLUTION i think it works for Azure, Github or Git. If your authentication is failing could be due to 4 probable reasons -- you enabled 2FA, you changed your password, you changed your username or the repo password is dynamic) --

Whatever it happened you should just FOLLOW FOUR STEPS:

1. Go wherever you repo is located and click on "CLONE" button.
2. There should be a HTTPS way and below click on "Generate git credentials" button. This has to give you a new password. (Azure Repos photo)

3. Go to your repo in cmd and enter:

   git push -u origin your-Branch-Name

4. (IF NEEDED) If origin url route is not defined just enter the command below and do step 3 again:

   git remote add origin https://my-git-url

5. After git push command it will ask your credentials. Use the credentials that you have already generated in your repo.

Floorman

Answer 34

If you have a GitLab domain cloud server and you are searching for the exact format for your user name along with your company's cloud server incorporating the access token, the format would look like this:

git remote set-url origin https://<USERNAME>:<ACCESS-TOKEN>@gitlab.xyz.cloud/<PROJECT>/<REPO>.git

It helped me whenever my authentication failed because of access token expiry.

Don't forget to generate the access token from GitLab account.

Fomentation

Answer 35

In case this is tangentially helpful, since this question is now a top hit for http authentication problems with git: Windows Credential Manager had stored my password correctly, and since I was using Git LFS I configured an http URL instead of the usual ssh://.

My problem was that my corporate password policy forced an account password change but I never updated my stored credentials (since I always use an ssh key).

Simply updating the password directly in the Wincred GUI worked: just look for a git:https://<your-url> entry.

Woolley

Answer 36

I also ran into the error (that's why I am landed here), but none of the suggestions worked for me. This was my very first time I tried to deploy a local Git repository to Azure.

When I got this error, I reset my credentials (by clicking the link in Azure) after a few tries. The problem is that at this point it tells me my user name is already taken, so I also changed my user name to another one.

In the end, I manually deleted the .git folder on my local drive, and redeployed it without problem.

Alsace

Answer 37

Problem Statement: "git fatal authentication failed". I am using Bitbucket.

Solution:

I simply deleted the user from using the access management of Bitbucket and then added the same user. The .gitconfig file is simple:

[user]
    name = BlaBla
    email = [email protected]

[push]
    default = simple

Flasher

Answer 38

With correct credentials if the problem prevails:

If you’re using Android Studio 2.1 beta then it’s a bug. Upgrade to beta 2 (3 MB update file). This worked for me.

Pyromania

Answer 39

Make sure you have write permission to push.

read ***write*** admin 

Migration

In what context? Where does it go? Is all or part of it literal or not? The configuration file entries in the question has the form setting = value (= is literal). – Egyptian

Answer 40

This happened to us after forcing "Two Factor Authentication" before login from Gitlab. We had to paste the text inside id_rsa.pub to Gitlab, and then reintroduce the repository in VS code using the terminal.

Radiography

Answer 41

This the way, I resolved my access denied problem in GIT GUI and git bash.

This SSH key is copy-pasted in the GitHub access token.

For me everything was fine, I also tried the Windows Credentials Manager but then also the problem was not resolved. Then suddenly, I got pop up from the firewall, which was the main culprit behind all. After I clicked on allow manually then I could fetch or push to GitHub.

Uthrop

Answer 42

I had just enabled two factor authentication for my Github account, so I disabled two factor authentication and I was able to login with my UID and PWD

Jolt

Answer 43

Given Solution: Using a Personal Access Token is one way of bypassing this problem. I don't have two-factor authentication enabled but whenever, I would login to a new PC I get email verification code to verify PC.

Solution: You can login to GitHub on a browser and verify your identity, that will let GitHub know to trust that PC. Afterwards, login with bash and this time your login should work as usual because now you are whitelisted.

---

Note: If you have any existing GitHub account and want to switch, then, delete it in Credentials Manager > Windows Credentials (Generic Credentials Section). Doing so will allow you to login when you make another git operation.

Geriatrics

Answer 44

Enabling credentials helper solved the problem for me.

Siffre

Answer 45

I had the same problem. After restarting my System it worked.

Neutrino

Answer 46

Execute $ git credential fill protocol=https host=example.com It will open dialog box 'Git Credential Manager', define your credentials in this box and use them when asked during your next push attempt. See List git credentials from credential helper

Circumcision

Answer 47

In my case the source of problem was git preferring current windows user over stored credentials. You can disallow this by running in command line:

git config --global credential.https://YOUR.SERVER.allowwindowsauth false

Lack of spaces between url and setting is intended

Loux

Answer 48

Make sure that your SSH key is added to your current SSH session.

1. Copy the output of cat ~/.ssh/id_rsa.pub to your GitHub settings under SSH and GPG keys.

2. Update your current SSH session with ssh-add ~/.ssh/id_rsa.pub.

I am using Windows PowerShell with OpenSSH installed.

Fronde

Are you sure that you added the public key to the agent? – Sisterinlaw

Answer 49

My solutions is:

1. Access to C:\Users\USERNAME\AppData\Local\Atlassian\SourceTree
2. Find the file passwd
3. Right click on that file and open with Notepad
4. You will see a list of username and password like:

[email protected] AQAAANCMnd8BFdERjHoAwE/Cl+sBAAAAMUOX3Q56PEuXEBSDFAFAASEH...

5. Find the username and password you entered incorrectly, and delete it
6. Save the file, and close it
7. SourceTree will ask you again for your username and password on the next push or fetch

Palmary

Answer 50

For Windows, if username and password does not work for you with https please go through this doc authenticate with https

probably you have to generate a personal access token and use it instead of the password

In newer version of Git recommends using personal access token instead of a password but older versions do not show anything so I was stuck at this point.

Brokenhearted