git push (over SSH) fails with "broken pipe" error

[Aleksandar Pesic]

I was struggling few days to resolve issue with pushing a new repository to my local (on-premise) Bitbucket Server implementation. I was trying to add an existing code to a new Bitbucket repository by following:

cd existing-project
git init
git add --all
git commit -m "Initial Commit"
git remote add origin ssh://git@bitbucket.mydomain.com:7999/phscs/temp.git
git push -u origin master

But whenever I tried to actually push (the last line), I was getting an ugly error:

packet_write_wait: Connection to 172.16.1.1 port 7999: Broken pipe
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly

I was also trying to push over HTTPS, but with no luck. With HTTPS I was getting some RPC call related error.

Very strange facts:

• I was able to clone any existing repository to the same client machine;
• I was even able to push, but only if I add a single file (instead of "git add --all" I've used "git add file_name"). It's important to note that there were no too many files - under 50 files, few hundreds KB in total, so it cannot be about the size.

Finally, I've solved it. The answer is below.

Update: I'm not able to post the answer here, probably because the question is for some reason marked as "spam" (????)

So you won't be able to see the answer, thanks to Atlassian. Ridiculous!

[Deleted user]

I had that issue when working with an arch distro on VMWare.

Adding

IPQoS=throughput

to my ssh config (~/.ssh/config) did the trick for me.

[Krzysztof_Matysik]

Thank you very much, it worked for me :)

[Daniel Morán]

it worked!

[Steve]

I've searched for an answer to this and read literally every single page on the web.  

This is the answer that worked for me.

[Stephan Krauß]

Hi @Aleksandar Pesic, are you able to post the answer again please?

[Aaron Smith]

Hi Aleksandar

Are you able to try and post the answer again please?

Regards

[Ana Retamal]

Hi Aleksandar! This question is not showing as Spam to me, maybe our filter marked it as Spam by accident, but now it's been cleared (it happens sometimes!).

Would you mind sharing your solution with the rest of our Community, so hopefully it will help someone else?

Kind regards!

Ana