while push code into aws codeCommit getting this error --> repo : RPC failed; curl 56 LibreSSL SSL_read: SSL_ERROR_SYSCALL, errno 54

Question

I create a repo on AWS codecommit over north virginia and then able to clone it on my local using https url. then i add some of my laravel code, commit it and try to push it over the codecommit. then i got this error

iDevOps@swetank01-MacBook-Pro sample-laralab % git push                                      
Enumerating objects: 5379, done.
Counting objects: 100% (5379/5379), done.
Delta compression using up to 4 threads
Compressing objects: 100% (4137/4137), done.
Writing objects: 100% (5379/5379), 296.87 MiB | 300.98 MiB/s, done.
Total 5379 (delta 1004), reused 5371 (delta 1004)
error: RPC failed; curl 56 LibreSSL SSL_read: SSL_ERROR_SYSCALL, errno 54
fatal: the remote end hung up unexpectedly
fatal: the remote end hung up unexpectedly
Everything up-to-date

i even tried creating on other location like on us-east-2. there i got different error like

git clone https://git-codecommit.us-east-2.amazonaws.com/v1/repos/laralab
Cloning into 'laralab'...

repo could not be found

I faced this error first i recently implement same CI/CD pipeline using aws without getting got issue inbetween. Any hint Will be Appreciated

flaxel · Accepted Answer · 2021-04-10 10:59:08Z

0

Related to the GitHub issue it is a problem with your git/curl/libressl or the proxy behind your internet. You can update your git/curl/libressl or try to connect without using proxy.

Otherwise you can also change your git configuration regarding this post:

git config http.postBuffer 524288000

answered Apr 10, 2021 at 10:59

flaxel

4,6874 gold badges22 silver badges32 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

swetank soni Over a year ago

I tried it but still same Error ---> Writing objects: 100% (5379/5379), 296.87 MiB | 279.66 MiB/s, done. Total 5379 (delta 1004), reused 5371 (delta 1004) error: RPC failed; curl 56 LibreSSL SSL_read: SSL_ERROR_SYSCALL, errno 54 fatal: the remote end hung up unexpectedly fatal: the remote end hung up unexpectedly.. >> Is it issue from AWS CodeCommit Side i am also pretty much confusdd becasue it working it my older repo and not working with newly created repos

flaxel Over a year ago

Did you use a vpn connection or a firewall? Can you increase the buffer size to 1048576000? Only as a temporary test, can you disable sslVerify with git config http.sslVerify "false"?

swetank soni Over a year ago

I Tried but not working facing same error as facing earlier, now my am checking for some probability from AWS end may be conf or IAM user

flaxel Over a year ago

Do you want to use the git push to upload many files that are also relatively large? If so, can you try this solution? Can you also try it with ssh?

Raj V · Accepted Answer · 2021-06-10 15:00:39Z

This error is due to the inconsistency in the authentication method and the way the repository is cloned. There are two ways to setup authentication method & cloning a repository.

ssh
https

If you had setup your authentication mode as ssh, then clone the repository with ssh method only. Doing otherwise(cloning with https) will cause this issue. I recently faced this issue and I went through a lot of SO posts

on increasing the global buffer
checking for a larger file size
Re-initialize git

These didn't work for me.

All I had to do was delete and re-clone it with ssh method, as the authentication method setup was ssh. Prior to this, I was cloning with https method, which is wrong. This delete and re-cloning using the same method worked like charm.

Note - Before/After the fix, I was checking in the same piece of code.

swetank soni · Accepted Answer · 2022-07-01 20:41:38Z

0

Works Like a Charm !!!

git config --global credential.UseHttpPath true

answered Jul 1, 2022 at 20:41

swetank soni

292 silver badges16 bronze badges

Collectives™ on Stack Overflow

while push code into aws codeCommit getting this error --> repo : RPC failed; curl 56 LibreSSL SSL_read: SSL_ERROR_SYSCALL, errno 54

3 Answers 3

4 Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

4 Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related