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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Cannot clone private GitHub repository (and yes, I'm using a PAT)

Ok, a bazillion people have posted about this symptom.  And they all start with "but I'm different."  Well, me too.

I just refreshed my PAT in GitHub and reentered it as the password for my account in SourceTree.  Now when I go to clone I can see all my repositories, public and private.  But when I select a private one the message shows "This is not a valid source path / URL", and the details say that authentication failed.  Here's what I know:

  • This all used to work as recently as a month ago.  Sigh.
  • I've updated SourceTree and the embedded Git
  • There's only one configured account and it's set to default
  • Clearing saved passwords didn't help

This is on Windows, in case that matters.  Stuck!

1 answer

1 accepted

3 votes
Answer accepted

Ok, I resolved (?) this as follows, adapting one of the password-clearing tips:

  1. Changed authentication for the account from basic to OAuth, sign in
  2. Close SourceTree
  3. Remove the file C:\Users\Tom\AppData\Local\Atlassian\SourceTree\passwd
  4. Start SourceTree
  5. Do a pull or something else that requires authentication.  Even though the OAuth token is current you are still prompted for a password here.
  6. Paste in your Personal Access Token for the password

And you're back up.  My mac configuration did not have this issue, and it's not using a PAT anywhere.  It was at OAuth already, which is the main reason I did step 1 to get them consistent.

But it looks like there is a super-double-secret password storage that is invisible and separate from what you see in the Accounts section.   Urp.

I just wanted to say thank you for sharing your solution. I spent hours trying to get my new install working. The "delete the passwd file" step fixed me up. Cheers

Nikolas Nikolaou
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!
Feb 01, 2023

Thank you so much. I've been struggling with this for ages. You are a hero.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events