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,456,344
Community Members
 
Community Events
176
Community Groups

Remote repository no longer accessible

Everything was fine and then I tried to clone a new repository today and there is a red X on my user name in the Remote window. 

When I hover over it it says...

Unable to read memberships for the user from the remote host

Failed to list teams for user (my user name)

This endpoint has been removed. 

 

I can go to the clone window and clone the repository from there by hand. 

Please advise on how to fix. 

17 answers

1 accepted

Solution: This bug has been fixed in Sourcetree 3.4.8.

Although, for some reason, the website still lists the 3.4.7 version for Windows. Here's a direct link to the Windows 3.4.8 exe until they fix the link on the website.

Here are the release notes for 3.4.8.

Actually, updating to version 3.4.8 prevents the list of repos from loading entirely and now the program crashes at startup, so don't do that. Use the 3.4.7 workaround below until an actual fix is released.

 

 

Solution:

After updating to version 3.4.7, click the "Refresh" button next to your list of repos and it should call the new API instead of attempting to use the old broken one.

 

Other possible workarounds:

  1. Update Sourcetree to version 3.4.7
  2. Go to Remote > "Edit Accounts" and delete your saved accounts.
  3. Close Sourcetree
  4. Restart your computer
  5. Open Sourcetree
  6. Go to Remote > "Add an account"
  7. In the dialog window that appears, choose your host and add your credentials (if you're using basic authentication, be sure to enter your username rather than your email address, otherwise you'll get a cryptic error message)
  8. Click "Refresh OAuth Token" or "Refresh Password"
  9. On the list of repos, click "Refresh".

For the record, I'm having this problem, and I just started with version 3.4.7 that I just installed today, never had an earlier one. The "refresh" workaround appears to work, BUT, I have to do it EVERY SINGLE TIME I start the program.

That's still very broken to me and should be addressed.

Like Christopher Wolf likes this

@Alan Karna - Darn, looks like you're right. Thankfully it only take a few seconds to refresh, but that's really something that Atlassian needs to fix.

Like Alan Karna likes this

This looks like a breaking bug - the Bitbucket API endpoint has changed but SourceTree has not been updated to match.  I don't think there's anything we can do until SourceTree is updated or the API is modified.

Personally I'm going to look around for a new Git client.

After updating to version 3.4.7, click the "Refresh" button next to your list of repos and it should call the new API instead of attempting to use the old broken one.

Like # people like this

Thanks a lot!
Yesterday was a frustrating first day due to this bug

Facing the same problem. 

Am I the only one that find it extremely unprofessional, that they would deprecate their API, but not change it in their own software? 

Luckily it's easy to migrate repositories to Githhub, takes a couple of minutes a piece, so that's what we'll be doing. 

Thankfully, the workaround appears to be simple. Update Sourcetree to version 3.4.7 and then click Refresh next to your list of repos, at which point it should start using the new API endpoint.

Updating to 3.4.7 worked for me.  My 2 cents...

Just upgraded both of my machines to 3.4.8, problem is gone. The remote repositories now auto-populate without having to click on Refresh. Woo hoo!

Unfortunately, this appears to have made the program even worse on my end.

The repo list still won't load and I now have to uncheck and recheck the checkbox instead of just clicking "Refresh".

Also, the program now frequently crashes at startup, so I'm going to have to revert to 3.4.7 for now...

Anyone else still getting this error on their Mac?

I'm on version 4.1.6 and I still can't create or clone remote repos.

I was able to work around this by switch from OAuth/SSH to Basic/HTTPS. Not ideal, but at least it's working.

How do I understand this tool is abandoned?
Judging by the dates on the messages, this critical bug has not been resolved for so long.
This is my first time using git, and I wanted to work with GUI right away, so as not to waste time memorizing console commands, this tool was advised to me as the best option for a beginner, under Windows, but i realizing that it is probably better to start with another one.

No, it had a bug that affected some people using it.  Later versions fixed it (you can't call it "abandoned" if new versions with bug fixes are being released)

@Nic Brough -Adaptavist- - To clarify, the solution that I posted above (the one that you accepted) is just a reliable workaround for the immediate problem but doesn't fix the underlying bug that's still present in the program.

The latest version of Sourcetree (3.4.7) still requires you to regularly click the "Refresh" button due to the broken API calls that haven't been fixed after over three months. This is something that Atlassian needs to address and the lack of an official response after all this time hasn't been reassuring. So while the program may not be truly abandoned, it's definitely not a good look that it doesn't currently work right out of the box.

Yes, that's exactly what I'm talking about, the first report of this (or similar?) error was more than a year ago, and since then there has not been an update to fix it, usually this is the case in abandoned applications. The release date of the penultimate version (3.4.6): 13-Aug-2021 is more than a year ago. I can't see the release date of the latest version in the version archive.

But in general, this is not so important, how important is the fact that many users can still use the program, which means I need help to explain to me how to set it up so that it starts working normally?

Er, all I was pointing out was that the software is not "abandoned", and I don't have the issue.  I am a light user though, so I might not have seen it.  I'm not commenting on whether there is a bug here or not.

Updating manually to the latest Sourcetree fixed this issue for me (ver 3.4.7). If you still have a red cross on your Avatar icon, re-check the pop-up tooltip error, it might be a secondary issue and not the original issue discussed here.

After updating to 3.4.7.0, I still get the red X overlay with no repositories shown. Here is the tooltip I see:

SourceTree.jpg

Clicking on Refresh will then show the repositories.

Sorry, I should clarify - I've cleared the first error "Unable to read memberships for the user from the remote host" and am now just getting the "Failed to list teams for user" which I'm continuing to troubleshooting to resolve.

Edit: Ahh, found the problem - you need to deselect "Show Organization Repos" tickbox. Easy!

Like ma_arizag likes this

For me, that does make the red X overlay go away, but the repositories are still not shown. With "Show Organizational Repos" unchecked, clicking on Refresh does not show them.

I have this issue as well, it won't list my remote repos when I deselect show organization repos. But when i selected it again and refreshed it worked

Like Bitman32 likes this

It looks like you just have to click the "Refresh" button next to the list of repos. The checkbox doesn't seem to matter.

Any suggestions? I am using sourcetree 3.4.7 on a new PC and 3.4.6 on my laptop. It used to work on the laptop, then stopped working, strangely enough at the same time as when I tried to install sourcetree on the new PC. Gives the message "Failed to list teams for user [username] This endpoint has been removed"

I have no idea why, but when I got both of my laptops on 3.4.7, it magically worked. When I try to add a remote repository, it still shows an X overlay over my avatar and no repositories listed. But, when I click on Refresh, the overlay goes away and the repositories appear.

Like ChrisRogersWebDev likes this

Holy sh*t! My avatar had the red X, and then I pressed refresh like you said and magically the red X was removed and all the repos were listed.

Had to work out some credential helper section thing, but it seems to work now.

Thanks very much!

Like ChrisRogersWebDev likes this

I have no idea what the root cause was/is.  This cost me days of time and worry. Manually getting both laptops on 3.4.7 magically got it working for me. Every time I start SourceTree, it will still show  the red X overlay, but I can live with it.

Glad it helped someone.

the red x has now magically disappeared for me ?! It would be nice to get an explanation from Atlassian, has eaten up a lot of people's time.

Like Christopher Wolf likes this

Even though it said program had the latest version, this was not correct. Once I updated from 3.3 to 3.4 it started to work properly.

I had the same problem for days. Tools / Options / Updates reported SourceTree was up to date on version 3.3. Went to Atlassian site and manually downloaded and installed 3.4.7, problem went away.

We updated and it did not resolve the issue.

facing the same 

fyi same problem

FYI, experiencing the same problem too.

It now works. Didn't change anything. I'm still on Sourcetree version 3.4.7.0

 

Looks like they changed something online.

same problem

FYI, I am also experiencing the same problem too, Can you please suggest the solution?

FYI, experiencing the same problem too.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events