desktop: Github Desktop version 1.0.12 Authentication Failed during fetch with remote

Description

After upgrading to the new Github desktop from the classic Github Desktop on Windows 10 I get an Authentication Failed when using an https repository URL.

Version

GitHub Desktop version: 1.0.12

OS version: Windows 10 Pro Version 1709 OS Build 16299.192 (running as a VM under Mac OS X Sierra 10.12.6 using VitualBox)

Steps to Reproduce

Install latest GitHub Desktop
Add local repository (From GitHub Classic clone)
Try and fetch repository just added and receive the following error message:
Copy github_rsa.pub to id_rsa.pub and github_rsa to id_rsa in %USERPROFILE%.ssh to no avail. Still can’t clone, fetch, push or pull from the new Github Desktop. Still get same error message as above.

Expected behavior: I expect that I can clone a remote repository using the new GitHub Desktop application. I expect that I can fetch an already cloned repository.

Actual behavior: Both workflows give me an Authentication Failed error message

Reproduces how often: This has never worked for me. I can reproduce this behavior 100% of the time. I have two computers this is happening to me on. Both Windows 10 Pro VMs running under VirtualBox on Mac OS 10. Only difference is one is running High Sierra.

Logs - From fresh install on new computer today that has same issue.

2018-01-18T15:31:44.674Z - info: [main] Received possible protocol arguments: 2 2018-01-18T15:31:55.162Z - info: [ui] [AppStore] loading 0 repositories from store 2018-01-18T15:31:55.181Z - info: [ui] [Welcome] no sign in step found. ignoring… 2018-01-18T15:31:55.184Z - info: [ui] [Welcome] no sign in step found. ignoring… 2018-01-18T15:31:55.186Z - info: [ui] [Welcome] no sign in step found. ignoring… 2018-01-18T15:31:55.189Z - info: [ui] [Welcome] no sign in step found. ignoring… 2018-01-18T15:31:56.340Z - info: [ui] launching: 1.0.12 (Windows 10.0.16299) 2018-01-18T15:32:00.078Z - info: [ui] [Welcome] no sign in step found. ignoring… 2018-01-18T15:32:00.642Z - info: [ui] [Welcome] no sign in step found. ignoring… 2018-01-18T15:32:08.344Z - info: [ui] [Welcome] advancing to step: SignInToDotCom 2018-01-18T15:32:08.352Z - info: [ui] [Welcome] current sign in state not found. ignoring… 2018-01-18T15:32:16.450Z - info: [ui] Executing installGlobalLFSFilter: git lfs install --skip-repo (took 21.107s) 2018-01-18T15:32:41.882Z - info: [ui] [Welcome] kind Authentication is the same as Authentication. ignoring… 2018-01-18T15:32:51.656Z - info: [ui] [AppStore] adding account jborn (Jeffrey Born) to store 2018-01-18T15:32:51.665Z - info: [ui] [Welcome] advancing to step: ConfigureGit 2018-01-18T15:32:51.841Z - info: [ui] [Welcome] no sign in step found. ignoring… 2018-01-18T15:33:00.596Z - info: [ui] [Welcome] advancing to step: UsageOptOut 2018-01-18T15:33:01.928Z - info: [ui] Executing setGlobalConfigValue: git config --global --replace-all user.name jborn (took 1.282s) 2018-01-18T15:33:03.102Z - info: [ui] Executing setGlobalConfigValue: git config --global --replace-all user.email jeff.born@gmail.com (took 1.183s) 2018-01-18T15:33:05.939Z - info: [ui] Opt out reported. 2018-01-18T15:33:53.473Z - info: [ui] [AppStore] adding repository at E:\Source Code\GitHub\MidasDB to store 2018-01-18T15:33:56.305Z - info: [ui] Executing getStatus: git status --untracked-files=all --branch --porcelain=2 -z (took 2.790s) 2018-01-18T15:33:56.968Z - info: [ui] Executing getStatus: git status --untracked-files=all --branch --porcelain=2 -z (took 2.443s) 2018-01-18T15:33:57.468Z - info: [ui] Executing getCommits: git log cd3224f8430aff342311ade799b83060b1d3534b --date=raw --max-count=1 --pretty=%H%x1F%s%x1F%b%x1F%an <%ae> %ad%x1F%P -z --no-color – (took 1.142s) 2018-01-18T15:33:58.137Z - info: [ui] Executing getBranches: git for-each-ref --format=%(refname)%00%(refname:short)%00%(upstream:short)%00%(objectname)%00%(author)%00%(parent)%00%(symref)%00%(subject)%00%(body)%00%1F refs/heads refs/remotes (took 4.621s) 2018-01-18T15:33:58.584Z - info: [ui] Executing getBranches: git for-each-ref --format=%(refname)%00%(refname:short)%00%(upstream:short)%00%(objectname)%00%(author)%00%(parent)%00%(symref)%00%(subject)%00%(body)%00%1F refs/heads refs/remotes (took 4.054s) 2018-01-18T15:33:59.155Z - info: [ui] Executing getRecentBranches: git log -g --no-abbrev-commit --pretty=oneline HEAD -n 2500 – (took 5.626s) 2018-01-18T15:33:59.319Z - info: [ui] Executing getRecentBranches: git log -g --no-abbrev-commit --pretty=oneline HEAD -n 2500 – (took 4.787s) 2018-01-18T15:34:00.179Z - info: [ui] Executing getWorkingDirectoryDiff: git diff HEAD --no-ext-diff --patch-with-raw -z --no-color – Midas/MidasFactory/Schema Objects/Schemas/MIDAS/Programmability/Stored Procedures/Building_MergeThenDelete_From_AnchorAndDuplicateBuildingKeyList.proc.sql (took 2.616s) 2018-01-18T15:34:00.433Z - info: [ui] Executing getRemotes: git remote -v (took 1.050s) 2018-01-18T15:34:00.433Z - info: [ui] Executing getWorkingDirectoryDiff: git diff HEAD --no-ext-diff --patch-with-raw -z --no-color – Midas/MidasFactory/Schema Objects/Schemas/MIDAS/Programmability/Stored Procedures/Building_MergeThenDelete_From_AnchorAndDuplicateBuildingKeyList.proc.sql (took 2.975s) 2018-01-18T15:34:00.481Z - info: [ui] Executing getRemotes: git remote -v (took 1.326s) 2018-01-18T15:34:00.732Z - info: [ui] Executing getCommits: git log origin/DuplicateBuildingHandling…DuplicateBuildingHandling --date=raw --max-count=100 --pretty=%H%x1F%s%x1F%b%x1F%an <%ae> %ad%x1F%P -z --no-color – (took 1.388s) 2018-01-18T15:34:00.805Z - info: [ui] Executing getCommits: git log origin/DuplicateBuildingHandling…DuplicateBuildingHandling --date=raw --max-count=100 --pretty=%H%x1F%s%x1F%b%x1F%an <%ae> %ad%x1F%P -z --no-color – (took 1.662s) 2018-01-18T15:34:01.205Z - info: [ui] Executing isUsingLFS: git lfs track (took 7.701s) 2018-01-18T15:34:03.354Z - info: [ui] Executing getBranches: git for-each-ref --format=%(refname)%00%(refname:short)%00%(upstream:short)%00%(objectname)%00%(author)%00%(parent)%00%(symref)%00%(subject)%00%(body)%00%1F refs/heads refs/remotes (took 2.144s) 2018-01-18T15:34:03.629Z - info: [ui] Executing getStatus: git status --untracked-files=all --branch --porcelain=2 -z (took 2.425s) 2018-01-18T15:34:04.568Z - info: [ui] Executing getRecentBranches: git log -g --no-abbrev-commit --pretty=oneline HEAD -n 2500 – (took 3.344s) 2018-01-18T15:34:05.252Z - info: [ui] Executing getWorkingDirectoryDiff: git diff HEAD --no-ext-diff --patch-with-raw -z --no-color – Midas/MidasFactory/Schema Objects/Schemas/MIDAS/Programmability/Stored Procedures/Building_MergeThenDelete_From_AnchorAndDuplicateBuildingKeyList.proc.sql (took 1.624s) 2018-01-18T15:34:06.994Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 6.222s) 2018-01-18T15:34:06.995Z - error: [ui] git -c credential.helper= fetch --progress --prune origin exited with an unexpected code: 128. remote: Invalid username or password. fatal: Authentication failed for ‘https://github.com/peachtreegeographics/MidasDB.git/’

(The error was parsed as 3: Authentication failed. You may not have permission to access the repository or the repository may have been archived. Open options and verify that you’re signed in with an account that has permission to access this repository.) 2018-01-18T15:34:08.592Z - info: [ui] Executing getStatus: git status --untracked-files=all --branch --porcelain=2 -z (took 1.597s) 2018-01-18T15:34:09.016Z - info: [ui] Executing getBranches: git for-each-ref --format=%(refname)%00%(refname:short)%00%(upstream:short)%00%(objectname)%00%(author)%00%(parent)%00%(symref)%00%(subject)%00%(body)%00%1F refs/heads refs/remotes (took 2.015s) 2018-01-18T15:34:09.370Z - info: [ui] Executing getRecentBranches: git log -g --no-abbrev-commit --pretty=oneline HEAD -n 2500 – (took 2.354s) 2018-01-18T15:34:11.739Z - info: [ui] Executing getAheadBehind: git rev-list --left-right --count Dev…origin/Dev – (took 1.658s) 2018-01-18T15:34:16.835Z - info: [ui] [AppStore.withAuthenticatingUser] account found for repository: MidasDB - jborn (has token) 2018-01-18T15:34:24.142Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 7.246s) 2018-01-18T15:34:24.143Z - error: [ui] git -c credential.helper= fetch --progress --prune origin exited with an unexpected code: 128. remote: Invalid username or password. fatal: Authentication failed for ‘https://github.com/peachtreegeographics/MidasDB.git/’

(The error was parsed as 3: Authentication failed. You may not have permission to access the repository or the repository may have been archived. Open options and verify that you’re signed in with an account that has permission to access this repository.) 2018-01-18T15:34:32.458Z - info: [ui] Executing getStatus: git status --untracked-files=all --branch --porcelain=2 -z (took 8.337s) 2018-01-18T15:34:33.177Z - info: [ui] Executing getBranches: git for-each-ref --format=%(refname)%00%(refname:short)%00%(upstream:short)%00%(objectname)%00%(author)%00%(parent)%00%(symref)%00%(subject)%00%(body)%00%1F refs/heads refs/remotes (took 8.846s) 2018-01-18T15:34:33.430Z - info: [ui] Executing getRecentBranches: git log -g --no-abbrev-commit --pretty=oneline HEAD -n 2500 – (took 9.095s) 2018-01-18T15:34:36.306Z - info: [ui] Executing getAheadBehind: git rev-list --left-right --count Dev…origin/Dev – (took 2.241s) 2018-01-18T15:34:44.593Z - info: [ui] [AppStore.getAccountForRemoteURL] account found for remote: https://github.com/peachtreegeographics/MelllisaDataWindowsService.git - jborn (has token) 2018-01-18T15:34:47.107Z - info: [ui] Executing clone: git -c credential.helper= clone --recursive --progress – https://github.com/peachtreegeographics/MelllisaDataWindowsService.git C:\Users\Jeffr\Documents\GitHub\MelllisaDataWindowsService (took 2.450s) 2018-01-18T15:34:47.107Z - error: [ui] git -c credential.helper= clone --recursive --progress -- https://github.com/peachtreegeographics/MelllisaDataWindowsService.git C:\Users\Jeffr\Documents\GitHub\MelllisaDataWindowsService exited with an unexpected code: 128. Cloning into ‘C:\Users\Jeffr\Documents\GitHub\MelllisaDataWindowsService’… remote: Invalid username or password. fatal: Authentication failed for ‘https://github.com/peachtreegeographics/MelllisaDataWindowsService.git/’

remote: Invalid username or password. fatal: Authentication failed for ‘https://github.com/peachtreegeographics/MidasDB.git/’

Additional Information

I can use the git bash shell to do the tasks that are failing in the Github Desktop application. I can see a complete repositories to clone from the https://github.com/peachtreegeographics. I don’t believe I’d be able to do that without the right credentials. When not logged in with my credentials I can see four public repositories.

About this issue

Original URL
State: closed
Created 6 years ago
Reactions: 9
Comments: 69 (14 by maintainers)

Most upvoted comments

Goto File > Options > Sign Out and Sign In again. It works for me.

+51

miftahafina on Apr 17, 2018

I have logged out and logged back in multiple times. It still doesn’t work.

+15

jborn on Jul 20, 2018

I’m confused by why this would be opened as a new issue. I’ve had this issue since January 18 when I first reported it and have tried all the solutions mentioned in this thread (with no success) and provided logs and setup information. I’m happy to provide more details. Just tell me what you need and where to get it.

jborn on Sep 13, 2018

I had this same issue with version 1.2.3 I switched to using the command line, and git kept asking for my ssh passphrase, so I ran ssh-add to resolve that and it resolved the issue with GitHub Desktop. No idea if this will work for anyone else.

tomlovett on Jun 13, 2018

The repository I’m trying to access is a private repository hosted by github. I’m using my github credentials to access this private repository.

This happened to me as well, when I read that your repo is a private one as well I decided to make mine public and tried to access it through github desktop afterwards. It worked, hope this helps!

dotish on Jan 24, 2019

Same problem here.

Cannot fetch/push from a remote non-GitHub.com repo via https using the GUI button in the new GitHub Desktop v1.1.1.
Fetch/push works via command line using Git bash.
It also works with the old GitHub Desktop and its GUI button.
So there is something wrong just with the new GitHub Desktop GUI version and https repos other than GitHub.com.

mschroen on May 28, 2018

Try going to the toolbar > Repository > Repository Settings I was using SSH but changed it to HTTPS and it worked

alejovdev on Feb 20, 2020

In my case helped deleteon of this in registry: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor\Autorun]

ziimakc on Jan 20, 2019

Not working for me either, exact same issue

adamski11 on Jun 8, 2018

@jborn thanks for updating this issue with the latest log files, and I am sorry that we still have not yet been able to track down what is causing these authentication errors. I installed a fresh Windows 10 VM in VirtualBox on my macOS machine but was unable to reproduce this issue.

Would you mind running one more command from one of these VMs where you are experiencing this issue?

git config --list --show-origin

Please let me know the output of that command.

Also, have you tried performing a fresh reinstallation of GitHub Desktop to see if that helps with this issue (just to make sure nothing is corrupt that could be causing these errors)? To do this, you will need to close GitHub Desktop and delete the following two directories:

%LocalAppData%\GitHubDesktop %AppData%\GitHub Desktop

Then try reinstalling again. Let me know if that helps at all.

steveward on Oct 4, 2018

Just sign out and sign in again. 👍

KashyapCKotak on Jul 20, 2018

It worked for me when I logged out of my account and logged in back

mounikamuddasani1 on Jul 5, 2018

I’m on Windows 10 x64 and I started getting this issue after I had added a .cmd file to be autorun upon opening the command line prompt. @ReTWi’s solution worked for me.

I dug a bit deeper and found that in the file I had created, I had echo statements. Removing them from the file fixed the problem.

It seems thus that the authentication is being broken by the additional statements written to the command line upon running this autorun file.

Doggie52 on May 5, 2020

I was having the same problem, and I wasted a lot of time trying to fix it, following various solutions to propose some issues here. So I decided to sign out from the account in Github desktop, and login again. And this worked for me.

Go to File > Options> Accounts > Sign out > and Sign in again.

In my case, cloning my repository, I used my github.com account on the Github desktop, and I get an same authentication failed when using an https repository URL (as first described). So doing this procedure my same problem has been solved.

mirianfsilva on Jan 18, 2019

I agree with jborn. Many people have the problem and here are only super-specific fixes that do not solve the problem at its root. We all can push and pull in a standard way, with other software or terminal, using default credential settings. But GitHub Desktop seems to use some bugged credential or ssl lookup which breaks the whole thing. Just implement a simple push and pull command that uses the default options without fancy additions, and it will work as expected. One year later. Thanks.

mschroen on Jan 16, 2019

@shiftkey @jborn It looks like a ssh key issue. Generating a new key fix the problem for me: https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/

selimanac on Sep 13, 2018

I have the same problem with repositories set up with ssh remotes. Fetch from Git Bash works, but not from the Desktop program. If I remove the passphrase on the key, it works from the Desktop program. I would prefer to have a passphrase on the key though.

Windows 7, Github Desktop 1.1.1

justinmcgrath on Apr 23, 2018

I can confirm that logging out and back in does not fix this issue. I restarted my machine between signing out and signing back in in one attempt.

I noticed that the command line git package was out of date on my machine, so I updated that to the latest version, but that also did not fix the issue.

jborn on Apr 20, 2018

@patrickfcf head over to #4181, somebody suggested using https instead of http under repository settings. Could you comment and let us know if that fixes it for you?

patrickdundas on Mar 14, 2018

@sergkop the “The user name or passphrase you entered is not correct” error on macOS is probably related to keychain access - see this workaround which has worked for lots of people https://github.com/desktop/desktop/issues/3263#issuecomment-344590213

shiftkey on Jan 19, 2018