Suddenly getting 503 errors with SourceTree

Out of the blue, four repositories on BitBucket which I cloned with SourceTree a few days ago are suddenly producing 503 errors when I try to do a Fetch or Pull operation.

Just for grins I deleted one of the repositories and tried to clone it again and just got the 503 error.

I can access the repositories just fine through the web interface

3 answers

Same exact thing is happening to me. The command line gives the same results, so it doesn't appear to be a SourceTree issue but a BitBucket issue.

Tried again just now and everything seems to work fine.

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

1,747 views 1 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you