Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

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

0 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.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Sourcetree

Tip from the team: configure your repos for hosting goodness!

Supported Platforms macOS Windows We recently introduced support for additional hosting services such as GitHub Enterprise, GitLab (Cloud, Community Edition, Enterprise Edition), and...

3,921 views 4 7
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