Error update or install nodes on Home Assistant supervised OS


Sorry for my english.

I have the problem that it gives me an error when I install new nodes or when I update the existing ones. I've been looking for a solution for 15 days, but due to bad luck or lack of knowledge I can't find anything.

My configuration is:

Raspberry Pi 4B with Home Assistant in supervisor mode installed as primary operating system (not docker mode)

Could anyone help me?.

The log that I get when I try to install/update nodes is the following:

2023-01-28T09:47:33.915Z Install : node-red-contrib-home-assistant-websocket 0.48.0

2023-01-28T09:47:26.479Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict node-red -contrib-home-assistant-websocket@0.48.0
2023-01-28T09:47:28.235Z [err] npm
2023-01-28T09:47:28.237Z [err] WARN
2023-01-28T09:47:28.238Z [err] config production Use --omit=dev instead.
2023-01-28T09:48:40.465Z [err] npm
2023-01-28T09:48:40.465Z [err] ERR! code EACCES
2023-01-28T09:48:40.466Z [err] npm
2023-01-28T09:48:40.466Z [err] ERR!
2023-01-28T09:48:40.467Z [err] syscall connect
2023-01-28T09:48:40.467Z [err] npm ERR!
2023-01-28T09:48:40.467Z [err]
2023-01-28T09:48:40.468Z [err] errno EACCES
2023-01-28T09:48:40.484Z [err] npm ERR!
2023-01-28T09:48:40.485Z [err] FetchError: request to failed, reason: connect EACCES 2606:4700::6810 :1 to 23:443
2023-01-28T09:48:40.485Z [err] npm ERR! at ClientRequest. (/usr/lib/node_modules/npm/node_modules/minipass-fetch/lib/index.js:130:14)
2023-01-28T09:48:40.485Z [err] npm ERR! at ClientRequest.emit (node:events:513:28)
2023-01-28T09:48:40.485Z [err] npm ERR!
2023-01-28T09:48:40.485Z [err] at TLSSocket.socketErrorListener (node:_http_client:494:9)
2023-01-28T09:48:40.485Z [err] npm ERR! at TLSSocket.emit (node:events:525:35)
2023-01-28T09:48:40.485Z [err] npm ERR!
2023-01-28T09:48:40.486Z [err] at emitErrorNT (node:internal/streams/destroy:151:8)
2023-01-28T09:48:40.486Z [err] npm ERR!
2023-01-28T09:48:40.486Z [err] at emitErrorCloseNT (node:internal/streams/destroy:116:3)
2023-01-28T09:48:40.486Z [err] npm ERR! at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
2023-01-28T09:48:40.486Z [err] npm ERR! FetchError: request to failed, reason: connect EACCES 2606:4700::6810:1a23:443
2023-01-28T09:48:40.486Z [err] npm ERR!
2023-01-28T09:48:40.486Z [err] at ClientRequest. (/usr/lib/node_modules/npm/node_modules/minipass-fetch/lib/index.js:130:14)
2023-01-28T09:48:40.486Z [err] npm ERR! at ClientRequest.emit (node:events:513:28)
2023-01-28T09:48:40.486Z [err] npm ERR! at TLSSocket.socketErrorListener (node:_http_client:494:9)
2023-01-28T09:48:40.486Z [err] npm ERR! at TLSSocket.emit (node:events:525:35)
2023-01-28T09:48:40.486Z [err] npm ERR! at emitErrorNT (node:internal/streams/destroy:151:8)
2023-01-28T09:48:40.486Z [err] npm
2023-01-28T09:48:40.487Z [err] ERR! at emitErrorCloseNT (node:internal/streams/destroy:116:3)
2023-01-28T09:48:40.487Z [err] npm ERR! at process.processTicksAndRejections(node:internal/process/task_queues:82:21) {
2023-01-28T09:48:40.487Z [err] npm ERR! code: 'EACCES',
2023-01-28T09:48:40.487Z [err] npm ERR!
2023-01-28T09:48:40.487Z [err] errno: 'EACCES',
2023-01-28T09:48:40.487Z [err] npm ERR! syscall: 'connect',
2023-01-28T09:48:40.487Z [err] npm ERR!
2023-01-28T09:48:40.487Z [err] address: '2606:4700::6810:1a23',
2023-01-28T09:48:40.487Z [err] npm ERR! port: 443,
2023-01-28T09:48:40.487Z [err] npm
2023-01-28T09:48:40.487Z [err] ERR! type: 'system',
2023-01-28T09:48:40.487Z [err] npm ERR! requiredBy: '.'
2023-01-28T09:48:40.487Z [err] npm
2023-01-28T09:48:40.487Z [err] ERR! }
2023-01-28T09:48:40.488Z [err] npm ERR!
2023-01-28T09:48:40.488Z [err] npm ERR! The operation was rejected by your operating system.
2023-01-28T09:48:40.488Z [err] npm ERR!
2023-01-28T09:48:40.488Z [err] It is likely you do not have the permissions to access this file as the current user
2023-01-28T09:48:40.488Z [err] npm ERR!
2023-01-28T09:48:40.488Z [err] npm
2023-01-28T09:48:40.488Z [err] ERR! If you believe this might be a permissions issue, please double-check the
2023-01-28T09:48:40.488Z [err] npm ERR! permissions of the file and its containing directories, or try running
2023-01-28T09:48:40.488Z [err] npm
2023-01-28T09:48:40.488Z [err] ERR! the command again as root/Administrator.
2023-01-28T09:48:40.493Z [err]
2023-01-28T09:48:40.494Z [err] npm ERR! A complete log of this run can be found in:
2023-01-28T09:48:40.494Z [err] npm ERR! /root/.npm/_logs/2023-01-28T09_47_28_114Z-debug-0.log
2023-01-28T09:48:40.522Z rc=1

My level of knowledge is quite low, so I would appreciate patience with me. I'm doing my best to, from scratch, be able to make this whole system work.

Thanks in advance.

Hi @emimor - welcome to the forums.

I am afraid we're not going to be able to provide much here.

The error appears to be an issue accessing web resources.
NPM is trying to pulldown packages it needs, but its access to the NPM registry appears to be blocked.

Its likely HA OS is controlling this, or the container is configured incorrectly.

The access is trying to use the IPv6 address : 2606:4700::6810:1a23
so it may be a network config error in HA/The Container

we have very little HA users here, You may get better luck on the HA forums?
But in a nut shell, the Node RED container, is not able to break out to the internet (or at least NPM)

That's not to say someone might know - but usually with HA environments, we have little use


I would recommend to not install node-red from home assistant but just install it separately and install home assistant nodes separately in node-red as well (or while you at it, just drop home assistant altogether and just use node-red instead ;P).

But it looks like a permission issue. Did you try to run it as root (as suggested in the messages) ?

But it looks like a permission issue. Did you try to run it as root (as suggested in the messages) ?

Hi,i dont know do that.