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.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Community, I'm Julia and I'm on the Jira Software Cloud marketing team! We're looking for companies or teams using Bitbucket Cloud and Jira Software Cloud. If your team fits the t...
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!
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