Existing connection forcibly closed by remote host

cvandenbout October 20, 2017

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
TAGS
AUG Leaders

Atlassian Community Events