Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Fatal: could not read Password for '': Device not configured Edited

I updated to SourceTree v 2.7.2. this morning and my first push I received this error:

Pushing to

fatal: could not read Password for '': Device not configured

This had never been an issue prior to the update, so I'm thinking the two are connected.

I've tried re-logging in (choosing basic and OAuth with HTTPS as the protocol), restarting sourcetree and restarting my computer but have had no luck.


Help is appreciated!

33 answers

1 accepted

4 votes
Answer accepted
bgannin Atlassian Team Apr 07, 2018

We've identified the fix and will roll out a new build later today. Our apologies for the hiccup.

Awesome, thank you!

Like # people like this

Hi @bgannin,

Same issue here. I'm using the version 2.7.6(177) on a Mac. I'm trying to finish a feature from git-flow menu and I get this error:

fatal: could not read Password for '': Device not configured


I tried to re-login to Bitbucket but no luck

I tried to restart the mac but no luck


Should I do a downgrade?

Like tarasvitruk likes this
bgannin Atlassian Team Jun 18, 2018

@Manju might have a suggestion on this front.

Manju Atlassian Team Jun 18, 2018

@Cleyton Tonholi Are there other actions that result in this error too? Or is it just git-flow? Can you please let us know the account config for your Bitbucket account in Sourcetree? OAuth vs Basic? Or if you are using App Password? Please include a screenshot of the account from Sourcetree's preference. 

Manju Atlassian Team Jun 19, 2018

@Cleyton TonholiPlease use SSH for now. We are investigating this issue. It happens only for git flow and https auth. 

Like Alex_Ermolenko likes this

Hi @Manju,

I didn't test other actions because I was really focusing to finish a feature (via git-flow). The was authenticated via OAuth.

But after selecting System-Git it worked.

Thanks anyways.

@Manju i have same problem
To use ssh bitbucket need to enable pipeline, but it's paid ((


Does any another way to enable git flow in source tree?

Manju Atlassian Team Jun 25, 2018

Using git-flow or ssh does not have anything to do with pipelines. You should be able to use them with Bitbucket without having to enable pipelines on your repo and for free. 

Your solution worked for me @Cleyton Tonholi, thanks so much!

Like VasySav likes this

Well go ahead and Build another update cause getting error on 3.0.6

Using 3.01 for Mac and have this issue on gitflow commands.  Any hints?

Same here: mac version 3.0.5 build 205.  fatal: could not read Password for '': Device not configured



bgannin Atlassian Team Jan 10, 2019

Please vote and comment on appropriate ticket(s) in our public bug tracker. Community is for questions.

Hello @bgannin,

Same here too: mac version 3.0.5 build 205.  fatal: could not read Password for '': Device not configured

When will this bug get fixed? It seems that it was mentioned here in April 2018 and we're now in April 2019...

Adding your password to your URL seems to work but surely cannot be the adequate solution to this issue. What solutions do you recommend?

In the meantime, I've tried finding the ticket in your public bug tracker to vote and comment it, but couldn't find it.

Like # people like this

@bgannin, thanks for the suggestion to add the password in the URL.
This worked for me in an job emergency.

But I agree with you: this isn't the adequate solution to this issue. 

Like brentatseagreen likes this

Hello @Seb P 

Correct link is git-flow issue

Other solution is switch to ssh.

Try change repository link format from "" to ""

It helped for me

This worked for me. Thanks.

its worked for me :D

Many thanks you guy. This worked perfect for me :D

It works! It seems they want our passwords...

It works!!! Thank´s 

Thats Super insecure!!!!

Like # people like this

This worked for me as well!

This worked for me. Thank you!

insecure but it works! :D

his worked for me. Thanks.

Work for me to, Thanks.

Worked for me, too - not really safe :D 

Same problem here! and it's now September 2018

I have just gotten this error for the first time. I am running the latest version, 4.0 (232) on a Mac. Tried to finish a release.

This bug needs to be resolved.

I also just experienced this now 

I'm still having this issue. version 3.1.1 

it's March 2019 - How is this still a thing? lmao

I'm also on mac os x 10.14.3 

Same here...

Sourcetree 3.1
MacOsX 10.14.4

@Atlassian please fix this 

Like nxtcristian likes this

July 10th, 2020, Source v4.0.1 (234)

Still the same

@Atlassian still working on this?

Issue is still present in 2.7.6 (177) — git flow is broken because of it.


Atlassian, please fix it already!

I've the same problem in last version  of sourcetree for mac, any solution? 

This has been a problem for five months now, and it's still biting me! Atlassian, where are you? We shouldn't have to use SSH just to do this basic operation!

It's six months now....Sep 20

I've been having this issue ONLY when trying to finish a feature. Just finished some testing and the problem still existed. Then I tried the solution suggested by @BUROVIC above. Which is:

Try change repository link format from "" to ""

However I get this warning:


To find this setting open the repository and go to Repository->Repository Settings->Remotes tab.

But this worked and I'm not so comfortable doing this.

In the past I've made my commits, moved over to my Windows machine, pulled the changes, and then done the Feature Finish.

Again, this only happened to me when finishing a feature.

Manju Atlassian Team Sep 11, 2018

If this is specific to git flow actions, I would recommend you to move this to a separate thread or submit a ticket on our public issue tracker for us to look into. 

Sourcetree Mac Developer   

Just updated to v3.0 and now this issue is back on my desktop Mac. I never had the problem on my Windows machine. Not sure about my laptop.

Manju Atlassian Team Oct 11, 2018

Is this for a git-flow action?

Same issue, using git-flow action

I got same issue 29-10-2018, using git-flow action.

Cant even login in OAuth method...

This bug was introduced exactly one year ago! Still not fixed. We have to use URL with password in Repository Settings, which is very unsafe. HAPPY BIRTHDAY!!!

Is anybody in Atlassian working on that?

@bgannin , @Manju ?

Same problem today with Sourcetree 4.0

That's bad news. I got it working but have spent hours and hours trying to figure it out. I did switch to an SSH connection but had problems with that too. I went back to a regular connection. It's been working so far but not surprised to hear your report of another failure.

I've been testing the competitive application Fork. It provides more complete error messages and is helpful to sort issues out. 

The issue still exists. Version 4.0 (232). It's really annoying.

Well here it is just a little over one month from my post above where it was all working and now it's not working again.

I've been in software development for over 20 years and once in a while a software product comes along that my peers and I would consider to be "worse than useless". This is such a product. If it were obviously useless you wouldn't waste your time but this is worse than useless because you spend so much time and get nothing for it.

It's often more important as to who you are partnering with in software development as well as the software product they've developed. This is such a case. You would think they would have pride in their product and would contact one of the developers reporting the problem to resolve it but no. They don't care and it's been over a year. 

This happens to me too often. Trying to finish a feature. Getting this error. Just updated to v2.7.4. It was working before the update.

This seems to be a cycle. Works, update, broken, fixed.

I move over to my Windows 10 machine, pull the updates, then do the finish on the feature and it works fine. Running v2.6.3 of SourceTree on Win10.

Of course, then I have to go back to my Mac and pull all the changes.

Great, just upgraded to V 3.0.6 and get this error... how do I now work????

I only get this error when finishing a git flow feature (ver: 3.0)!

you could use the following command in your terminal:

# git flow feature finish branch_name

I downgrade to version 2.7.2, it works for me

Like # people like this

Same problem with Sourcetree 3.0 (200). Occurs when finishing a hotfix e.g.

Manju Atlassian Team Feb 07, 2019

This is a known issue with some of the git flow related actions. The team is looking into it and will address it in an upcoming release. Appreciate your kind cooperation and patience in this regard. 

Same problem with Sourcetree 3.0.1 (205). Occurs when finishing a release via Git Flow.

I use ssh and two factor authentication, but the remote url was set as a HTTPS format. I changed it into ssh-format like this<account_name>/<repo_name>.git, which solved my issue..

Issue is still ongoing without resolution on Mac

Same issue on 3.2.1 !

Same in 3.2.1 on OSX

FIX IT (09/2020)

All the the answers here are wrong... You shouldn't NEVER do something like that:

All you have to do is:

- Go to Sourcetree -> Preferences -> Git
- You will have the section "Git Version" with 2 options: Reset to ebedded Git and Use System Git

Sourcetree use the Ebedded git for default.
Click on "Use System Git" and.... Fixed!


Follow me on:

Thanks. It works!

0 votes
bgannin Atlassian Team Apr 06, 2018

It sounds similar to this: 

"Looks like the problem was that Bitbucket [Cloud] was not configured to use an SSH key, and the console failed once it prompted and didn't return a username or password."

0 votes
bgannin Atlassian Team Apr 06, 2018

We've added a Debug menu (turn on in the Advanced preferences) that also includes authentication logging which should help shed some light on the problem. @Manju will work with you further to isolate the problem. We appreciate your patience and report.

Brian Ganninger
Senior Mac Developer, Sourcetree

Hey Brian,

How do I get that same support. I keep seeing people reporting the same issue but no response yet. I have tried everything anyone has posted regarding this issue since January and then a bunch of other things!

(edited with a clarification) 2.7.2 is only available to 5% of users currently and in beta; we aren't proceeding further with the release until this is sorted out.

bgannin Atlassian Team Apr 06, 2018

@Ryan Sherman There's not a side channel discussion happening, he'll reply here or ask for a ticket to gather more information.

The same for me

Same problem version 2.7.6 on Mac

Same problem for me version 2.7.6 for Mac

Same problem for me version 2.7.6(177) for Mac

I am able to pull and push the commits but when I am trying to finish current branch, I am getting following error:

fatal: could not read Password for 'https://shivam.a.singh@bitbucket****': Device not configured

Fatal: Could not fetch feature/<branch_name> from origin.

+ 1 same problem when I try to finish feature on Git Flow

Try downgrading to 2.7.2.

I downgraded my sourcetree to 2.7.2 and now I can use finish feature in git-flow. I guess I'm sticking to SourceTree version 2.7.2.

Going back to good old Sourcetree 1.9    --- Never liked this new version.

I am still seeing this bug and I am on Sourcetree verison 3.2.1.

Was this issue never fixed or what is the status? Would be great if someone from Atlassian could respond.

I got around the bug by switching to ssh instead.

Like Yohann likes this

@Jonas Altin

Are you on a Mac or Windows machine? If you are on a Mac please explain how to do this. Thanks.

I'm on a mac.


This link should explain how you can do it: (the section that you need to look at is 'Set up SSH with Sourcetree on macOS').

I'm still having the same issue as well ever since I changed my laptop password (AD-backed).

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Sourcetree

[dev team] Sourcetree for Windows 2019 Preview - Dark Theme

Hi folks, While the full post is over on our blog I'd like to share the dark theme we've got planned for 2019 here directly as well to keep the discussion going.  The ...

3,270 views 19 18
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you