Bitbucket - hit git. Package damaged | Broken pipe

Question

Most of my repositions suddenly had a strange problem. I used various types of files (.html, .pdf, .png, .js, .css, etc.) for normal operation via SSH for Bitbucket without any problems.

A few days ago, I started getting the following error when trying to click:

A message was received about disconnecting from 104.192.143.3: 2: the package was fatal: the remote end unexpectedly hung up

It seems that when images or PDFs are included in my commits. For minor changes to text files I can click without problems.

I tried to click through HTTPS and got the following error:

error: RPC error; result = 56, HTTP code = 0
fatal: the remote end hung up unexpectedly.

Tried to increase httpPostBuffer:

(git config http.postBuffer 524288000)

but without success. Tried to create a .gitattributes file for proper file processing, and then deleted the cached index, again without success.

I am working on Ubuntu 14.04 LTS. Git version 1.9.1.

I tried to reproduce the error on a Windows machine by cloning a repo and making similar changes, but I could not, because it was moving normally.

I am stuck.

Any help assigned.

Thanks in advance,
George Georgopoulos

Answer 1

In my case, I switch my ADSL connection to the hot spot of my smartphone and it works ...

Answer 2

Another solution is to install a speed limiter on your computer.

I installed Network Link Conditioner from Apple, set the maximum download speed to 500 kbps, and I can click on the bitpack again.

Get Network Link Conditioner from the apple developer site. This is part of the IO Tools hardware for the Xcode package. It was a bit uncomfortable to run. I had to install a version that matched my Xcode installation before it worked, and reboot at least once.

Answer 3

I also had this problem (on three different repositories on two different PCs). I know this did not work for you, but switching to https allowed us to push the commit, which caused problems, and then switched to ssh and had no problems since then.

It seems that these specific commits are not the cause of these problems.

Answer 4

I had the same problem. I connected using PIA and it works great!

Answer 5

Connected using VPN and fixed the problem. It is very sad that some Internet service providers and / or system administrator block access to bitbuket.

Answer 6

I had the same problem and contacted support. They asked me if I was behind any firewall or proxy server that I was not.

But I just decided to change my ISP and try again, and voila, it worked. Just in case, this helps someone else.

Answer 7

I had the same problem on a VMware Ubuntu 14.04 virtual machine running on Windows 10.
The git version was the same as yours (1.9.1), which led me to your question.
I tried many different things (including recompiling git with openssl), but nothing worked.

At some point, I changed the network settings to VM (the selected bridge instead of the NAT network interface), and it worked.

It turned out that the solution to my problem is not related to a specific system. I hope this answer saves other people from trouble.