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

Question

I use dokku with digital ocean for a while now without any problem

I have a problem now when deploying to dokku leveraging 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 try

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

but it doesn't work. I think it's because the size of the content to push is a bit high...

Thanks for your help!

Update

After set the postBuffer option to the value 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 last progress hint I have before the upload hangs is:

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

Answer 1

Firstly, this

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

Won't make any difference, as long as you are pushing over SSH(port 22):

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

Your error has nothing to do with configuration, but with bad internet connection/low bandwidth somewhere between you and destination point, which results in big size packets being broke in tcp and lost.

It's extensively discussed here. Try:

1) switching to http (this will increase size limit for brake due to a bit smaller header overhead)

2) decreasing repo size (repack or gc --aggressive)

However, this will work, only if you are on the verge of getting it there. If your connection is really bad you can't physically transfer big( also because containing multiple headers) packets of data, then the only fix:

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