NodeRed in Home Assistant no longer can install pallets or update, seems to be offline. npm ERR! network ‘proxy’ config is set properly

Third party integrations Node-RED
1

I have Node Red Plugin v14 (or 3.0.2) installed in Home Assistant (Home Assistant 2022.12.8 Supervisor 2022.12.1 Operating System 9.4 Frontend 20221213.1 - latest on a pi400). I first noticed when my telegram pallet stopped sending or receiving messages that something was amiss. I seem also no longer be able to update any pallets, for example:

2022-12-30T12:54:32.859Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict [email protected]
2022-12-30T12:54:35.252Z [err] npm WARN config production Use `--omit=dev` instead.
2022-12-30T13:02:16.599Z [err] npm
2022-12-30T13:02:16.599Z [err]  ERR! code ETIMEDOUT
2022-12-30T13:02:16.600Z [err] npm 
2022-12-30T13:02:16.600Z [err] ERR!
2022-12-30T13:02:16.601Z [err]  syscall connect
2022-12-30T13:02:16.601Z [err] npm ERR!
2022-12-30T13:02:16.601Z [err]  
2022-12-30T13:02:16.602Z [err] errno
2022-12-30T13:02:16.602Z [err]  ETIMEDOUT
2022-12-30T13:02:16.612Z [err] npm ERR! network
2022-12-30T13:02:16.612Z [err]  request to https://registry.npmjs.org/node-red-contrib-telegrambot failed, reason: connect ETIMEDOUT 2606:4700::6810:1023:443
2022-12-30T13:02:16.612Z [err] npm ERR! network
2022-12-30T13:02:16.613Z [err]  This is a problem related to network connectivity.
2022-12-30T13:02:16.613Z [err] npm ERR! network In most cases you are behind a proxy or have bad network settings.
2022-12-30T13:02:16.613Z [err] npm 
2022-12-30T13:02:16.613Z [err] ERR! network 
2022-12-30T13:02:16.613Z [err] npm ERR!
2022-12-30T13:02:16.613Z [err]  
2022-12-30T13:02:16.614Z [err] network If you are behind a proxy, please make sure that the
2022-12-30T13:02:16.614Z [err] npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
2022-12-30T13:02:16.621Z [err] 
2022-12-30T13:02:16.621Z [err] npm ERR!
2022-12-30T13:02:16.621Z [err]  A complete log of this run can be found in:
2022-12-30T13:02:16.621Z [err] npm ERR!     /root/.npm/_logs/2022-12-30T12_54_35_018Z-debug-0.log
2022-12-30T13:02:16.646Z rc=1

I tried, to reinstall the node red plugin in Home Assistant but that did not do the trick. Automations still work. thanks for any help

2

I had this issue and found by going into Home Assistant\Settings\System\Network\Configure network interfaces and disable IPv6, save, restart Home Assistant, everything started working again. Hope this helps.

2 Likes
3

I have the same problem with not being able to update any nodes in pallets in Node-Red.

Were you able to find a solution for this issue?
I have tried to disabling IPv6 and also starting Node-Red in safe mode but still can’t update any nodes in pallets. I have all the latest updates in Home Assistant as of today, but noticed this problem for at least a couple of months. I haven’t been able to find a solution.
Thanks if anybody has any susuggestions.

4

Disabling IPV6 in Home Assistant then restarting Home Assistant worked for me!! Thank you for the feedback!!

5

The same here – disabling IPv6 fixed this issue – many thanks for the clue! Just wondering whether HA would need IPv6 for some other purpose…

6

+1. Disabling IPv6 fixed this issue. Many thanks!

7

I run into this problem but with another package, turned out that the problem was nodered, basically I had to upgrade to 3.1.0 for it to start working. I think newer packages are not compatible with old versions of nodered.
I’ts not relevant for the given question but I guess other with the same problem will endup here as I did.

8

in my case disabling IP6 did not solve the problem. my nodered servers on raspberry pi and my pc were behind the enterprise network router . i enabled zero tire on HA and connect to the vpn. Then I disconnect my pc from enterprises company wifi and connected to HA via my personal wifi hotspot with zero tire. then this issue disappeared. I think connecting some nodred data base on the internet was blocked by company wifi. if anyone has this issue try to change internet connection.