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 Join to answer
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...

708 views 0 4
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot