Everything you need to know to resolve the Git Push RPC error

Varun Joshi
The Startup
Published in
4 min readMay 14, 2020

--

And not spend 8 hours browsing the web looking for a solution.

It’s a bright, sunny day & you’re working on some nice UI changes on your project, everything looks great, a few new images, changes across multiple files, business as usual. When you’re done, you proudly commit your changes & push your code to your repository.

BOOM. Disaster strikes.

Disclaimer: These errors can happen on any kind of days, not just bright & sunny.

As you look at the git push output compressing objects & writing them, you wonder if your internet went out because git does not return a confirmation that your changes have been pushed. Git has frozen!

Multiple re-tries to push end with the same result until you decide to let git take its time. After about 45 mins or so, you get a wonderful error message from git stating your push has well, failed.

error: RPC failed; http2 499 curl 16 Error in HTTP2 framing layerfatal: remote hung up unexpectedly

Huh, that’s rude. A quick Google search reveals you are not the only one with the error, however a lot of them got a different error code.

The frustration when you cannot figure out what went wrong.

There are a few solutions suggested on StackOverflow, which have worked for a lot…

--

--

Varun Joshi
The Startup

Software engineer who loves writing tech articles. I simplify complex concepts and share insights to connect developers with non-technical audiences.