ssh reset by peer when fetching from several repos

Question

Hey,
I have several git repos in one pycharm project,
I also have a pycharm plugin that auto fetch my repos every hour or so.
ever since I changed my connection to ssh I get the following notifications
ssh_exchange_identification: read: Connection reset by peer

If I fetch one by one I can but it's a hassle, so is there any reason for that?

seems like bitbucket is limiting the connections

Theodora Boudale · Answer

Hi Ofek,

I see that the repos you have access to belong to workspaces on a paid billing plan, so I would suggest creating a ticket with Bitbucket Cloud support team for further investigation.

You can create a ticket via https://support.atlassian.com/contact/, in "What can we help you with" select "Technical issues and bugs" and then Bitbucket Cloud as product.

Please make sure to mention in the ticket what you have tried/tested from my suggestions above. You may also be asked for additional info from the engineer that will work on your ticket, in order to troubleshoot this.

Kind regards,
Theodora

Ofek Ishay · Answer

Hi Theodora,
Thank you for your answer,
I've tried all tested all issues, seems like I still cannot fetch or pull my several repos.

Theodora Boudale · Answer

Hi Ofek,

There are many possible causes for the error you are seeing:

* The most common one is misconfigured Access Control Lists and Firewalls that may be rejecting traffic to Bitbucket's IP addresses. I suggest checking that the IPs listed in the following link are whitelisted* https://support.atlassian.com/bitbucket-cloud/docs/what-are-the-bitbucket-cloud-ip-addresses-i-should-use-to-configure-my-corporate-firewall/

* The second most common cause is higher MTU/MSS values in the packets we receive, you can check the following article for troubleshooting:* https://confluence.atlassian.com/bbkb/troubleshooting-bitbucket-cloud-mtu-mss-issues-858778091.html

* Another less common cause for TCP resets may be due to Anycast Shift:* https://community.atlassian.com/t5/Bitbucket-articles/Diagnosing-and-Troubleshooting-TCP-Resets-from-Bitbucket-Cloud/ba-p/1562132

You can try modifying the hosts file of the operating system to direct traffic to one of Bitbucket's legacy IP addresses18.205.93.2
18.205.93.0
18.205.93.1

and check if the issue is resolved afterwards.

Kind regards,
Theodora