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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,467,421
Community Members
 
Community Events
177
Community Groups

Cannot connect to remote repositories

I have a user who has three remote repositories set up and working. We have recently changed her username, and since then, she cannot create any new remote repositories. 

When she clicks on the new tab and selects "remote", the connection shows with a red cross and does not connect, even though when editing her "hosting account", the authentication shows as OK - green tick.

I suspect this is permissions at the remote end (bitbucket). 

Please assist!

1 answer

0 votes
Mike Corsaro Atlassian Team May 15, 2019

Hello! As a work around the user should be able to also create the repository in Bitbucket itself, and then manually clone the repository using the URL in Sourcetree.

 

Could you try the following?

  • Have the user remove all credentials from Sourcetree (Tools > Options > Authentication). Make sure the entries under "Git Saved Passwords" are also removed
  • Restart Sourcetree, and have the user re-add their account

 

Additionally, this scenario can be completely avoided in the future by using SSH keys for authentication rather than username and password. You can find instructions for doing that here.

Hi Mike. 

Thanks very much for your reply! I have asked the users to do this and they report that they are still having the issue. 

I have uploaded a screenshot to try and explain the issue further.

Kind regards,

Richard

error.jpg

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events