Home Assistant Community

Cant Install New Nodes

#1

Hey guys my pi finally crapped out for the last time! I’ve upgraded to a NUC running ProxMox which in turn runs HASSIO.
The problem I am having is I’m trying to import my flows and it complains that they (2 of them) are missing. No problem. Go to manage palette find the node I want and click install. (This worked no problems on the little pi) The NUC however throws this error.


2019-04-17T08:52:13.427Z Install : node-red-contrib-schedex 1.5.1

2019-04-17T08:52:13.558Z npm install --no-audit --no-update-notifier --save --save-prefix="~" --production [email protected]
2019-04-17T08:52:21.214Z [err] npm
2019-04-17T08:52:21.215Z [err] ERR! code EAI_AGAIN
2019-04-17T08:52:21.215Z [err] npm
2019-04-17T08:52:21.216Z [err] ERR! errno
2019-04-17T08:52:21.216Z [err] EAI_AGAIN
2019-04-17T08:52:21.219Z [err] npm
2019-04-17T08:52:21.220Z [err] ERR! request to https://registry.npmjs.org/node-red-contrib-schedex failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org registry.npmjs.org:443
2019-04-17T08:52:21.234Z [err]
2019-04-17T08:52:21.235Z [err] npm ERR!
2019-04-17T08:52:21.235Z [err] A complete log of this run can be found in:
2019-04-17T08:52:21.235Z [err] npm ERR!
2019-04-17T08:52:21.235Z [err] /root/.npm/_logs/2019-04-17T08_52_21_223Z-debug.log
2019-04-17T08:52:21.243Z rc=1

Any help? The single post I can find on the node-red forums says it a DNS issue, but I’m not bright enough to work it out.

#2

As VM or alongside PVE? you should leave proxmox pristine, and use a guest VM to run homeassistant or even an LXC if you’'re not gonna pass hardware.

Try basic networking first ping the gateway, then 8.8.8.8 finally ping google.com

If the last one fails is a DNS issue, if no replies come back from 8.8.8.8 then you have routing network problems (no internet)

#3

Yeahs its a VM as I use a dongle for zigbee. Do i ssh into HASSIO and ping?

#4

yeah, I personally don’t use hassio but give it a try. Proxmox network connectivity is ok?

#5

So just installed the ssh addon pinged google 8.8.8.8 and it pinged back. Yes the network health is good

#6

What about ping google.com?

#7

It appears to be OK.
(Thanks for taking the time to help)

#8

Looks like then docker network is failing to resolve
Take a look here

#9

Can I install the 2 nodes I require manually??
That looks above my paygrade :slight_smile:

#10

Don’t think so, can’t imagine trying to install node.js packages manually by getting dependencies one by one.

#11

Grief… Its never easy :frowning:
Thanks again

#12

I just get a lot of this in the node-red addon log

17/Apr/2019:20:01:53 +1000] 200 192.168.1.101, 172.30.32.1(172.30.32.2) GET /icons/node-red-node-suncalc/sun.png HTTP/1.1 (Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36)
[17/Apr/2019:20:01:53 +1000] 200 192.168.1.101, 172.30.32.1(172.30.32.2) GET /icons/node-red-contrib-actionflows/actionflows.png HTTP/1.1 (Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36)
[17/Apr/2019:20:01:53 +1000] 200 192.168.1.101, 172.30.32.1(172.30.32.2) GET /icons/node-red/rpi.png HTTP/1.1 (Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36)
[17/Apr/2019:20:01:53 +1000] 200 192.168.1.101, 172.30.32.1(172.30.32.2) GET /red/images/icons/node-error.png HTTP/1.1 (Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36)
[17/Apr/2019:20:01:53 +1000] 200 192.168.1.101, 172.30.32.1(172.30.32.2) GET /icons/node-red-contrib-alexa-home-skill/alexa.png HTTP/1.1 (Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36)
[17/Apr/2019:20:01:53 +1000] 200 192.168.1.101, 172.30.32.1(172.30.32.2) GET /icons/node-red-contrib-modbus/modbus.png HTTP/1.1 (Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36)
[17/Apr/2019:20:01:53 +1000] 200 192.168.1.101, 172.30.32.1(172.30.32.2) GET /red/images/icons/node-changed.png HTTP/1.1 (Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36)

#13

I can only add nodes in Chrome, Not in firefox. Maybe you have the same issue.

#14

I tried but no good. Im leaning towards a network issue. When I start the addon the logs report
[21:35:33] ERROR: Something went wrong contacting the HIBP API
[21:35:33] WARNING: Could not check password, assuming it is safe.
curl: (6) Could not resolve host: api.pwnedpasswords.com

Is there something im missing in proxmox? Sorry Im a noob with PM

#15

vmbr0 should be a bridge connecting your physical adapter to a vm switch, so you should be using vmbr0 (doesn’t apply to more elaborate network configs), and you should not be natting the VM.

#16

I have not changed any settings for the network side, as everything else seemed to work.

Im stuck. I might just wipe the lot and try a new approach.

#17

What’s your VM configuration? You should be using virtio network and disk types for best performance

#18

Capture

Sorry Im a ProxMox/ noob. Ive only been using linux for a few months (ubuntu)

#19

Quick update (Ive been on holidays). I got back today and flashed straight Hass.io onto the NUC SSD.
I am seeing the exact same errors and cannot add new nodes. Im stumped.