desktop: It keeps saying `The user name or passphrase you entered is not correct.`

Description

I have reset my password and git cli and SourceTree both work.

Version

GitHub Desktop version: 1.0.11

OS version: macOS 10.12.6 (16G1036)

Steps to Reproduce

  1. Last Friday it is still working and once I start working again today this application keeps saying login failed.

Expected behavior: [What you expected to happen]

Actual behavior: [What actually happened]

Reproduces how often: I don’t know what is going on. I can’t tell how to reproduce it

Logs

fatal: Authentication failed for 'https://github.com/my/project.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 preferences and verify that you're signed in with an account that has permission to access this repository.)
2017-12-18T03:42:52.250Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 1.825s)
2017-12-18T03:42:52.251Z - error: [ui] `git -c credential.helper= fetch --progress --prune origin` exited with an unexpected code: 128.
remote: Repository not found.
fatal: Authentication failed for 'https://github.com/my/project.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 preferences and verify that you're signed in with an account that has permission to access this repository.)
2017-12-18T03:42:58.963Z - info: [ui] storing generic credentials for 'github.com' and 'tom10271'
2017-12-18T03:42:58.990Z - error: [ui] Error saving generic git credentials: tom10271@github.com
Error: The user name or passphrase you entered is not correct.
2017-12-18T03:43:00.852Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 1.838s)
2017-12-18T03:43:00.854Z - 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/my/project.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 preferences and verify that you're signed in with an account that has permission to access this repository.)
2017-12-18T03:43:23.382Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 1.801s)
2017-12-18T03:43:23.383Z - 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/my/project.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 preferences and verify that you're signed in with an account that has permission to access this repository.)
2017-12-18T03:43:31.069Z - info: [ui] storing generic credentials for 'github.com' and 'tom10271'
2017-12-18T03:43:31.098Z - error: [ui] Error saving generic git credentials: tom10271@github.com
Error: The user name or passphrase you entered is not correct.
2017-12-18T03:43:32.856Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 1.746s)
2017-12-18T03:43:32.856Z - 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/my/project.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 preferences and verify that you're signed in with an account that has permission to access this repository.)

Additional Information

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Comments: 19 (1 by maintainers)

Most upvoted comments

@tom10271 we think this is related to Keychain access due to some sort of macOS update:

Try opening Keychain Access.app. Right-click on the login keychain and try locking it and then unlocking it again.

@tom10271 we think this is related to Keychain access due to some sort of macOS update:

Try opening Keychain Access.app. Right-click on the login keychain and try locking it and then unlocking it again.

It worked!!! THANK YOU!

Please do not reply nice, awesome whatever again

Thanks! But this is weird.