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

[Adrian Kimmitt]

git -c diff.mnemonicprefix=false -c core.quotepath=false push -v origin master:master 

Pushing to https://ACCOUNTNAME@bitbucket.org/ACCOUNTNAME/REPONAME.git

POST git-receive-pack (chunked)

error: RPC failed; result=22, HTTP code = 411

fatal: The remote end hung up unexpectedly

fatal: The remote end hung up unexpectedly

Everything up-to-date

Completed with errors, see above

I have been getting this error sporadically today across multiple different repositories. Some were created today,s ome were created months ago. I have committed/pushed to these daily for some time now, and only started getting this error about 5 hours ago. Some other users accessing my repo's have got the same error when committing.

[Adrian Kimmitt · Accepted solution]

*UPDATE* I did not make any changes to the bitbucket repo or my local repo since I posted this initial problem. I now opened up my SVN client, and PUSHED the 5 pending commits I had errors from earlier.... And it worked. Clearly its a problem in bitbuckets backend somewhere.

[njerunjeru]

git config --global http.postBuffer 157286400

solved my problem

[Prashant Mali]

Yes. It works for me too.

[Kiti Chigiri]

try to run the following command

git config http.postBuffer 524288000

see https://confluence.atlassian.com/display/FISHKB/Git+PUSH+results+in+RPC+failed,+result%3D22,+HTTP+code+%3D+411 for more information

[Adrian Kimmitt]

My buffers were already set to these values days ago, before the problem:
size limit (text): 10,240kb
size limit (binary): 102,400kb

*UPDATE* I did not make any changes to the bitbucket repo or my local repo since I posted this initial problem. I now opened up my SVN client, and PUSHED the 5 pending commits I had errors from earlier.... And it worked. Clearly its a problem in bitbuckets backend somewhere.