Repo issues

[Jeremiah Franklin]

Hello, I am currently running into an issue where I have a private repo that whenever I try to clone it, the url is not being picked up as a repo, saying the path or url is not valid or that I do not have permission (I do have permission). I do not know what to do despite doing the FAQ parts

[Tomislav Tobijas]

@Srikar Janapati I'd say some basic troubleshooting steps on this would be:

Test cloning via git command line - open a terminal and run 

git clone <repository_clone_url>

If that works, the issue is likely with Sourcetree itself. If it fails, there may be a permission or repository access issue.

Update and re-authenticate in Sourcetree - check if you're using latest Sourcetree version and in the app go to File > Clone/New and enter the repo URL. If prompted, re-enter your credentials and double-check that you're using the correct auth method.

Clear Sourcetree saved credentials 

1. Close Sourcetree
2. Navigate to this or similar directory (depending on OS): 

   C:\Users\<your-username>\AppData\Local\Atlassian\Sourcetree

3. Delete the file named passwd > this should remove saved credentials and prompt you to re-authenticate
4. Reopen Sourcetree and try cloning again

If that doesn't work, you'll have to troubleshoot this further by checking the errors you're getting 👀

[Tomislav Tobijas]

Hi @Jeremiah Franklin ,

Can you maybe share where your repo is hosted? 

There's this article about cloning a Git repository if you're hosting it on Bitbucket Cloud: Clone a Git repository 
Not sure if it will help, but it may guide you in some direction.

There's also this one related to generating SSH keys: Set up SSH with Sourcetree 

Cheers,
Tobi

[Srikar Janapati]

I'm encountering same issue where neither source tree nor git bash recognizing the git URL while cloning or fetching. Although I'm the repo admin and project admin, still not able to clone or fetch the things. We're using Bitbucket Data center but not the cloud. It works fine few days but all of sudden on last monday it started returning the error. 

All my fellow users are working normally on that repo and project. 

Any suggestions on this issue?

TIA. 

[Jeremiah Franklin]

What worked for me was putting my username at the front of the URL eg. username@link 

This only happens with private github/lab projects apparently.