![]() ![]() ![]() Changed SSH Client to OpenSSH, instead of the default PuTTY/PlinkĪfter these two changes, fetching, cloning and pushing to my remotes all work fine. Fork is getting better and better day after day and we are happy to share our results with you.I made two changes in Tools > Options which fixed this: Select which scopes you wish to grant this token. The steps to do this are as follows: Go to your Personal Access Tokens settings in GitHub. fatal: Could not read from remote repository. To work with GitHub's two-factor authentication in SourceTree you can simply use your access token instead of your password. git -c diff.mnemonicprefixfalse -c core.quotepathfalse fetch origin Permission denied (publickey,password). It turned out my issue was to do with the SSH Client Configuration (the ‘access denied’ and “Too many authentication failures for git” messages were the big clues). However, when I try to git pull in SourceTree, I get this. ![]() This was running Source Tree 1.6.something and 1.7.0, with the remote hosted in GitLab Community Edition version 8.1.4. I try to commit a file to a gitlab repo, but I receive git -c diff.mnemonicprefixfalse -c core.quotepathfalse -no-optional-locks push -v -tags origin main:main remote. Please make sure you have the correct access rights "Too many authentication failures for git"įatal: Could not read from remote repository. Initially when I tried to Fetch from a Gitlab remote in SourceTree, I got error messages like this: git -c diff.mnemonicprefix=false -c core.quotepath=false fetch originįATAL ERROR: Server sent disconnect message ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |