Error deploying with git (dokku) - timeout / broken pipe

Question

I have been using the digital ocean dock for a while without any problems

I had a problem deploying to dokku using the following command:

git remote add dokku dokku@some-ip :myapp git push dokku develop:master 

I have the following problem:

 Counting objects: 528, done. Delta compression using up to 4 threads. Compressing objects: 100% (509/509), done. packet_write_wait: Connection to some-ip port 22: Broken pipe fatal: The remote end hung up unexpectedly error: failed to push some refs to ' dokku@some-ip :myapp' 

I'm trying to

• set ServerAliveInterval for ssh client
• git config http.postBuffer 209715200 / git config ssh.postBuffer 209715200

but that will not work. I think this is because the content size for push is a little high ...

Thank you for your help!

Update

After setting the postBuffer parameter to 209715200 , I got the following error:

 Counting objects: 528, done. Delta compression using up to 4 threads. Compressing objects: 100% (353/353), done. Timeout, server some-ip not responding.38.00 KiB/s fatal: The remote end hung up unexpectedly error: failed to push some refs to ' dokku@some-ip :myapp' 

The final progress clue that you have before downloading:

 Writing objects: 87% (466/531), 33.85 MiB | 120.00 KiB/s 

Answer 1

The first is

  git config http.postBuffer 209715200 / git config ssh.postBuffer 209715200 

It doesn't matter if you click SSH (port 22):

 packet_write_wait: Connection to some-ip port 22: Broken pipe 

Your error has nothing to do with the configuration, but with a poor Internet connection / low bandwidth somewhere between you and the destination, which leads to the fact that large packets are broken on tcp and lost.

It has been discussed in detail here . Try:

1) switching to http (this will increase the size limit for the brake due to slightly smaller header headers)

2) reduction in repo size (repack or gc -aggressive)

However , this will only work if you are on the verge of receiving it. If your connection is really bad, you cannot physically transmit large (also because it contains multiple headers) data packets, then the only fix:

Increase your bandwidth (switch to LAN, change network, etc.). This may be a requirement both on the client side and on the receiving side.