Skip to main content
The 2026 Annual Developer Survey is live— take the Survey today!

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

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

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.

enter image description here

Answer*

Draft saved
Draft discarded

Required fields are marked with *

Cancel
3
  • 1
    Your answer could be improved with additional supporting information. Please edit to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers in the help center. Commented May 3, 2022 at 9:40
  • This does not provide an answer to the question. Once you have sufficient reputation you will be able to comment on any post; instead, provide answers that don't require clarification from the asker. - From Review Commented May 8, 2022 at 11:35
  • 1
    Switching from http to ssh fixed the issue for me. The GitHub documentation for setting up ssh was easy to follow. In my case, the issue wasn't due to network reliability. A colleague on the same network could clone without a problem. I also tried a different network on the same laptop, but got the same issue. Setting the depth to 1or changing git configuration settings didn't help. Commented Aug 15, 2024 at 1:29