Forums

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

How do I connect SourceTree to my Bitbucket account from a second computer?

tiberius
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!
November 6, 2023

Greetings.

I've been using my own laptop for over a year and it has no issues accessing my work's BitBucket account through SourceTree. Recently I've needed to add a work laptop so I can access the same account. However, SourceTree on the new work laptop refuses to allow me to clone a repository using the same URL. It always gives, "This is not a valid source path." My work computer is logged into Bitbucket with no issues. SourceTree on the work laptop can also access the repository branches that I copied over to it from my personal laptop. I just can't clone anything. What's up? This is supposed to be automatic. I'm not allowed to use my personal laptop anymore for code development, but the work laptop does not have access, so I cannot checkin code for release. Please help.

Tiberius

1 answer

0 votes
Martin Runge
Community Champion
July 3, 2026

Hi @tiberius

Welcome to the Atlassian community!

Since this thread is from late 2023, did you manage to get the second laptop up and running? If it's still relevant, the "not a valid source path" error usually means that while the new laptop can access Bitbucket through the browser, Sourcetree might not have the correct credentials or Git configured yet, which is why it can’t resolve the clone URL.

I would check these on the work laptop:

  • Confirm Git is installed and configured under Tools > Options > Git, since a missing embedded Git alone triggers that exact error.
  • Add the account anew via Tools > Options > Authentication, using an app password for HTTPS or an SSH key instead of assuming the browser login will carry over.
  • Clone using the actual Git URL ending in .git from the Clone option in Sourcetree within Bitbucket, not the browser page URL—this is the most common reason for that message.

Copying a repo folder from the personal laptop does not include the credentials, so the work laptop still needs its own auth set up once. Did this end up being the Git path, the credentials, or a proxy on the work machine?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events