Bower calls blocked by corporate proxy

I'm trying to use Bower for a web app, but find myself hitting some sort of proxy issues:

D:\>bower search jquery
bower retry         Request to https://bower.herokuapp.com/packages/search/jquery failed with ECONNRESET, retrying in 1.2s
bower retry         Request to https://bower.herokuapp.com/packages/search/jquery failed with ECONNRESET, retrying in 2.5s
bower retry         Request to https://bower.herokuapp.com/packages/search/jquery failed with ECONNRESET, retrying in 6.8s
bower retry         Request to https://bower.herokuapp.com/packages/search/jquery failed with ECONNRESET, retrying in 15.1s
bower retry         Request to https://bower.herokuapp.com/packages/search/jquery failed with ECONNRESET, retrying in 20.3s
bower ECONNRESET    Request to https://bower.herokuapp.com/packages/search/jquery failed: tunneling socket could not be established, cause=Parse Error

Relevant points:

  • I can browse to https://bower.herokuapp.com/packages/search/jquery and it returns a full json response.
  • I can use git to clone, both using the git:// protocol and http(s).
  • I can use NPM directly without these issues
  • I've tried using Fiddler to determine what's being blocked, but it doesn't detect any calls from the Bower command. I can see calls from NPM commands in Fiddler.
  • I've searched the Bower issues list, seen similar issues, but they either have no solution or it doesn't seem quite the same as mine.

Any ideas?

86866 次浏览
小开

Are you behind a proxy?

Have you set up environment variables HTTP_PROXY and HTTPS_PROXY?

SET HTTP_PROXY=http://yourproxyserver:yourproxyport
SET HTTPS_PROXY=http://yourproxyserver:yourproxyport
小开

Try changing the registry value in your .bowerrc:

{
"registry": "http://bower.herokuapp.com"
}
小开
最佳答案

Thanks @user3259967

This did the job.

I would like to add that if you are behind a proxy that needs to be authenticated, you can add the username/password to your .bowerrc file.

{
"directory": "library",
"registry": "http://bower.herokuapp.com",
"proxy":"http://<USERNAME>:<PASSWORD>@<PROXY_IP>:<PROXY_PORT>/",
"https-proxy":"http://<USERNAME>:<PASSWORD>@<PROXY_IP>:<PROXY_PORT>/"
}

NOTICE the use of http:// in https-proxy

小开

The solution for me is this config .bowerrc

{
"directory": "vendor",
"registry": "http://bower.herokuapp.com",
"proxy": "http://<user>:<pwd>@proxy.host.br:8080",
"https-proxy": "http://<user>:<pwd>@proxy.host.br:8080",
"strict-ssl": false
}

Using the http protocol in https-proxy plus registry entry with http protocol.

Remember to change 8080 port number to whatever is yours proxy server port.

小开

I did not have a .bowerrc file to configure my bower settings. I found the settings living in a file called defaults.js. found under "C:\...\bower\node_modules\bower-config\lib\util\defaults.js"
I hope this helps others:

var defaults = {
'cwd': process.cwd(),
'directory': 'bower_components',
'registry': 'http://bower.herokuapp.com',
'shorthand-resolver': 'git://github.com/\{\{owner}}/\{\{package}}.git',
'tmp': paths.tmp,
'proxy': '<<http://user:pass@proxy:port>>',  // change proxy here or at the top
'https-proxy': '<<http://user:pass@proxy:port>>',  // change proxy here or at the top
'timeout': 30000,
'ca': { search: [] },
'strict-ssl': false,
'user-agent': userAgent,
'color': true,
'interactive': null,
'storage': {
packages: path.join(paths.cache, 'packages'),
links: path.join(paths.data, 'links'),
completion: path.join(paths.data, 'completion'),
registry: path.join(paths.cache, 'registry'),
empty: path.join(paths.data, 'empty')  // Empty dir, used in GIT_TEMPLATE_DIR among others
}
};


module.exports = defaults;

小开

you can try suggest @thebignet into same issue on GitHub

Set proxy, https-proxy and strict-ssl configuration into .bowerrc File :

{
"proxy"       : "http://<host>:<port>",
"https-proxy" : "http://<host>:<port>",
"strict-ssl"  : false
}

But you must run Command from terminal:

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

For Win 7.

What worked for me , are below steps as suggested at this link - read #nanowizard answer.

  1. In .bowerrc file, remove any http_proxy / https_proxy settings that you might have done earlier. This is important. So final content of this file should look like :-

    {
"directory": "app/bower_components"
}

  2. Set environment variables in your pc - http_proxy and https_proxy to your corporate firewall proxy. In case, your corporate proxy requires authentication and if your password contains special characters, convert it to hex form as suggested by this link. As in my case escaping of characters with '\' did not help. Also I had to restart my system.

Note : http_proxy and https_proxy should contain same proxy address as shown below 

http_proxy = http://<user>:<password>@<your company proxy>:<port>
https_proxy= http://<user>:<password>@<your company proxy>:<port>  ->Note no 's' in http://...
小开

I am behind corporate firewall and I have to specify domain name too. None of these answers worked for me. Here is what I did -

  1. Downloaded CNTLM from http://cntlm.sourceforge.net/
  2. Obviously installed it.

  3. Open up cntml.ini and change the following

    Domain your_domain_name

    Username your_domain_username

    Password your_domain_passowrd

    PassLM 1AD35398BE6565DDB5C4EF70C0593492 (uncomment this)

    PassNT 77B9081511704EE852F94227CF48A793 (uncomment this too)

    Proxy http://localhost:8888

  4. Go to services.msc and start the CNTLM Authentication service.

  5. Download Fiddler 4/2 (whatever they call it).
  6. Install this too. This will run in http://localhost:8888
  7. Now whatever program you’re running forward(proxy) it to http://locahost:3128 ( that’s what CNTLM is running.)

In this case specify http.proxy and https.proxy as http://localhost:8888

This will work for other client programs. Just specify proxy as http://localhost:8888

小开 
{
"directory": "library",
"registry": "http://bower.herokuapp.com",
"proxy":"http://<USERNAME>:<PASSWORD>@<PROXY_IP>:<PROXY_PORT>/",
"https-proxy":"http://<USERNAME>:<PASSWORD>@<PROXY_IP>:<PROXY_PORT>/"
}

This code worked for me. I am using Win 7 and chrome and also git bash. Here few things need to be cleared. This takes me huge time to find the actual data regarding the user name, password, proxy IP and Port. I will describe it step by step so that every learners can easily grasp the message:

  1. Create a file in the notepad named .bowerrc in the login folder; You can go there by typing at Start>Run>%UserProfile% and press OK.

  2. Type above code in the .bowerrc file with the following changes:

    Replace <USERNAME> with your internet connection user ID or login ID

    Replace <PASSWORD> with your internet connection password or login password.
    Replace <PROXY_IP> and <PROXY_PORT> with the working proxy IP address and its port number. 

       **Note: There should be no angle brackets.**

  3. Proxy IP should be different than your own IP.

  4. Before using any proxy IP and port you should check it is working by changing your proxy IP and port.

  5. You can go through this link to know the details of proxy settings at description here

  6. From this proxy settings you will get Proxy IP and Port.
  7. Recheck all the input so that all are correct and save and close the file.
  8. Open git bash and change directory to the project file and type command and hit enter, in my case, git bash command:

a@a-PC MINGW32 /d/conFusion

$ bower install

  1. It worked like magic.
小开

In case it helps someone, I had a 'bower blocked by group policy' error.

Solution was to make an exception in CryptoPrevent, a application installed on our company computers to prevent crypto lockers.

小开

For info, in your .bowerrc file you can add a no-proxy attribute. I don't know since when it is supported but it works on bower 1.7.4 and it solve the issue of bower behind a corporate proxy with an internal repository

.bowerrc :

{
"directory": "bower_components",
"proxy": "http://yourProxy:yourPort",
"https-proxy":"http://yourProxy:yourPort",
"no-proxy":"myserver.mydomain.com"
}

Regards

小开 
"strict-ssl": false

in .bowerrc did for me

小开

its work for me to change in .bowerrc file

{
"directory": "client/lib",
"registry": "http://bower.herokuapp.com",
"proxy":"http://192.168.1.205:3228",
"https-proxy":"http://192.168.1.205:3228"
}
  • where client/lib is installation directory where do you want to install
  • and http://192.168.1.205:3228 is your proxy ip with port. corporate proxy can be different according to oraganization.
小开

Please make sure there are no special characters in your proxy password. Convert it to hex. It works for me.

小开

In addition to setting the below proxy in .bowerrc:

{
"directory": "app/bower_components",
"proxy":"http://<user>:<password>@proxy.company.com:<proxy-port>",
"https-proxy":"http://<user>:<password>@proxy.company.com:<proxy-port>",
"http-proxy":"http://<user>:<password>@proxy.company.com:<proxy-port>",
"strict-ssl": false,
"registry": "http://bower.herokuapp.com"
}

I am required to run the following commands to fix the issue:

npm cache clean
bower cache clean
bower install
小开

The registry used in the the other answers is now deprecated. Please update it!

{
"proxy":"http://<user>:<password>@proxy.company.com:<proxy-port>",
"https-proxy":"http://<user>:<password>@proxy.company.com:<proxy-port>",
"registry": "https://registry.bower.io"
}

提交答案