Git / Bower Errors: Exit Code # 128 & Failed connect

Question

I use Bower to install multiple libraries. For demonstration, here I am installing bootstrap. Regardless of the package, I get the following errors:

C:\Scott>bower install bootstrap bower not-cached git://github.com/twbs/bootstrap.git#* bower resolve git://github.com/twbs/bootstrap.git#* bower ECMDERR Failed to execute "git ls-remote --tags --heads git://github .com/twbs/bootstrap.git", exit code of #128 Additional error details: fatal: unable to access 'https://github.com/twbs/bootstrap.git/': Failed connect to github.com:443; No error 

I tried using the following solution to remove the first error - which I found from this search :

 git config --global url."https://".insteadOf git:// 

However, this does not work and does not implement any other solutions found on this page. Looking for a solution for the 2nd error, it seems that setting the username / pwd for the proxy server will solve the problem if you are on the corporate network / behind a firewall. However, I do not use a proxy server, as I am on my home PC / network (Windows 7 x64).

Thank!

EDIT: command window with errors:

Answer 1

Port 22 is blocked on my computer. As soon as I found that I blocked it and opened the port, I was able to run the cmd collector without any problems.

Answer 2

I know this is not a “fix” for the problem, but you can use

git config --global url."https://".insteadOf git://

tell git to use HTTPS instead of git, which developed my installation of npm dependencies.

Answer 3

Instead, run the following command:

  git ls-remote --tags --heads git://github.com/twbs/bootstrap.git 

you should run this command:

  git ls-remote --tags --heads [e-mail]:twbs/bootstrap.git 

or

  git ls-remote --tags --heads https://github.com/twbs/bootstrap.git 

or you can run git ls-remote --tags --heads git://github.com/twbs/bootstrap.git , but you need to do git always use https like this:

  git config --global url."https://".insteadOf git:// 

Link: https://github.com/bower/bower/issues/50

Answer 4

I came across this with my corporate network.

It seemed strange to me because I always used ssh to communicate with git and never had a problem.

I tried https and did not work, so I added proxy settings to git config and everything was fine

 git config --global http.proxy http://proxyuser:[e-mail]:8080 git config --global https.proxy https://proxyuser:[e-mail]:8080 

And making sure it worked

 git config --list 

Answer 5

It seems that azsl1326 did not use bower (git) on port 9418 (git: //), and then told git to use port 22 (https: //). This still failed, but then the opening of port 22 got the desired result.

The most direct solution is to open port 9418. This is the port that uses the git: // protocol.

Answer 6

Go to your application folder and run this command

git config --global url. "https: //" .insteadOf "git: //

"

This should fix your problem.

Answer 7

You may need to generate the ssh key so that you are authenticated with github.

Answer 8

This error is due to the poor configuration of your firewall. You will notice that the other person is trying to contact git through the git:// protocol, not http:// . You must open port 9418 . Add two lines to the iptables configuration:

 iptables -t filter -A INPUT -p tcp --dport 9418 -j ACCEPT iptables -t filter -A OUTPUT -p tcp --dport 9418 -j ACCEPT 

That should do the trick.

Answer 9

Are you behind a firewall?

Git does not display the proxy configuration when it is called, so explicitly set environment variables, for example:

 export HTTP_PROXY=http://username:password@proxyserver:port/ export HTTPS_PROXY=http://username:password@proxyserver:port/ 

If your corporate proxy does not need authentication, just omit the username:password@ bit in the URLs.

It worked for me!

Answer 10

If your village github block, for example. Chinese mainland, then you can create a proxy server, for example. use goagent and gae, then set the proxy address for git, for example.

 git config --global http.proxy 127.0.0.1:8087 

Answer 11

First, you should check if the Visual Studio command recognizes the git command: Tools> Command Prompt

C: \ .... \> git

if this command is not recognized, you must add the git folder to your environment variables

stack overflow

This is what I was missing and helped.

Hope this helps.

Answer 12

I am adding my answer here, as this is one of the closest questions that fit my situation. I tried to install select2, not bootstrap, but the result was the same.

bower install select2 reported that git could not find the directory. Is used

git config --global url. "https: //" .insteadOf git: //

config fix, but this led to a (rephrased) error

I can not use https

My problem was unsatisfactorily resolved, since it involves magic.

I tried to run this in a shell (cmd.exe, windows). I ran the same command and ran it in powershell and it worked. ಠ_ಠ

tl; dr: a combination of https: // and powershell worked for me

Answer 13

I got this error after my antivirus program quarantined the download from github.com. For an unknown reason.

After cleaning these files (exe files) everything worked.

Answer 14

 git config --global url. "https://".insteadOf "git://" 

didn't work for me. So I found this alternative:

Go to the temp folder. (i.e. if you use windows, then C:\Users\{username}\AppData\Roaming\bower\cache\packages ). There you can see several files. Open each one and you will see the url. Change it from git://... to https://... and save all the files.

Now run bower install .

Answer 15

Check your git configuration settings ( git config --global --edit ). In my case, there were a couple of more invalid entries like:

[core]
gitproxy = gitproxy.cmd
["Https: //"]
["Https: //"]
[url "https: //"]

Review them and delete if you no longer need them.

Answer 16

Your keys are wrong. Just add them to github / bitbucket / whatever you use. This is nothing more than a problem with your keys.

Answer 17

However, I do not use a proxy server, as I am on my home computer / network

Had the same problem (getting exit code 128) on my home network and was pretty sure that I did not use a proxy. It turns out that Git saved the proxy server, which I used to log in for some time in the past - after looking in the configs I found it under the tag [http].

I'm new to Git, and I'm not at all sure if these configs are usually easily accessible - I use Tortoise Git since I am not doing anything and I have a GUI for things.

Hope that the “answer” nonetheless helps.

Answer 18

In my case, I had access to the folder where I was at the time of the command! On Windows, I created the folder first on the command line: mkdir "MyFolder", and I had an error. but if I create the folder with the mouse, right click, create the folder, etc. Works great!

Answer 19

If you are authenticating with bitbucket, where I get error 128 and Failed connect. but when using git authentication, the hub is working fine.

Answer 20

I know this is an old question, anyway let me add one more thing.

Sometimes (if you are working in an office or on a private network), the gateway server firewall blocks https requests (port 443) from the command line

 git config --global url."http://".insteadOf "https://" 

Use this to configure git to use http over https for these situations

Answer 21

It worked for me

Copy the libcurl.dll file to the Git installation folder (C: \ Program Files \ Git \ bin \ libcurl.dll). Paste it in the place where git.exe exists (C: \ Program Files \ Git \ libexec \ git -core).

Answer 22

Run these 2 commands to give git access through your system

 eval `ssh-agent` ssh-add ~/.ssh/id_rsa 

These commands assume that you have an ssh key on the remote git server (bitpack / github / other)