1

This error (fatal: the remote end hung up unexpectedly) keeps popping up when I tried to push my work to GitHub.
Tried all the solutions mentioned in the articles; error: RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err 1)

Few to mention

  • git config --global http.postBuffer 524288000
  • git config --global http.version HTTP/1.1

    Help me out here..
Tharaka Malwaththa
  • 11
  • 1
  • 5
  • 2
    You won't see this problem if you're using HTTP 1.1. What error message do you get when you set `http.version` to `HTTP/1.1`? Also, please [see the Git FAQ}(https://git-scm.com/docs/gitfaq#http-postbuffer) about why you should not set or need to set `http.postBuffer`. – bk2204 Aug 25 '21 at 21:19
  • Downsizing to HTTP 1.1 is almost never a good idea, we should go forward instead of backwards. It's best to look for different solutions first IMHO. – MS Berends Aug 30 '21 at 13:14
  • Yes. I slightly have some idea that downsizing HTTP version is not good. I did it because I had no other option. To answer both questions, the error I get is the same in spite of HTTP version. – Tharaka Malwaththa Aug 30 '21 at 15:35
  • Currently have the same problem, it only happens when a filesize is > 400kb, have you found a solution? – K i Jan 31 '23 at 06:10

1 Answers1

0

Ran into this today, although I never had this before.

Your post buffer setting might be a bit overkill. Try to use a value like:

git config --global http.postBuffer 157286400
# and then
git push
MS Berends
  • 4,489
  • 1
  • 40
  • 53