Problem installing an npm packet

[gtas93@hotmail.es]

Hello guys, recently, I default-reseted my Multitech Conduit, and no matter what Firmware version I try to use, I keep getting this problem when it comes to installing the node-red-contrib-mqttssl node.

The log looks like this

0 info it worked if it ends with ok
1 verbose cli [ 'node', '/usr/bin/npm', 'install', 'node-red-contrib-mqttssl' ]
2 info using npm@1.4.28
3 info using node@v0.10.40
4 warn package.json mts-gpio@ No description
5 warn package.json mts-gpio@ No repository field.
6 warn package.json mts-gpio@ No README data
7 warn package.json mts-mcard@ No description
8 warn package.json mts-mcard@ No repository field.
9 warn package.json mts-mcard@ No README data
10 warn package.json mts-serial@ No description
11 warn package.json mts-serial@ No repository field.
12 warn package.json mts-serial@ No README data
13 verbose readDependencies using package.json deps
14 verbose cache add [ 'node-red-contrib-mqttssl', null ]
15 verbose cache add name=undefined spec="node-red-contrib-mqttssl" args=["node-red-contrib-mqttssl",null]
16 verbose parsed url { protocol: null,
16 verbose parsed url   slashes: null,
16 verbose parsed url   auth: null,
16 verbose parsed url   host: null,
16 verbose parsed url   port: null,
16 verbose parsed url   hostname: null,
16 verbose parsed url   hash: null,
16 verbose parsed url   search: null,
16 verbose parsed url   query: null,
16 verbose parsed url   pathname: 'node-red-contrib-mqttssl',
16 verbose parsed url   path: 'node-red-contrib-mqttssl',
16 verbose parsed url   href: 'node-red-contrib-mqttssl' }
17 silly lockFile 4821d294-node-red-contrib-mqttssl node-red-contrib-mqttssl
18 verbose lock node-red-contrib-mqttssl /home/root/.npm/4821d294-node-red-contrib-mqttssl.lock
19 silly lockFile 4821d294-node-red-contrib-mqttssl node-red-contrib-mqttssl
20 silly lockFile 4821d294-node-red-contrib-mqttssl node-red-contrib-mqttssl
21 verbose addNamed [ 'node-red-contrib-mqttssl', '' ]
22 verbose addNamed [ null, '*' ]
23 silly lockFile 74ae5b3e-node-red-contrib-mqttssl node-red-contrib-mqttssl@
24 verbose lock node-red-contrib-mqttssl@ /home/root/.npm/74ae5b3e-node-red-contrib-mqttssl.lock
25 silly addNameRange { name: 'node-red-contrib-mqttssl', range: '*', hasData: false }
26 verbose request where is /node-red-contrib-mqttssl
27 verbose request registry https://registry.npmjs.org/
28 verbose request id 7de5e795bce2599d
29 verbose url raw /node-red-contrib-mqttssl
30 verbose url resolving [ 'https://registry.npmjs.org/', './node-red-contrib-mqttssl' ]
31 verbose url resolved https://registry.npmjs.org/node-red-contrib-mqttssl
32 verbose request where is https://registry.npmjs.org/node-red-contrib-mqttssl
33 info trying registry request attempt 1 at 10:58:17
34 http GET https://registry.npmjs.org/node-red-contrib-mqttssl
35 info retry will retry, error on last attempt: Error: tunneling socket could not be established, cause=connect ECONNREFUSED
36 info trying registry request attempt 2 at 10:58:29
37 http GET https://registry.npmjs.org/node-red-contrib-mqttssl
38 info retry will retry, error on last attempt: Error: tunneling socket could not be established, cause=connect ECONNREFUSED
39 info trying registry request attempt 3 at 10:59:30
40 http GET https://registry.npmjs.org/node-red-contrib-mqttssl
41 silly lockFile 74ae5b3e-node-red-contrib-mqttssl node-red-contrib-mqttssl@
42 silly lockFile 74ae5b3e-node-red-contrib-mqttssl node-red-contrib-mqttssl@
43 error network tunneling socket could not be established, cause=connect ECONNREFUSED
43 error network This is most likely not a problem with npm itself
43 error network and is related to network connectivity.
43 error network In most cases you are behind a proxy or have bad network settings.
43 error network
43 error network If you are behind a proxy, please make sure that the
43 error network 'proxy' config is set properly.  See: 'npm help config'
44 error System Linux 3.12.27r13
45 error command "node" "/usr/bin/npm" "install" "node-red-contrib-mqttssl"
46 error cwd /opt/node-red/nodes
47 error node -v v0.10.40
48 error npm -v 1.4.28
49 error code ECONNRESET
50 verbose exit [ 1, true ]

I have tried hard-setting the proxy by:

npm config set proxy http://”proxynameof my organization”.es:8080
npm config set https-proxy http://”proxynameof my organization”.es:8080

hard setting the gateway…and many ways more, does anynbody know what could be going on here?

Thanks in advance

• This topic was modified 5 years, 3 months ago by gtas93@hotmail.es.
• This topic was modified 5 years, 3 months ago by gtas93@hotmail.es.

[Author]

Posts