Github Push Error: RPC failed; result=22, HTTP cod

Question

stupid issue with Github going on right now. I have a decent amount of changes (~120MB in size), when I attempt to push, this is what happens:

error: RPC failed; result=22, HTTP code = 413
fatal: The remote end hung up unexpectedly 
fatal: The remote end hung up unexpectedly

I've already done

git config http.postBuffer 524288000, so that doesn't seem to be the issue. What could it be?

Answer 1

I had this error (error: RPC failed; result=22, HTTP code = 413) when I tried to push my initial commit to a new BitBucket repository. The error occurred for me because the BitBucket repo had no master branch. If you are using SourceTree you can create a master branch on the origin by pressing the Git Flow button.

Answer 2

I had the same problem but I was using a reverse proxy.

So I had to set

client_max_body_size 50m; 

inside both configure files :

• on the gitlab nginx web server (as said inside the previous answers)
• but also on the nginx reverse proxy hosted on the dedicated server.

Answer 3

I already had "HTTPS//" in the git URL yet faced this error.

All I did was to add option -u with push and it worked.

git push -u origin master

Answer 4

Was facing the same issue however it got resolved by cleaning up the git repository (Clean untracked files using "git clean").

Answer 5

I figured it out!!! Of course I would right after I hit post!

I had the repo set to use the HTTPS url, I changed it to the SSH address, and everything resumed working flawlessly.

Answer 6

For those who use IIS 7 to host a git http/https endpoint:

You need to increase your uploadReadAheadSize.

Launch Internet Information Services (IIS) Manager

1. Expand the Server field

2. Expand Sites

3. Select the site you want to make the modification for.

4. In the Features section, double click Configuration Editor

5. Under Section select: system.webServer > serverRuntime

6. Modify the uploadReadAheadSize section (The value must be between 0 and 2147483647.)

7. Click Apply

8. Restart the Website