nvm installation fails on fedora 19 with "Unable to access nvm.git" error

[deepiajay29]

• Operating system and version: Fedora 19 running on Virtual Box

• nvm debug output: nvm debug bash: nvm: command not found...

• nvm ls output:

  ```sh ```

• How did you install nvm? (e.g. install script in readme, Homebrew):

• What steps did you perform? sudo wget -qO- https://raw.githubusercontent.com/creationix/nvm/v0.33.2/install.sh | bash

• What happened? nvm isntallation failed with the following error: => Downloading nvm from git to '/home/sukumad1/.nvm' => Cloning into '/home/sukumad1/.nvm'... fatal: unable to access 'https://github.com/creationix/nvm.git/': Peer reports incompatible or unsupported protocol version. Failed to clone nvm repo. Please report this!

• What did you expect to happen? expected nvm to install correctly

• Is there anything in any of your profile files (.bashrc, .bash_profile, .zshrc, etc) that modifies the PATH?

• If you are having installation issues, or getting "N/A", what does curl -I --compressed -v https://nodejs.org/dist/ print out?
  • About to connect() to nodejs.org port 443 (#0)
• Trying 104.20.23.46...
• Connected to nodejs.org (104.20.23.46) port 443 (#0)
• Initializing NSS with certpath: sql:/etc/pki/nssdb
• CAfile: /etc/pki/tls/certs/ca-bundle.crt CApath: none
• SSL connection using TLS_RSA_WITH_AES_128_CBC_SHA
• Server certificate:
• subject: CN=*.nodejs.org,OU=PositiveSSL Wildcard,OU=Domain Control Validated
• start date: Aug 14 00:00:00 2017 GMT
• expire date: Nov 20 23:59:59 2019 GMT
• common name: *.nodejs.org
• issuer: CN=COMODO RSA Domain Validation Secure Server CA,O=COMODO CA Limited,L=Salford,ST=Greater Manchester,C=GB

  HEAD /dist/ HTTP/1.1 User-Agent: curl/7.29.0 Host: nodejs.org Accept: / Accept-Encoding: deflate, gzip

  < HTTP/1.1 200 OK HTTP/1.1 200 OK < Date: Thu, 13 Jun 2019 05:00:28 GMT Date: Thu, 13 Jun 2019 05:00:28 GMT < Content-Type: text/html Content-Type: text/html < Connection: keep-alive Connection: keep-alive < Set-Cookie: cfduid=d2f9d2d2a458eb04fbb99b1eac5b0d56c1560402028; expires=Fri, 12-Jun-20 05:00:28 GMT; path=/; domain=.nodejs.org; HttpOnly Set-Cookie: cfduid=d2f9d2d2a458eb04fbb99b1eac5b0d56c1560402028; expires=Fri, 12-Jun-20 05:00:28 GMT; path=/; domain=.nodejs.org; HttpOnly < CF-Cache-Status: HIT CF-Cache-Status: HIT < Expires: Thu, 13 Jun 2019 09:00:28 GMT Expires: Thu, 13 Jun 2019 09:00:28 GMT < Cache-Control: public, max-age=14400 Cache-Control: public, max-age=14400 < Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct" Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct" < Vary: Accept-Encoding Vary: Accept-Encoding < Server: cloudflare Server: cloudflare < CF-RAY: 4e618045dd7dd732-SYD CF-RAY: 4e618045dd7dd732-SYD < Content-Encoding: gzip Content-Encoding: gzip

<

• Connection #0 to host nodejs.org left intact

  Note: I have already updated by GIT and also ran the following: yum update -y nss curl libcurl Still not working

[ljharb]

You ran the install script with sudo - that won't do what you expect. One of the whole points of nvm is to not have to use sudo.

What happens if you rerun the installation script as it is in the readme verbatim?

[deepiajay29]

Getting the same error even without sudo

wget -qO- https://raw.githubusercontent.com/creationix/nvm/v0.33.2/install.sh | bash => Downloading nvm from git to '/home/sukumad1/.nvm' => Cloning into '/home/sukumad1/.nvm'... fatal: unable to access 'https://github.com/creationix/nvm.git/': Peer reports incompatible or unsupported protocol version. Failed to clone nvm repo. Please report this!

On Thu, Jun 13, 2019 at 3:38 PM Jordan Harband notifications@github.com wrote:

You ran the install script with sudo - that won't do what you expect. One of the whole points of nvm is to not have to use sudo.

What happens if you rerun the installation script as it is in the readme verbatim?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/nvm-sh/nvm/issues/2064?email_source=notifications&email_token=AMK77UWWT4RIAZE4MAAQO4LP2HMNBA5CNFSM4HXV5CC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXSSEEQ#issuecomment-501555730, or mute the thread https://github.com/notifications/unsubscribe-auth/AMK77USULV6PTDGXNCQJJGLP2HMNBANCNFSM4HXV5CCQ .

[ljharb]

What version of git do you have? Per the readme, nvm requires v1.7.10 or later.

[deepiajay29]

git version 1.8.3.1

On Thu, Jun 13, 2019 at 4:56 PM Jordan Harband notifications@github.com wrote:

What version of git do you have? Per the readme, nvm requires v1.7.10 or later.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/nvm-sh/nvm/issues/2064?email_source=notifications&email_token=AMK77UVOQJBWTU56WJ7PUEDP2HVR5A5CNFSM4HXV5CC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXSWW6Q#issuecomment-501574522, or mute the thread https://github.com/notifications/unsubscribe-auth/AMK77UROEEADVR3I5S37QE3P2HVR5ANCNFSM4HXV5CCQ .

[ljharb]

What happens if you try to git clone the repo directly? if https is unsupported, perhaps your OS is missing OpenSSL?

[deepiajay29]

Can you please let me know how to git clone?

[ljharb]

git clone https://github.com/nvm-sh/nvm.git ~/.nvm

[deepiajay29]

Same error even with git clone: [sukumad1@f19_vm_sukumad1 Downloads]$ git clone https://github.com/nvm-sh/nvm.git ~/.nvm Cloning into '/home/sukumad1/.nvm'... fatal: unable to access 'https://github.com/nvm-sh/nvm.git/': Peer reports incompatible or unsupported protocol version.

[ljharb]

In that case, it’s not a problem with nvm - it’s that your machine is unable to connect to https with git.

Perhaps your ssl certs are out of date, or perhaps your machine is lacking OpenSSL? I’m not sure how to help you from here.