error: RPC failed; curl 56 OpenSSL SSL_read: error:140943FC:SSL routines:ssl3_read_bytes:sslv3 alert bad record mac, errno 0

Question

I use Arch Linux and this problem appears when trying to push on my rip

error: RPC failed; curl 56 OpenSSL SSL_read: error:140943FC:SSL routines:ssl3_read_bytes:sslv3 alert bad record mac, errno 0

this issue when writing

git push origin master

Counting objects: 65, done. Delta compression using up to 4 threads. Compressing objects: 100% (56/56), done. Writing objects: 100% (65/65), 76.27 KiB | 1.00 MiB/s, done. Total 65 (delta 32), reused 0 (delta 0) error: RPC failed; curl 56 OpenSSL SSL_read: error:140943FC:SSL routines:ssl3_read_bytes:sslv3 alert bad record mac, errno 0 fatal: The remote end hung up unexpectedly fatal: The remote end hung up unexpectedly Everything up-to-date

i'm change my buffer size and upgrade git, curl, openssl but doesn't work .

so any help pleas.

Confer

Where are you trying to push? GitHub? GitLab? Bitbucket? Somewhere else? – Proteinase

GitHub .......... – Confer

Not sure how long are you using Git & Github, but I am using it for a very long time and from yesterday I am having exactly the same error. – Mangum

I use it for a very long time too, and I never see this error before...... Git was work fine.... but this error happened suddenly, and it happened with other people with different os's – Confer

Ok in windows it was the outdated Git Credential Manager problem. Updated from here and the error is gone. Probably there is one for Linux as well. – Mangum

Answer 1

So I ran into the same issue and contacted github.com/contact. In the end, they gave the hint that solved it for me. I needed to change the git config to use TLSv1.2 instead of SSLv3:

git config http.sslVersion tlsv1.2

As GitHub support told me, in the beginning, the issue could be related to a change which they deployed a few months ago, that disables support for deprecated legacy TLS and SSH algorithms, including those that were used in older versions of some Git clients. You can find more information and advice here:

https://githubengineering.com/crypto-removal-notice/

Lockman

Although it didn't help me with exactly the same error, there is a tip if you get warning: unsupported ssl version TLSv1.2: using default - type tlsv1.2 in lowercase. – Mangum

git config --global http.sslVersion tlsv1.2 to set it globally. – Estrange

This worked after upgrading Git to version 2.37.3. It didn't work before I did. – Jaymie

If you're not currently in a repo, you'll likely need to add the --global flag after git config or you'll get an error – Lyckman

Answer 2

This is the final answer:

git config --global http.postBuffer 1048576000

Rhianna

Answer 3

Just switch to mobile hotspot and push.

Seton

This worked for me. Probably there is an issue with my home wifi. – Promoter

This solution worked for me, too. Thank you, what a tricky thing – Neocolonialism

I still had to try 2-3 times for large files (90+ MB). It looks to me like it's something on Github side, as I see reports of this (or similar errors that lead to "The remote end hung up unexpectedly") on several stackoverflow threads, for WinXX, Linux, and MacOS. Lots of solutions seem to work, but I think the reality is that so far nothing fixes this 100% yet – Andreeandrei

Answer 4

As R.singh said I changed my internet connection to Mobile hotspot and it worked for me like a magic !

Mouton

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 – Paving

Answer 5

I had a similar issue and solved it by updating Git.
If you're on Windows run Command Prompt as Administrator and execute

git update-git-for-windows

Occident

Answer 6

in my case, these commands work

1. git config http.postBuffer 524288000

2. git push

if git push is not working then use this one

1. git push origin branch-name

Crotty

Answer 7

change your DNS to 0.0.0.0 and push!

Scopolamine

As it’s currently written, your answer is unclear. Please edit to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers in the help center. – Wavell

Answer 8

I turned off VPN and it worked.

Advertisement