kex_exchange_identification: read: Connection reset by peer

[Ivelin Ivanov]

Hello,

For the past two weeks, I’ve been experiencing an intermittent issue when running git pull. The error occurs sporadically, but not every time. Below is the error message:

kex_exchange_identification: read: Connection reset by peer fatal: Could not read from remote repository.

Sometimes, the git pull command works fine, and I receive the message "Already up to date." However, other times, the connection resets, and I cannot pull updates from the repository.

Here are some examples of the output:

x@server1:/public_html$ git pull

Already up to date.

x@server1:~/public_html$ git pull

kex_exchange_identification: read: Connection reset by peer fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.

x@server1:~/eu/public_html$ git pull

kex_exchange_identification: read: Connection reset by peer fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.

x@server1:~/public_html$ git pull

kex_exchange_identification: read: Connection reset by peer fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.

x@server1:~/domains/store.getwebsite.eu/public_html$ git pull

Already up to date.

and so on...

This issue occurs intermittently, without a clear pattern. We would appreciate your assistance in investigating the problem, as we have multiple websites relying on this Git repository. Consistent updates are crucial to our automated system, and these errors disrupt our workflow.

[Ben]

Hi @Ivelin Ivanov 

That error message usually means that Bitbucket is terminating the connection due to a problem on the client-side.

May I know if you are connecting with a VPN? If so, I'd suggest testing with the VPN disabled, or resetting your router/trying a different network connection.

Cheers!

- Ben (Bitbucket Cloud Support)

[Ivelin Ivanov]

No it's from my Ubuntu VPS hosting. Its work fine for a years, but last 2 months, I start getting this error every day.

[Ben]

Hi @Ivelin Ivanov 

We recently added some new IP addresses and retired some old IP addresses, this may explain why you are getting intermittent failures - as this was finalised toward the end of August this year

Could you please review the following page - perform whitelisting if you have not already done so and let me know if it resolves the issue?

• https://bitbucket.org/blog/ip-address-update-2024

Cheers!

- Ben (Bitbucket Cloud Support)