2

I've just logged onto our Prod box (Centos) after a long break, and I can't do git pull for some reason.

There seems to be a local problem with this clone of the repo, because I can clone and pull the same repo using the same credentials on other machines (that never had a clone of this repo before)

The command-line message is:

[root@ft41 project_folder]# git pull
Password: 
error:  while accessing https://<myusername>@bitbucket.org/<myproject>/<myrepo>.git/info/refs

fatal: HTTP request failed

The parts in angle-brackets have been redacted by me. Is this info/refs the usual URL for this request? Could something in the local clone be corrupted and causing this?

If it's helpful:

[root@ft41 project_folder]# git status
# On branch master
nothing added to commit

Please note - I have done git pull from this pc/directory successfully many times in the past. It does support HTTPS protocol.

Black
  • 5,023
  • 6
  • 63
  • 92

2 Answers2

7

That could be because of the very recent disabling of TLSv1 and TLSv1.1 done by BitBucket (GitHub had done that in Feb. 2018)

As mentioned here, do upgrade nss, curl and libcurl (see here for an example of curl upgrade on CentOS).

sudo yum update -y nss curl libcurl
VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
  • 1
    it worked! If anyone has this issue try `sudo yum update -y nss curl libcurl` Saved you a click ;) – Black Dec 05 '18 at 23:50
  • i am facing the same issue in Rhel6.9 but i am unable to update nss curl libcurl. any idea? – user11668570 Jan 21 '20 at 08:22
  • @user11668570 Simply download the rpms for [nss](https://centos.pkgs.org/6/centos-updates-x86_64/nss-3.44.0-7.el6_10.i686.rpm.html), [curl](https://centos.pkgs.org/6/centos-x86_64/curl-7.19.7-53.el6_9.x86_64.rpm.html) and [libcurl](https://centos.pkgs.org/6/centos-x86_64/libcurl-7.19.7-53.el6_9.x86_64.rpm.html) in `/home//mycurl` (any path you want). Use `rpm2cpio | cpio -idmv` to unzip them, and add `/home//mycurl/bin` to your `PATH`. Add `export LD_LIBRARY_PATH=/home//mycurl/usr/lib64`. – VonC Jan 21 '20 at 08:36
0

Also may happen when using outdated git CLI. Trying the same commands on more recent version helped me to resolve the issue.

RAM237
  • 903
  • 11
  • 17