Problem after installing Sourcetree 2.1.7.0
Asked by eugeniomiro:

I've just upgraded Sourcetree from 2.1.6.0 to 2.1.7.0 and realized a repository which is not on Bitbucket nor Github, but an old Linux server using SSH is not accessible because all credentials now apparently need to be related to Bitbucket, Bitbucket Server or Github.

I can't see in the new UI an option to add credentials for a server not related to that.

Is there any way to configure that somewhere else?

Thank you in advance.


Answers:
author: Ryan Smith
body: I finally found a solution to this. If you remove the passwd file, Sourcetree will recreate the file and allow you to reauthenticate all of your repos when you try to connect.

comments: author: eugeniomiro
body: You saved my day [@Ryan Smith](/t5/user/viewprofilepage/user-id/1142681), thank you very much! This worked like a charm.


author: Ana Retamal
body: Hi Eugenio! We only provide account profiles for Bitbucket Cloud, Bitbucket Server and Github by default, but you can still connect to different services or your own server. To do that, use the **Clone from URL** feature to check out repositories from SourceTree using SSH.

For more information, you can read [How do I use SSH with SourceTree](https://confluence.atlassian.com/bitbucket/how-do-i-use-ssh-with-sourcetree-282173660.html).

Hope this helps!

Ana

comments: author: eugeniomiro
body: Thank you, Ana, for your fast response.

I actually had a user already configured with repository credentials before updating to 2.1.7.0 and the repository is still configured as it was. What happened was that it started to complain about invalid credentials when I fetched new changes from the repo using the UI, and the only way to get them after the update was using the command line and provide the credentials manually.

I don't actually have a UI to update those credentials if they change either, I can only see those related to Bitbucket Cloud, Bitbucket Server, and Github.


author: eugeniomiro
body: I'm adding below the log I'm getting when I push the fetch button
> git -c diff.mnemonicprefix=false -c core.quotepath=false fetch --prune origin  
> Access denied  
> Access denied  
> Access denied  
> Access denied  
> Access denied  
> FATAL ERROR: Server sent disconnect message  
> type 2 (protocol error):  
> "Too many authentication failures for eugenio.miro"
>
> <br />
>
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights  
> and the repository exists.
>
> Completed with errors, see above.


author: Ana Retamal
body: Hi Eugenio, what do you mean by:
> I don't actually have a UI to update those credentials if they change either, I can only see those related to Bitbucket Cloud, Bitbucket Server, and Github.

If you use Windows, you'll find how to do it at [Clone a repository into SourceTree](https://confluence.atlassian.com/sourcetreekb/clone-a-repository-into-sourcetree-780870050.html#ClonearepositoryintoSourceTree-Method#1-DirectlythroughtheSourceTree'sMainUI). If you use Mac, you can find that option by clicking in **New:**

**![Screen Shot 2017-07-25 at 11.26.05.png](https://community.atlassian.com/t5/image/serverpage/image-id/3535i7398AE5C206F694C/image-dimensions/333x209?v=v2 "Screen Shot 2017-07-25 at 11.26.05.png")**

Is that what you were referring to?

Regards,

Ana


author: Ryan Smith
body: I'm also running into the same error as Eugenio when upgrading to 2.1.7.0. The credentials for all of my repos have been reset and there doesn't seem to be a way to enter new authentication info through the GUI.


author: Ana Retamal
body: Hi [@Ryan Smith](/t5/user/viewprofilepage/user-id/1142681), you can add a repository by URL by clicking on **New \> Clone from URL** as you can see in the screenshot in my previous comment. Note that you can not enter it through the **Accounts** menu, that's only for Bitbucket Server, Cloud and Github.

Can you find that option? If this is missing in your application, can you send me a screenshot?

Best regards,

Ana


author: eugeniomiro
body: I tried your suggestion and unfortunately, it didn't work as expected, this is the output I get in the Details window, which is the same I get when using the already cloned repository.

![errorSourceTree.png](https://community.atlassian.com/t5/image/serverpage/image-id/3699iFD7C172B865B427E/image-size/large?v=v2&px=999 "errorSourceTree.png")

Moreover, if this worked after removing and cloning the repo again, that wouldn't be the best solution either because I have several local branches I'd like to keep and also several stashes that are useful as they are, I'd prefer a solution keeping the current repository and changing the credentials. I started to check other options like GitKracken if this doesn't work, even if I don't like it so much, but this can be a deal breaker for me... and my team...

I hope we can work around this problem soon, I don't want to be outdated on my tools and this is an important one for me and my team, I already told them to hold on updating to this version until we have a solution to this.

Thank you anyway for your help.


Tags: install

update