Existing connection forcibly closed by remote host

We're getting a lot of "An existing connection was forcibly closed by the remote host" errors on clones and large updates to Mercurial repos in BitBucket. It happens almost every time at the office, and just once in a while from home. What could be happening on our end that would cause BitBucket to forcibly close the connection and what can we do about it?

We've found that if we add the --uncompressed attribute to the hg clone command, it seems to work fine. Problem is, we can't get that to work inside SourceTree.

We're using both SSH and HTTPS to connect and our Internet connection both in the office and at home is over 40 Mbps.

0 answers

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted Friday in Bitbucket

What is your #1 piece of advice to new users getting started using Bitbucket?

Hello Community! My name is Claire Maynard, and I’m a Product Marketing Manager on the Bitbucket team. I’m interested in hearing what advice or tips you have for new users getting started on ...

169 views 9 2
Join discussion

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