Bower calls blocked by corporate proxy

bower, proxy

Solution

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

Problem

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?

Original source