CODEWITHSUNDEEP
gitazure
Alxandir
Alxandir

Reputation: 3

Azure Web App Git Push Failure (RPC failed; result=56)

I have been developing a web app on Microsoft Azure with a Git repository using Node.js and AngularJS.

It has been deploying successfully for the past few weeks and then today, I have added a small animation to the page using ng-show and @keyframes. When attempting to push these changes to the git, I get the following output:

C:\Users\Alexander\Documents\Azure\AlexH>git push origin master
Counting objects: 13, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (10/10), done.
Writing objects: 100% (13/13), 49.24 KiB | 0 bytes/s, done.
Total 13 (delta 6), reused 10 (delta 3)
efrror: RPC failed; result=56, HTTP code = 0
atal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
Everything up-to-date

I have read that this was due to the HTTP post buffer limit so I have attempted the following, giving no improvement:

git config http.postBuffer 524288000

I have also restarted the web app through the Azure Portal and retried the push, again giving no improvement.

I'd appreciate any help you can provide to resolve this.

Upvotes: 0

Views: 344

Answers (2)

David Ebbo
David Ebbo

Reputation: 43183

Looking at last deployment (commit id starts with 4d00), it seems it was successful. Could it be that for some reason the client disconnected (for some reason), but that the deployment is actually working fine?

Please try going to the deployment list in the portal, so check whether it all looks successful. I suspect it will.

Upvotes: 1

BartBog
BartBog

Reputation: 1979

In a similar post, see Github Push Error: RPC failed; result=22, HTTP code = 413

the solution was to either reconfigure your webserver or to switch protocol (push via ssh instead of https).

You might want to try one of these solutions...

Upvotes: 0

Related Questions