The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How can I fix the error: fatal: could not read Username for 'https://github.com': Device not configured

Harald Maier
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 22, 2013

HI, does anybody know how to fix this error:

fatal: could not read Username for 'https://github.com': Device not configured

...during merge:

Errors during merge

Switched to branch 'master'

Switched to branch 'develop'

fatal: could not read Username for 'https://github.com': Device not configured

Could not push to develop from origin.

3 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote
Ronald DiFrango
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 9, 2015

I'm seeing something similar and have yet to find a resolution with the URL removed as its an internal private GitHub instance:

 

git -c diff.mnemonicprefix=false -c core.quotepath=false -c credential.helper=sourcetree push -v --tags origin refs/heads/development:refs/heads/development refs/heads/master:refs/heads/master 
Pushing to https://<my URL>/<REPO>.git
error: git-credential-sourcetree died of signal 5
fatal: could not read Username for 'https://<my URL>': Device not configured
Completed with errors, see above

 

I'm on OS X Yosemite with the git version:

git version 2.3.2 (Apple Git-55)
1 vote
stevestreeting
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
January 22, 2013

He's using HTTPS so SSH keys aren't related.

I haven't seen this but I've Googled some reports of this when installing your own system git and using the 'credential-osxkeychain' extension to get the command-line git to use OSX's keychain to log in over HTTPS links. You don't need that extension to work with SourceTree, it provides its own integration with the keychain, so if you've done this it would be worth disabling it to see if that helps.

0 votes
KieranA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
January 22, 2013

Just as a quick, have you set your public/private keys up correctly?

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

TAGS
AUG Leaders

Atlassian Community Events