Bower install - failed with ETIMEDOUT

Question

When I run bower install, I get the following error:

Request to https://bower.herokuapp.com/packages/jquery failed with ETIMEDOUT, retrying in 1.8s

But when I run the same URL in the address bar of Chrome, I get the json. I don't know why it fails when I do bower install using Windows 7 command shell. I suspect it has got something to do with my workplace's proxy settings.

Anyone?

Have you tried something like `http_proxy='proxyserver' https_proxy='proxyserver' bower install`? (where proxyserver is your proxy) — Mangled Deutz, Apr 07 '14 at 15:36
@MangledDeutz I tried `set HTTP_PROXY=http://myproxy:8080` and `set HTTPS_PROXY=http://myproxy:8080` and it worked! Post your comment as answer below so that I can accept it! Thank you! :) — AlwaysALearner, Apr 08 '14 at 05:50

score 18 · Answer 1 · answered Nov 11 '15 at 05:07

18

Try edit .bowerrc

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

answered Nov 11 '15 at 05:07

Robert Moon

1,025
10
17

where is this file on mac – rd_ Mar 05 '18 at 10:13

score 14 · Accepted Answer · answered Apr 08 '14 at 08:57

14

Have you tried something like http_proxy='proxyserver' https_proxy='proxyserver' bower install? (where proxyserver is your proxy)

answered Apr 08 '14 at 08:57

Mangled Deutz

11,384
6
39
35

are you setting these values in npm via "npm config set" command? – Roman May 23 '14 at 23:37
2

no, these are environment variables. Try `set HTTP_PROXY=http://myproxy:8080` on your shell (I assume you are on windows?) – Mangled Deutz May 24 '14 at 09:56
Thank you. That did not help me, unfortunately. I had to change the git to use the https instead of git protocol to work behind the proxy. – Roman Jun 05 '14 at 23:51

score 9 · Answer 3 · edited Apr 04 '15 at 11:27

9

Getting error related to proxy when no proxy is configured: May be npm is picking up proxy.

Delete the proxy attribute from npm config and try. Use:

npm config delete proxy

This solved my problem.

edited Apr 04 '15 at 11:27

mins

6,478
12
56
75

answered Apr 04 '15 at 10:40

Vishal Acharya

99
1
2

`npm config delete proxy` worked for me. I was getting the same error. I'm not using a proxy. I tried `npm clean cache` and `bower clean cache` but neither worked for me. Thank you my friend :) – Sparky Aug 24 '15 at 00:41

score 8 · Answer 4 · answered Oct 11 '17 at 13:29

8

You need to set the new registry for bower in .bowerrc:

{
  "registry": "https://registry.bower.io"
}

The old url https://bower.herokuapp.com/ is no more available.

answered Oct 11 '17 at 13:29

Matteo Alessani

10,264
4
40
57

Confirming that this works for me too. If there is already a .bowercc and it has "directory": "wwwroot/lib" in it, just put a comma on that line, and on the next line insert registry. – Jason Roner Jul 12 '18 at 20:22

score 3 · Answer 5 · answered Nov 17 '16 at 14:28

In my case (Win7), this problem was fixed by providing bower with the proxy settings.

As @Robert Moon mentioned in his answer, you can place this settings in the .bowerrc file.

For proxies that require authentication you will need to provide it as follows:

http://domain\username:password@proxyserverurl:port

The back slash is particularly tricky since it needs to be escaped in the .bowerrc file

Example .bowerrc:

{
  "directory": "bower_components",
  "proxy": "http://domain%5Cusername:password@proxyserverurl:port",
  "https-proxy": "http://domain%5Cusername:password@proxyserverurl:port",
  "no-proxy":"localserver.domain.com"
}

The official documentation from Bower that mentions proxy settings:
https://bower.io/docs/config/#bowerrc-specification

score 0 · Answer 6 · answered Oct 23 '17 at 09:40

0

I was also stuck with the same error. The following steps fixed the error for me:

Remove any existing proxy: npm config delete proxy

Then set proxy using: npm config set proxy http://<host>:<port>

You may also need to change the proxy settings for git:

git config --global http.proxy http://<host>:<port>
Now edit the .bowerrc file as described by Robert Moon

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

answered Oct 23 '17 at 09:40

Pransh Tiwari

3,983
1
32
43

it is necessary to reset the PC? Thanks – Diego Mar 16 '18 at 20:12
I didn't need to reset the PC. Just try if it isn't working for you. – Pransh Tiwari Mar 16 '18 at 22:10

score 0 · Answer 7 · answered Jul 16 '21 at 10:58

0

Prod server build bower well, but the develop server does not build, it is stop with ETIMEDOUT. The error went through when I added:

"timeout": 120000

into .bowerrc.

Info from page https://bower.io/docs/config/ helped me.

answered Jul 16 '21 at 10:58

Радогор

21
2

From Review: Hi, this post does not provide an answer to the question. Once you have sufficient [reputation](https://stackoverflow.com/help/whats-reputation) you will be able to [comment on any post](https://stackoverflow.com/help/privileges/comment). Instead, please [provide answers that don't require clarification from the asker](https://meta.stackexchange.com/questions/214173/why-do-i-need-50-reputation-to-comment-what-can-i-do-instead). – sɐunıɔןɐqɐp Jul 18 '21 at 11:37

Bower install - failed with ETIMEDOUT

7 Answers7

Linked