I am trying to upload my files up to my repository but i kept getting this error - “error: RPC failed; curl 56 LibreSSL SSL_read: error:1404C3FC:SSL routines:ST_OK:sslv3 alert bad record mac, errno 0”
This is like my 30th so far…I can’t even solve this issue after several different attempts of solutions.
Do you have a system proxy set?
I have a zero idea what you just said. I’m a newbie with dev life. I tried several solutions that existed on google search but nothing pan out.
Are you working on Windows or Linux?
It is Mac OSCatalina.
Enumerating objects: 6, done.
Counting objects: 100% (6/6), done.
Delta compression using up to 8 threads
Compressing objects: 100% (4/4), done.
Writing objects: 100% (4/4), 180.74 KiB | 36.15 MiB/s, done.
Total 4 (delta 1), reused 0 (delta 0), pack-reused 0
error: RPC failed; curl 56 LibreSSL SSL_read: error:1404C3FC:SSL routines:ST_OK: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
Same issue for just one jpg…
If they’re large files and you don’t have LFS enabled that might be the problem.
Okay, let try that solution. I’m fed up with this error.
Apparently, there were a few occurrences here…Apparently, I wasn’t the current root administrator, lfs wasn’t up to the date, and homebrew needs an update. Then issue persistent until I add git lfs install inside my error-originated directory. Apparently, it works now…I am not having high hope just yet…I would bet it might come back in a few weeks.
I will let you know as this issue is plausible for now. Help me understand why GitHub warning about 100 MB limitation but not umm 174,490 bytes jpg picture upload issue…?
Back to square one…
I am having the same problem after updated to new macOS. I am not sure what is the error and not able to find correct answers. Any help will be great appriciate.
To be honest with you…I hit a dead end with this. However, after two or three weeks…it just has gone like the wind. Just like that with no solution. During that time, I tried to use LFS, but it was a totally bad idea with img because it renders them to be failed because of link scrambler. At this moment, I would recommend you take a look at your SSL portion cause it is all weird in there. Try to update your sslv3 or tslv something. It may give you some headway but no promises here. I do acknowledge your pains and frustrations…
Hi,
Thank you for your prompt reply. There should be some logical explanation; I can not accept or leave my changes to local branches for a long. I must push these changes to the remote so that I can collaborate with others. Anti-virus on MacOS blocking traffic. It could be anything, but I am still not convinced and trying to rule out all the possible causes.
I am suspecting a few things here, MacOS updated, git releases (git-SCM) and not enough testing done. Also, it could be a multiple users account on the same machine with credential stores.
On other extremes, It could be a specific edge case(i.e. in my case Ionic CLI)
Steps to reproduce are simple.
View error message
Enumerating objects: 52 done.
Counting objects: 100% (52/52), done.
Delta compression using up to 8 threads
Compressing objects: 100% (48/48), done.
Writing objects: 100% (51/51), 148.63 KiB | 6.19 MiB/s, done.
Total 51 (delta 2), reused 0 (delta 0), pack-reused 0
remote: fatal: early EOF
error: RPC failed; curl 18 transfer closed with outstanding read data remaining
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
Everything up-to-date
from the log file
git -c credential.helper= -c protocol.version=2 push origin develop:develop --progress exited with an unexpected code: 1.So this is a bit of unusual for me.
Let us see if I create a local repository first and then push to remote (non existing on my GitHub account and create from the start).
Here is a fresh start
Steps to reproduce
------ git log from VSCode
Looking for git in: /usr/local/bin/git
Using git 2.29.2 from /usr/local/bin/git
git rev-parse --git-dir
Open repository: /Users/rlodhiya/Desktop/projects/ionicfinance/ionictesting
git fetch
git status -z -u
git symbolic-ref --short HEAD
git rev-parse master
Fatal: ambiguous argument ‘master’: unknown revision or path not in the working tree.
Use ‘–’ to separate paths from revisions, like this:
‘git […] – […]’
git for-each-ref --sort -committerdate --format %(refname) %(objectname)
git remote --verbose
git config --get commit.template
git status -z -u
git symbolic-ref --short HEAD
git rev-parse master
Fatal: ambiguous argument ‘master’: unknown revision or path not in the working tree.
Use ‘–’ to separate paths from revisions, like this:
‘git […] – […]’
git for-each-ref --sort -committerdate --format %(refname) %(objectname)
git remote --verbose
git config --get commit.template
git check-ignore -v -z --stdin
git status -z -u
git symbolic-ref --short HEAD
git rev-parse master
git rev-parse --symbolic-full-name master@{u}
fatal: no upstream configured for branch ‘master.’
git for-each-ref --sort -committerdate --format %(refname) %(objectname)
git remote --verbose
git config --get commit.template
git checkout -q master
git status -z -u
git symbolic-ref --short HEAD
git rev-parse master
git rev-parse --symbolic-full-name master@{u}
fatal: no upstream configured for branch ‘master.’
git for-each-ref --sort -committerdate --format %(refname) %(objectname)
git remote --verbose
git config --get commit.template
git symbolic-ref --short HEAD
git remote add origin https://github.com/USERNAME/ionictesting.git
git status -z -u
git symbolic-ref --short HEAD
git rev-parse master
git rev-parse --symbolic-full-name master@{u}
fatal: no upstream configured for branch ‘master.’
git for-each-ref --sort -committerdate --format %(refname) %(objectname)
git remote --verbose
git config --get commit.template
git push -u origin master
remote: fatal: early EOF
error: RPC failed; curl 18 transfer closed with outstanding read data remaining
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
Everything up-to-date
To rule out configuration or anything else.
I created one more local repository and published successfully to Github. Now, this is really a strange one but let me see.
Really bizarre but I am running out of options (It is a latest ionic CLI - FYI)
I hope someone must have a similar problem in the entire universe and may share some insight here.
Oh Jesus…during my struggle and I only found two potential solutions. They weren’t helpful because they just a few steps and nothing works. I hope someone else will chip in. They were about SSLv3 and something about large files.
It is possible that it has something to do with SSLv3. I am not sure. As mentioned it worked for fewer changes (ie readme.md file committed and pushed to the remote repository without any problem.)
Since I have updated to new version of Mac OS, I am facing this issue. It is bit Odd one but log is not helpful and other google results are not giving me any further clues.
Maybe need to refresh everything and start fresh. 
Could be but my issue affected Github at first then it spread to a few other apps and browsers. They react to the same issue as your terminal to Github. It was weird…You can try to check your keychain cause it has something up with upload or calling a connection somehow fuzed out.
I had same issue when using GitHub deskktop against a GitLab instance in a Google Cloud virtual machine.
So i got the http URL of the repository in repository settings as well as setting repository/repository settings/remote and repository/repository settings/git for appropiate local settings regarding repository URL, user name and email. I checke file/options/git is coherent as well.
Then I fetched, then I included a change in repository, commited and when I push, I get that error.
If I do any pull it works.
I checked i was able to push from an Ubuntu VM with git command line and it worked!
I also removed credentials from windows credential manager and reinstalled git and github desktop but nothing worked.
Believe me, I really want to help you with this. It is ridiculous…there’s no solid solution at all. LTS was bullshit and just adding another error on my plate. Don’t try the LTS solution. Mine just stopped giving out that error at one day and back to normal. It sucks…I almost had to buy a new laptop or something. I tried to reset the whole operation software etc…nothing works.
