error: RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err 1)

Question

error: RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err 1)

I tried 'push' while writing 'git'. However, the following message does not solve the problem.

Answer 1

You can force git using http version 1.1

git config --global http.version HTTP/1.1

https://gist.github.com/daofresh/0a95772d582cafb202142ff7871da2fc

Answer 2

You might be pushing data larger than the postBuffer size.

You can try increasing post buffer size using

git config --global http.postBuffer 157286400

For reference: https://confluence.atlassian.com/bitbucketserverkb/git-push-fails-fatal-the-remote-end-hung-up-unexpectedly-779171796.html

Answer 3

Simple solution (reverts to http 2 after) :

git config --global http.version HTTP/1.1
git push 
git config --global http.version HTTP/2

Answer 4

XCode 11.4.1

Increasing the git buffer size worked for me

git config --global http.postBuffer 524288000

Answer 5

Working Solution:

First change HTTP version to 1.1 and then push and once done change back to HTTP2

$ git config --global http.version HTTP/1.1
After it push was ok and I have changed HTTP version to 2 again:
$ git config --global http.version HTTP/2

Answer 6

git config http.postBuffer 524288000

This is the latest, should solve your issue

Answer 7

I followed most of the answers but not solved my problem.

In my case, the answer is very simple

I encountered this error when pushing GIT through an ADSL Broadband Wi-Fi network with low signal strength, low stability, and low speed.

Then, I was able to push it very successfully when I pushed it into the GIT through a Fibre Broadband Wi-Fi network with greater signal strength, greater stability, and higher speed.

Error:

Push failed Enumerating objects: 44, done. Delta compression using up to 12 threads RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: CANCEL (err 8) the remote end hung up unexpectedly Total 30 (delta 18), reused 0 (delta 0) the remote hung up unexpectedly

Answer 8

It's was not working for me. But worked after downgrading version of HTTP from 2 to 1.1:

$ git config --global http.version HTTP/1.1

After this change, pushing was successful and I have changed HTTP version to 2 again:

$ git config --global http.version HTTP/2

Answer 9

In most cases git config http.postBuffer 524288000 should work.

In my case, I was pushing a large number of changes (I changed a lot of packages thus there were many lines updated) in my yarn.lock/package-lock.json file. Since it is usually not required, removing it made the error go away. So you can try this too if you are working with Javascript

Answer 10

In most cases, increasing the buffer size will work.

git config http.postBuffer 524288000

It worked for me.

Use of

git config --global http.version HTTP/1.1

should be kept as a last option.

Using a gitbash terminal on a windows machine (if this info helps you in any way).

Answer 11

It sounds like either the remote server you're using or some middlebox (e.g., a proxy) is not speaking the HTTP/2 protocol correctly. You can either fix that by asking the owner of that remote server or middlebox to fix their server, or you can force the use of HTTP/1.1.

If you want to force the use of HTTP/1.1, you can set the http.version configuration option to HTTP/1.1. That can also be set on a per-URL basis as described in the http.<url>.* section in the git-config manual page.

Answer 12

For my case with the bitbucket behind nginx, disabling proxy request buffering was the answer:

server {
    listen 443 ssl http2 default_server;
    ...
    proxy_request_buffering off;

    # These are also relevant:
    proxy_read_timeout      600;
    client_max_body_size    0;

Answer 13

I went through a similar situation. I tried;

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

even,

git config --global core.compression 0  

but, nothing changed. I had two folders with this error. one with 10MB size and one with 65MB.

finally. I tried with a Fibre connection.

So yeah. try with a different, higher speed connection. probably it will work.

Good Luck!

Answer 14

In my case I had to reset the origin to ssh instead of http/https:

git remote set-url origin git@your-git.com

To check your origins you can use:

git remote -v

Answer 15

My issue was slightly different, with a "packages already packed" info with the RPC::HTTP/2 stream not closed cleanly message.

For me this worked:

git checkout --orphan newBranch
git add -A  # Add all files and commit them
git commit -am "Clean Repo"
git branch -D master  # Deletes the master branch
git branch -m master  # Rename the current branch to master
git push -f origin master  # Force push master branch to github

Thanks to: https://panjeh.medium.com/cleaning-up-git-github-repository-without-deleting-git-directory-c86b7415b51b

Answer 16

One of the most popular answers is:

git config --global http.postBuffer 157286400

Don't do this blindly as raising this is not, in general, an effective solution for most push problems, but can increase memory consumption significantly since the entire buffer is allocated even for small pushes(from the git documentation).

Check if you've files with size >100 MB first. If yes, then there is a better-suited solution for your problem.

Solution: Git-LFS as it is intended for versioning large files.

Git Large File Storage (LFS) replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a remote server like GitHub.com or GitHub Enterprise.

You can look at this good tutorial on git-lfs which will answer most of your follow-up questions.

Answer 17

The easy solution is just Change your internet network temporary for example use your mobile hotspot, and after you did push, you can be back to your current network.

This problem would be happened in pull, push or even clone commands. And the reasons could be your network setting related packet size setting, buffer size and ...

Answer 18

git config --global http.postBuffer 524288000 you can just increase your buffer size it worked for me

Answer 19

for me helped just this

server {
    listen 443 ssl http2 default_server;
    ...
    location / {
         ...
         proxy_request_buffering off;
         ...
    }
}

Answer 20

Ironically, for me it turned out to be bad internet connection - I tried everything above, nothing worked, then I did a speed test and found I had 100+Mb download but only 0.x Mb upload at the time, due to some wifi issues. After I fixed it the problem disappeared.

Answer 21

Using different internet access solved the problem for me, I switched from my main wifi and connect to my phone and it worked.

Answer 22

I solved this annoyng problem by changing my wi-fi DNS on my work laptop.

Answer 23

With me there was issue with my internet and also the large amount of files in my code. I fixed this, Please check your internet speed and also use this.

   git config http.postBuffer 524288000
    git push

Answer 24

Don't forget to add an SSH key to your Github account. That was causing the error for me.

Answer 25

For me I thought that was my internet so I tried with a better internet but the error persists. Until I have found this solution:

Basicaly I had to copy into another branch the files and delete the other and rename the current one. To clean the repo.

git checkout --orphan newBranch
git add -A  # Add all files and commit them
git commit -am "Clean Repo"
git branch -D master  # Deletes the master branch
git branch -m master  # Rename the current branch to master
git push -f origin master  # Force push master branch to github

Answer 26

If you are pushing large files you might get this error just use Git Large File Storage

Answer 27

It could be due to low signal strength. I have pushed heavy files in the open source repositories too and haven't encountered this error. More than the buffer size, it depends largely on the signal strength. You could try pushing it 2 or 3 times more or restart your router, and if it still doesn't work, try the following command:

git config http.postBuffer 524288000
git push

Answer 28

If none of this helps, maybe you could try using ssh to connect to your git repository. That helped me.

If you are using Bitbucket you can add your ssh key to the repository settings and that way you will gain ssh access. On Github I think you should have ssh access by default. Try connecting to the repository using ssh instead of https, you can do that by changing the remote url for your git.

Answer 29

I've tried all the approach but didn't work.

Turns out it was my network problem, just disconnect and then connect your wifi and it will work.

This is the error I was getting.

Answer 30

You really might be pushing data having large size. I was having the same error then I preferred using git LFS and it worked.

Just untrack that specific file (file with huge size) before commit. Use following command.

git rm --cached "<file_name>

Then push remaining files and then use git LFS to upload the file with large size. To know how to upload using git LFS refer this.

Answer 31

I have also faced this. I just switched to another mobile hotspot and it worked for me .

Answer 32

Could be caused by a folder/file having the same name with the branch.

Try:

git push <branch_name> --

If worked, then better rename one of them.

Answer 33

For me this was caused by a forgotten return 444; in my nginx config. The connection termination caused this misleading error message under HTTP 2.0

Answer 34

Following the advice of some people here:

git config http.postBuffer 524288000
git push

Results to an error:

remote: error: See http://git.io/iEPt8g for more information.
remote: error: File public/img/layout/group-photo.psd is 184.91 MB; this exceeds GitHub's file size limit of 100.00 MB
remote: error: GH001: Large files detected. You may want to try Git Large File Storage - https://git-lfs.github.com.

So this is more of a file issue rather than a network connectivity issue in my case. Move the large file out of the project and proceed to commit and push the whole thing.

Answer 35

Also check if you maybe using a VPN, I got the error while using VPN, I decided to turn my VPN off and try again, then it Worked

Answer 36

I live rurally and have mobile broadband, that is based on a very low 4g signal, I get two bars of signal on a good day. I was pushing several files amounting to only 39mb, which is well below github's max file size, I have also pushed much bigger commits on the same repo from this location, so it did not make sense that the file size caused the problems for me. I tried everything mentioned here, changing to HTTP1, and changing postbuffer did not help.

After several hours of head scratching, I restarted my router and was able to push the commit to github.

Hopefully this can help someone out there that also has terrible a internet connection.

Answer 37

Switch to Mobile Internet or Change the Internet Connection. This is happened some time because of network issue.

Answer 38

Surprisingly, I didn't find any answers on this thread that mention simply retrying. I ran into the same error, then simply retried my push and it worked fine. No changing settings or other actions needed.

Answer 39

If your error is related to trying to push large file (I had that error message in my case), run:

git filter-branch -f --index-filter 'git rm --cached --ignore-unmatch {your full path file name}'

https://medium.com/@marcosantonocito/fixing-the-gh001-large-files-detected-you-may-want-to-try-git-large-file-storage-43336b983272

Answer 40

For me this query works : git push --set-upstream origin main

Answer 41

The only issue in this case is Bad Internet Connection and nothing else. I fixed it by switching to better internet connection.

Answer 42

Disconnect from your VPN and try again. That's what solved it for me.

Answer 43

In my case, I changed my password on the server (Gitlab) but not in my local git credentials.