I'm working with several repositories, but lately I was just working in our internal one and all was great.
Today I had to commit and push code into other one, but I'm having some troubles.
$ git push appharbor master
error: The requested URL returned error: 403 while accessing https://[email protected]/mitivo.git/info/refs?service=git-receive-pack
fatal: HTTP request failed
There is nothing I can do, that would bring the password entry again.
How can I reset the credentials on my system so Git will ask me for the password of that repository?
I have tried:
git config --global --unset core.askpass
in order to unset the password
git config credential.helper 'cache --timeout=1'
in order to avoid credentials cache...
Nothing seems to work; does anyone have a better idea?
44 Answers 44
If this problem comes on a Windows machine, do the following.
Go to Credential Manager
- in Czech, it is called: Správce pověření
- in Dutch, it is called: Referentiebeheer
- in French, it is called: Gestionnaire d'identification
- in German, it is called: Anmeldeinformationsverwaltung
- in Italian, it is called: Gestione credenziali
- in Norwegian, it is called: Legitimasjonsbehandling
- in Polish, it is called: Menedżer poświadczeń
- in Portuguese, it is called: Gerenciador de Credenciais
- in Russian, it is called: Диспетчер учётных данных
- in Spanish, it is called: Administrador de credenciales
Go to Windows Credentials
Delete the entries under Generic Credentials
Go to Windows Credentials and Delete the entries under Generic Credentials
Try connecting again. This time, it should prompt you for the correct username and password.
credential.helper=manager. To test this type git config --list. If it's set to store then credentials are not stored in the credentials store but are stored un-encrypted.git:https://github.com and I was prompted to enter my username/pass the next time I cloned a repo using PyCharm. I had more than one github account and the wrong one was cached.Systemsteuerung\Alle Systemsteuerungselemente\Anmeldeinformationsverwaltung.Credential Manager. That worked for me tooThe Git credential cache runs a daemon process which caches your credentials in memory and hands them out on demand. So killing your git-credential-cache--daemon process throws all these away and results in re-prompting you for your password if you continue to use this as the cache.helper option.
You could also disable use of the Git credential cache using git config --global --unset credential.helper. Then reset this, and you would continue to have the cached credentials available for other repositories (if any). You may also need to do git config --system --unset credential.helper if this has been set in the system configuration file (for example, Git for Windows 2).
On Windows you might be better off using the manager helper (git config --global credential.helper manager). This stores your credentials in the Windows credential store which has a Control Panel interface where you can delete or edit your stored credentials. With this store, your details are secured by your Windows login and can persist over multiple sessions. The manager helper included in Git for Windows 2.x has replaced the earlier wincred helper that was added in Git for Windows 1.8.1.1. A similar helper called winstore is also available online and was used with GitExtensions as it offers a more GUI driven interface. The manager helper offers the same GUI interface as winstore.
Extract from the Windows 10 support page detailing the Windows credential manager:
To open Credential Manager, type "credential manager" in the search box on the taskbar and select Credential Manager Control panel.
And then select Windows Credentials to edit (=remove or modify) the stored git credentials for a given URL.
Control Panel\User Accounts\Credential Manager under Windows 7Retype:
$ git config credential.helper store
And then you will be prompted to enter your credentials again.
WARNING
Using this helper will store your passwords unencrypted on disk
.git/config.git config --unset credential.helperI faced the same issue as the OP. It was taking my old Git credentials stored somewhere on the system and I wanted to use Git with my new credentials, so I ran the command
$ git config --system --list
It showed
credential.helper=manager
Whenever I performed git push it was taking my old username which I set long back, and I wanted to use new a GitHub account to push changes. I later found that my old GitHub account credentials was stored under
Control Panel → User Accounts → Credential Manager → Manage Windows Credentials.
I just removed these credentials and when I performed git push it asked me for my GitHub credentials, and it worked like a charm.
git config --global --list should now return credential.helper=manager-core and not credential.helper=managerTry using the below command.
git credential-manager
Here you can get various options to manage your credentials (check the below screen).
Or you can even directly try this command:
git credential-manager uninstall
This will start prompting for passwords again on each server interaction request.
git: 'credential-manager' is not a git command. See 'git --help'.removal failed. U_U Press any key to continue... fatal: InvalidOperationException encountered. Cannot read keys when either application does not have a console or when console input has been redirected from a file. Try Console.Read. (with the nice U_U emoji out of nowhere :))I found something that worked for me. When I wrote my comment to the OP I had failed to check the system config file:
git config --system -l
shows a
credential.helper=!github --credentials
line. I unset it with
git config --system --unset credential.helper
and now the credentials are forgotten.
git config --global --unset credential.helper and maybe just git config --unset credential.helper in your repository if you had somehow set it explicitly there.This error appears when you are using multiple Git accounts on the same machine.
If you are using macOS then you can remove the saved credentials of github.com.
Please follow below steps to remove the github.com credentials.
- Open Keychain Access
- Find github
- Select the github.com and Right click on it
- Delete "github.com"
- Try again to Push or Pull to git and it will ask for the credentials.
- Enter valid credentials for repository account.
Done
git config --list
will show credential.helper = manager (this is on a windows machine)
To disable this cached username/password for your current local git folder, simply enter
git config credential.helper ""
This way, git will prompt for password every time, ignoring what's saved inside "manager".
git: 'credential-' is not a git command. See 'git --help'., but for security I am upvoting this answer because it is the only one that made me be prompted for a new password. I am wondering, however, if this is not just masking the problem (is the password really removed?)rm -rf ~/.git-credentials did. Note that it can vary (git help credential-store)git config --unset credential.helper clears the entry. This answer just sets it to empty string and produces the error that @ribamar described in comments.You have to update it in your Credential Manager.
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.
In my case, Git is using Windows to store credentials.
All you have to do is remove the stored credentials stored in your Windows account:
In Windows 2003 Server with "wincred"*, none of the other answers helped me. I had to use cmdkey.
cmdkey /listlists all stored credentials.cmdkey /delete:Targetdeletes the credential with "Target" name.
cmdkey /list; cmdkey /delete:Target
(* By "wincred" I mean git config --global credential.helper wincred)
cmdkey is the command-line counterpart to the Windows Credentials described in the chosen answer.cmdkey help for reference.If you want git to forget old saved credentials and re-enter username and password, you can do that using below command:
git credential-cache exit
After running above command, if you try to push anything it will provide option to enter username and password.
git help -a and you will see information about credential-cache in Low level commands / Internal helpers.git help -a ?Using latest version of git for Windows on Windows 10 Professional and I had a similar issue whereby I have two different GitHub accounts and also a Bitbucket account so things got a bit confusing for VS2017, git extensions and git bash.
I first checked how git was handling my credentials with this command (run git bash with elevated commands or you get errors):
git config --list
I found the entry Credential Manager so I clicked on the START button> typed Credential Manager to and left-clicked on the credential manager yellow safe icon which launched the app. I then clicked on the Windows Credentials tabs and found the entry for my current git account which happened to be Bit-bucket so I deleted this account.
But this didn't do the trick so the next step was to unset the credentials and I did this from the repository directory on my laptop that contains the GitHub project I am trying to push to the remote. I typed the following command:
git config --system --unset credential.helper
Then I did a git push and I was prompted for a GitHub username which I entered (the correct one I needed) and then the associated password and everything got pushed correctly.
I am not sure how much of an issue this is going forward most people probably work off the one repository but I have to work across several and using different providers so may encounter this issue again.
In case Git Credential Manager for Windows is used (which current versions usually do):
git credential-manager clear
This was added mid-2016. To check if credential manager is used:
git config --global credential.helper
→ manager
manager-core.Got same error when doing a 'git pull' and this is how I fixed it.
- Change repo to HTTPS
- Run command
git config --system --unset credential.helper - Run command
git config --system --add credential.helper manager - Test command
git pull - Enter credentials in the login window that pops up.
- Git pull completed successfully.
git config --system --unset credential.helper outputs C:/Program Files/Git/etc/gitconfig: Permission denied.- Go to
C:\Users\<current-user> - check for
.git-credentialsfile - Delete content or modify as per your requirement
- Restart your terminal
If your credentials are stored in the credential helper (generally the case), the portable way to remove a password persisted for a specific host is to call git credential reject:
in one line:
$ echo "url=https://appharbor.com" | git credential rejector interactively:
$ git credential reject protocol=https host=gitlab.com [email protected] ↵- ↵ is the Enter symbol, just hit Enter key twice at the end of input, don't copy/paste it
- The username doesn't seem recognized by wincred, so avoid to filter by username on Windows
After that, to enter your new password, type git fetch.
Comments
Need to login with respective github username and password
To Clear the username and password in windows
Control Panel\User Accounts\Credential Manager
Edit the windows Credential
Remove the existing user and now go to command prompt write the push command it shows a github pop-up to enter the username/email and password .
Now we able to push the code after switching the user.
Comments
In my case, I couldn't find the credentials saved in the Windows Credential Manager (Windows 7).
I was able to reset my credentials by executing
git config --global credential.helper wincred
It was honestly a hail Mary to see if it would wipe out my credentials and it actually worked.
Remove this line from your .gitconfig file located in the Windows' currently logged-in user folder:
[credential]
helper = !\"C:/Program Files (x86)/GitExtensions/GitCredentialWinStore/git-credential-winstore.exe\"
This worked for me and now when I push to remote it asks for my password again.
Comments
No answer given worked for me. But here is what worked for me in the end:
rm -rf ~/.git-credentials
That will remove any credentials! When you use a new git command, you will be asked for a password!
On Windows, at least, git remote show [remote-name] will work, e.g.
git remote show origin
This approach worked for me and should be agnostic of OS. It's a little heavy-handed, but was quick and allowed me to reenter credentials.
Simply find the remote alias for which you wish to reenter credentials.
$ git remote -v
origin https://bitbucket.org/org/~username/your-project.git (fetch)
origin https://bitbucket.org/org/~username/your-project.git (push)
Copy the project path (https://bitbucket.org/org/~username/your-project.git)
Then remove the remote
$ git remote remove origin
Then add it back
$ git remote add origin https://bitbucket.org/org/~username/your-project.git
https://name:[email protected]/repo-url. Then you should remove the origin and add again.git config -e and chaning url to origin. meddling with removing origin is overkill.For macOS users :
This error appears when you are using multiple Git accounts on the same machine.
Please follow below steps to remove the github.com credentials.
- Go to Finder
- Go to Applications
- Go to Utilities Folder
- Open Keychain Access
- Select the github.com and Right click on it
Delete "github.com"
Try again to Push or Pull to git and it will ask for the credentials. Enter valid credentials for repository account. Done, now upvote the answer.
Comments
You can remove the line credential.helper=!github --credentials from the following file C:\Program Files\Git\mingw64\etc\gitconfig in order to remove the credentials for git
Comments
Building from @patthoyts's high-voted answer:
His answer uses but doesn't explain local vs. global vs. system configs. The official git documentation for them is here and worth reading.
For example, I'm on Linux, and don't use a system config, so I never use a --system flag, but do commonly need to differentiate between --local and --global configs.
My use case is I've got two Github crendentials; one for work, and one for play.
Here's how I would handle the problem:
$ cd work
# do and commit work
$ git push origin develop
# Possibly prompted for credentials if I haven't configured my remotes to automate that.
# We're assuming that now I've stored my "work" credentials with git's credential helper.
$ cd ~/play
# do and commit play
$ git push origin develop
remote: Permission to whilei/specs.git denied to whilei.
fatal: unable to access 'https://github.com/workname/specs.git/': The requested URL returned error: 403
# So here's where it goes down:
$ git config --list | grep cred
credential.helper=store # One of these is for _local_
credential.helper=store # And one is for _global_
$ git config --global --unset credential.helper
$ git config --list | grep cred
credential.helper=store # My _local_ config still specifies 'store'
$ git config --unset credential.helper
$ git push origin develop
Username for 'https://github.com': whilei
Password for 'https://[email protected]':
Counting objects: 3, done.
Delta compression using up to 12 threads.
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 1.10 KiB | 1.10 MiB/s, done.
Total 3 (delta 1), reused 0 (delta 0)
remote: Resolving deltas: 100% (1/1), completed with 1 local object.
To https://github.com/whilei/specs.git
b2ca528..f64f065 master -> master
# Now let's turn credential-helping back on:
$ git config --global credential.helper "store"
$ git config credential.helper "store"
$ git config --list | grep cred
credential.helper=store # Put it back the way it was.
credential.helper=store
It's also worth noting that there are ways to avoid this problem altogether, for example, you can use ~/.ssh/config's with associated SSH keys for Github (one for work, one for play) and correspondingly custom-named remote hosts to solve authentication contextualizing too.
Comments
What finally fixed this for me was to use GitHub desktop, go to repository settings, and remove user:pass@ from the repository url. Then, I attempted a push from the command line and was prompted for login credentials. After I put those in everything went back to normal. Both Visual Studio and command line are working, and of course, GitHub desktop.
GitHub Desktop->Repository->Repository Settings->Remote tab
Change Primary Remote Repository (origin) from:
https://pork@[email protected]/MyProject/MyProject.git
To:
https://github.com/MyProject/MyProject.git
Click "Save"
Credentials will be cleared.
git config -e and changing or deleting credentials from origin urlUpdate Actually useHttpPath is a git configuration, which should work for all GCMs. Corrected.
Summary of The Original Question
- working with git on Windows
- working on multiple repositories on GitHub
- wrong credentials used for another GitHub repository
Although the title says "Remove credentials", the description leads me to the assumption that you may have multiple accounts on GitHub, e.g. for job-related vs. private projects. (At least that issue made me find this topic.) If so read on, otherwise, ignore the answer, but it may come in handy at some time.
Reason
Git Credential Managers (short GCM) like Microsoft's GCM for Windows store credentials per host by default. This can be verified by checking the Windows Credential Manager (see other answers on how to access it on English, French, and German Windows versions). So working with multiple accounts on the same host (here github.com) is not possible by default.
In October 2020 GCM for Windows got deprecated and superseded by GCM Core. The information here still applies to the new GCM and it should even use the credentials stored by GCM for Windows.
Solution
Configure git to include the full path to the repository as additional information for each credential entry. Also documented on GCM for Windows.
I personally prefer to include the HTTP(S) [repository] path to be able to use a separate account for each and every repository.
For all possible hosts:
git config --global credential.useHttpPath true
For github.com only:
git config --global credential.github.com.useHttpPath true
Have a look at the GCM and git docs and maybe you want to specify something different.
Comments
Kindly run following command -
git config --global credential.helper cache
and then run any git command like git pull it will ask for username and password. Enter the details and if you want to store your git credentials, run following command -
git config --global credential.helper store
Comments
For Windows 10, go to below path,
Control Panel\User Accounts\Credential Manager
There will be 2 tabs at this location,
- Web credentials and 2. Windows credentials.
Click on Windows credentials tab and here you can see your stored github credentials, under "Generic credentials" heading.
You can remove those from here and try and re-clone - it will ask for username/password now as we have just removed the stored credential from the Windows 10 systems
~/.netrcfile?netrc, which would store multiple credential in an encrypted file. It is better than entering your password each time for each session, since the cache only "caches" the password for a certain time. See a full example here.rm ~/.git-credentialsafterwards. Being prompted for a password doesn't mean that they are not stored.