Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
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

Source Tree not working properly after password reset

After originally setting up Source Tree to connect to our Bitbucket repository server, everything was working fine.  Then I had to change my password due to 90 day expiration and things started messing up.  I constantly have to re-enter my password in the account settings, after going to the stash login page to clear the captcha.  Then I get a green check mark by my account info for a short period before the issue re-appears.

What's more is, even immediately after doing so, I get this error when trying to pull down a repo:

Repository Type:  This is not a valid source path / URL

More Details: "Command: git -c diff.mnemonicprefix=false -c core.quotepath=false ls-remote
Error: fatal: ArgumentException encountered.
An item with the same key has already been added.
fatal: ArgumentException encountered.
An item with the same key has already been added.
fatal: Authentication failed for ''"

The URI path is 100% correct, and it does not matter if I go to a project and choose clone, or go to the stash site and copy the URL or click on the application hyperlink to open in Source Tree.  The third and final issue is that not all projects are displaying for me when I go to "Remote" and view the list of projects.


Anyone have any advice on what my issue might be or how to solve it?  I've tried deleting all the credential entries in Windows Credential Manager.  This is Source Tree

1 answer

1 accepted

5 votes
Answer accepted

You can delete the stored password in Sourcetree by going to c:\users\<your user ID>\AppData\Local\Atlassian\Sourcetree and rename/delete the passwd file. That usually helps when my developers change their passwords and get this error when using Sourcetree.

Thanks for the suggestion, I will give this a try!  I was able to work around the issue by changing the git URI and manually specifying username/password on clone.  Hopefully your suggestion will let me address the underlying problem directly.

This works so far.  I will wait a few days and make sure it stays functioning, then will mark this as the answer.

Enough time has elapsed with the issue fixed to convince me this was the solution.  Thanks again Mikael!

Thanks this worked for me. :)

The Solution worked for me as well. Thanks!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket

📣 Calling Bitbucket Data Center customers to participate in research

Hi everyone, Are you Bitbucket DC customer? If so, we'd love to talk to you! Our team wants to dive deep to understand your long-term plans regarding Bitbucket DC and Atlassian Cloud. Do you plan...

117 views 2 4
Read article

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