6

I have been using git for a while with no problems, then suddenly it started throwing this error when using git push:

error: gnutls_handshake() failed: A TLS packet with unexpected length was received. while accessing ... fatal: HTTP request failed

It was working fine, then suddenly it stopped.

What is the problem?

Thanks

Damien
  • 1,161
  • 2
  • 19
  • 31
Wahtever
  • 3,597
  • 10
  • 44
  • 79
  • 1
    Take a look here: http://askubuntu.com/questions/186847/error-gnutls-handshake-falied – niculare Mar 27 '13 at 17:56
  • @niculare - i am getting this error `dpkg-source: error: cannot open git_1.7.9.5-1.dsc: No such file or directory` on this line `sudo dpkg-source -x git_1.7.9.5-1.dsc` – Wahtever Mar 27 '13 at 18:06
  • check if the file `git_1.7.9.5-1.dsc` is on the current directory. If not, then maybe some previous commands failed. – niculare Mar 27 '13 at 18:14

5 Answers5

3

It seems there is a problem with the gnutls package. As a workaround, you can try to compile git with openssl. More info on how to accomplish this you can find here.

Community
  • 1
  • 1
niculare
  • 3,629
  • 1
  • 25
  • 39
1

The linked discussion on askubuntu references a version number for git that may not match up with your own. Instead of these two lines:

sudo dpkg-source -x git_1.7.9.5-1.dsc
cd git_1.7.9.5 8.

you need to account for the version of git you're using. In my case, it was 1.8.xxxxx.

sudo dpkg-source -x git_<git-version-number>.dsc
cd git_<git-version-number>

An easy way to get around this is to just copy the first part of the command and then hit Tab to autocomplete. This may not work perfectly if you have recompiled before.

cardonator
  • 386
  • 2
  • 9
1

In my case same error was caused by completely different thing.

Debian was upgraded from Wheezy to Jessie, and thus apache was upgraded 2.2.22 to 2.4.10. git was trying to push to https://www.example.com and it stopped working with error: gnutls_handshake() failed: A TLS packet with unexpected length was received

Turns out, www.example.com was resolving to both IPv4 and IPv6 addresses, and apache config was having <Virtualhost x.y.w.z:443> IPv4 address only. Changing that to <Virtualhost _default_:443> fixed the problem.

(just so if it helps somebody else with same problem... only found it after the tedious recompile of git with openssl didn't change anything at all)

Matija Nalis
  • 678
  • 1
  • 17
  • 30
1

This answer might help. I was surprised that the problems are nowhere to be linked together although the question is old.

Just to be sure the usefull info won't get lost, I copy a brief solution from the question:

hostname=XXX
port=443
trust_cert_file_location=`curl-config --ca`

sudo bash -c "echo -n | openssl s_client -showcerts -connect $hostname:$port 2>/dev/null  | sed -ne '/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p' >> $trust_cert_file_location"
StSav012
  • 776
  • 5
  • 15
1

I have also faced the same issue which was fixed later by disabling my Kaspersky antivirus in my local machine. I hope this may be helpful to others. error report and solution

Ragubathi U
  • 321
  • 2
  • 3
  • 18