Git push getting failed. error: RPC failed; curl 56 LibreSSL SSL_read: SSL_ERROR_SYSCALL, errno 60

Question

When I am trying to push my code to bitbucket, I am getting this error in terminal.

* LibreSSL SSL_read: SSL_ERROR_SYSCALL, errno 60
* stopped the pause stream!
* Closing connection 2
error: RPC failed; curl 56 LibreSSL SSL_read: SSL_ERROR_SYSCALL, errno 60
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
Everything up-to-date

The solutions which I already tried

1. Increasing git buffer size : git config http.postBuffer 524288000
2. Deleted .git and re-initiated setup
3. Restarted network. (Not a network issue though)
4. Restarted system.
5. Checked code base for files which are greater than 100MB to reset from commit. None of the files exceeds the limit.
6. Added export GIT_TRACE_PACKET=1, export GIT_TRACE=1, export GIT_CURL_VERBOSE=1 to check the verbose logs, None were logged except the above error.

Any help that solves the issue would be appreciated.

Answer 1

It seems that you have a problem in your network infrastructure!

It might be related to your tools or periodic poor network connection or some middle-wares on network those affect on packets!

There is some other rare situations if you won't get answer from rest of this answer, these rare situations need to be considered and analyzed.

Some following actions might help you to pass this situations:

1. Increase git buffer by git config http.postBuffer 524288000
2. Disable SSL validation on git! through: git config http.sslVerify false => (Don't forget IF YOU DIDN'T GET ANSWER from this, "ROLL IT BACK!")
3. Run(Establish) a High-Quality VPN and do git actions through that!

If you find one of these as your solution, please mention that as comment to be useful for others, and If you don't find them useful, describe more about your network quality or tools, to let us analyze and help better.

Answer 2

I was able to push from one repo and not the other, weirdly. None of the solutions I found online worked for me, but restarting my VPN worked for me. Maybe this will help someone.