Comments (13)
knolleary
commented on June 24, 2024
Those are strange errors to be hitting. They are both claims that npm cannot find a module at a specific level in the registry. But a quick search now shows those versions both exist and are installable.
I wonder if this is a networking issue from inside the container. Are you able to get a shell inside the container and try to manually install either of those modules?
from node-red-docker.
Robert126
commented on June 24, 2024
I can log in to the shell with in the container.
the file structure is /opt/nodered/data
I also deleted all containers and reinstalled them:
docker-compose down
docker system prune -a
docker-compose pull
docker-compose up -d
And I can ping a public website from here.
Can you advise what you what to do?
from node-red-docker.
Robert126
commented on June 24, 2024
I just found that it is a general problem.
zachowj/node-red-contrib-home-assistant-websocket#898
The issue seems to be not solved.
I adapted my docker-compsoe.yaml file and changed
But still receiving the same errors.
When I down graded the Node Red version, I m getting the following errors
docker logs nodered
13 Sep 21:29:47 - [info]
Welcome to Node-RED
===================
13 Sep 21:29:47 - [info] Node-RED version: v3.0.2
13 Sep 21:29:47 - [info] Node.js version: v16.20.1
13 Sep 21:29:47 - [info] Linux 6.2.16-12-pve x64 LE
13 Sep 21:29:48 - [info] Loading palette nodes
13 Sep 21:29:49 - [info] Dashboard version 3.5.0 started at /ui
13 Sep 21:29:49 - [info] Settings file : /data/settings.js
13 Sep 21:29:49 - [info] Context store : 'default' [module=memory]
13 Sep 21:29:49 - [info] User directory : /data
13 Sep 21:29:49 - [warn] Projects disabled : editorTheme.projects.enabled=false
13 Sep 21:29:49 - [info] Flows file : /data/flows.json
13 Sep 21:29:49 - [info] Server now running at http://127.0.0.1:1880/
13 Sep 21:29:49 - [warn]
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
13 Sep 21:29:49 - [info] Starting flows
13 Sep 21:29:49 - [info] Started flows
13 Sep 21:29:49 - [info] [server:Home Assistant] Connecting to http://***.***.***.***:8123
13 Sep 21:29:49 - [info] [mqtt-broker:mqtt] Connected to broker: mqtt://***.***.***.***:1883
13 Sep 21:29:49 - [info] [server:Home Assistant] Connected to http://***.***.***.***:8123
13 Sep 21:31:08 - [info] Upgrading module: node-red-contrib-home-assistant-websocket to version: 0.56.1
13 Sep 21:32:19 - [warn] Installation of module node-red-contrib-home-assistant-websocket failed:
13 Sep 21:32:19 - [warn] ------------------------------------------
13 Sep 21:32:19 - [warn] npm WARN config production Use `--omit=dev` instead.
npm ERR! code ETARGET
npm ERR! notarget No matching version found for [email protected].
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! A complete log of this run can be found in:
npm ERR! /data/.npm/_logs/2023-09-13T19_31_08_521Z-debug-0.log
13 Sep 21:32:19 - [warn] ------------------------------------------
Error: Install failed
at /usr/src/node-red/node_modules/@node-red/registry/lib/installer.js:285:25
at processTicksAndRejections (node:internal/process/task_queues:96:5)
13 Sep 21:32:19 - [error] Error: Install failed
13 Sep 21:33:32 - [info] Stopping flows
13 Sep 21:33:32 - [info] [server:Home Assistant] Closing connection to http://***.***.***.***:8123
13 Sep 21:33:32 - [info] Stopped flows
13 Sep 21:33:42 - [info]
Welcome to Node-RED
===================
13 Sep 21:33:42 - [info] Node-RED version: v3.0.2
13 Sep 21:33:42 - [info] Node.js version: v16.20.1
13 Sep 21:33:42 - [info] Linux 6.2.16-12-pve x64 LE
13 Sep 21:33:43 - [info] Loading palette nodes
13 Sep 21:33:45 - [info] Dashboard version 3.5.0 started at /ui
13 Sep 21:33:45 - [info] Settings file : /data/settings.js
13 Sep 21:33:45 - [info] Context store : 'default' [module=memory]
13 Sep 21:33:45 - [info] User directory : /data
13 Sep 21:33:45 - [warn] Projects disabled : editorTheme.projects.enabled=false
13 Sep 21:33:45 - [info] Flows file : /data/flows.json
13 Sep 21:33:45 - [warn]
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
13 Sep 21:33:45 - [info] Server now running at http://127.0.0.1:1880/
13 Sep 21:33:45 - [info] Starting flows
13 Sep 21:33:45 - [info] Started flows
13 Sep 21:33:45 - [info] [server:Home Assistant] Connecting to http://***.***.***.***:8123
13 Sep 21:33:45 - [info] [mqtt-broker:mqtt] Connected to broker: mqtt://***.***.***.***:1883
13 Sep 21:33:45 - [info] [server:Home Assistant] Connected to http://***.***.***.***:8123
13 Sep 21:35:05 - [info] Upgrading module: node-red-dashboard to version: 3.6.0
13 Sep 21:36:16 - [warn] Installation of module node-red-dashboard failed:
13 Sep 21:36:16 - [warn] ------------------------------------------
13 Sep 21:36:16 - [warn] npm WARN config production Use `--omit=dev` instead.
npm ERR! code ETARGET
npm ERR! notarget No matching version found for [email protected].
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! A complete log of this run can be found in:
npm ERR! /data/.npm/_logs/2023-09-13T19_35_05_895Z-debug-0.log
13 Sep 21:36:16 - [warn] ------------------------------------------
Error: Install failed
at /usr/src/node-red/node_modules/@node-red/registry/lib/installer.js:285:25
at processTicksAndRejections (node:internal/process/task_queues:96:5)
13 Sep 21:36:16 - [error] Error: Install failed
from node-red-docker.
Robert126
commented on June 24, 2024
As advised, I downgrade and changed my docker-compose.yaml
But I am still getting the errors
Please advice?
docker logs nodered
13 Sep 21:29:47 - [info]
Welcome to Node-RED
===================
13 Sep 21:29:47 - [info] Node-RED version: v3.0.2
13 Sep 21:29:47 - [info] Node.js version: v16.20.1
13 Sep 21:29:47 - [info] Linux 6.2.16-12-pve x64 LE
13 Sep 21:29:48 - [info] Loading palette nodes
13 Sep 21:29:49 - [info] Dashboard version 3.5.0 started at /ui
13 Sep 21:29:49 - [info] Settings file : /data/settings.js
13 Sep 21:29:49 - [info] Context store : 'default' [module=memory]
13 Sep 21:29:49 - [info] User directory : /data
13 Sep 21:29:49 - [warn] Projects disabled : editorTheme.projects.enabled=false
13 Sep 21:29:49 - [info] Flows file : /data/flows.json
13 Sep 21:29:49 - [info] Server now running at http://127.0.0.1:1880/
13 Sep 21:29:49 - [warn]
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
13 Sep 21:29:49 - [info] Starting flows
13 Sep 21:29:49 - [info] Started flows
13 Sep 21:29:49 - [info] [server:Home Assistant] Connecting to http://*.*.*.*
13 Sep 21:29:49 - [info] [mqtt-broker:mqtt] Connected to broker: mqtt://*.*.*.*
13 Sep 21:29:49 - [info] [server:Home Assistant] Connected to http://*.*.*.*
13 Sep 21:31:08 - [info] Upgrading module: node-red-contrib-home-assistant-websocket to version: 0.56.1
13 Sep 21:32:19 - [warn] Installation of module node-red-contrib-home-assistant-websocket failed:
13 Sep 21:32:19 - [warn] ------------------------------------------
13 Sep 21:32:19 - [warn] npm WARN config production Use `--omit=dev` instead.
npm ERR! code ETARGET
npm ERR! notarget No matching version found for [email protected].
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! A complete log of this run can be found in:
npm ERR! /data/.npm/_logs/2023-09-13T19_31_08_521Z-debug-0.log
13 Sep 21:32:19 - [warn] ------------------------------------------
Error: Install failed
at /usr/src/node-red/node_modules/@node-red/registry/lib/installer.js:285:25
at processTicksAndRejections (node:internal/process/task_queues:96:5)
13 Sep 21:32:19 - [error] Error: Install failed
13 Sep 21:33:32 - [info] Stopping flows
13 Sep 21:33:32 - [info] [server:Home Assistant] Closing connection to http://*.*.*.*
13 Sep 21:33:32 - [info] Stopped flows
13 Sep 21:33:42 - [info]
Welcome to Node-RED
===================
13 Sep 21:33:42 - [info] Node-RED version: v3.0.2
13 Sep 21:33:42 - [info] Node.js version: v16.20.1
13 Sep 21:33:42 - [info] Linux 6.2.16-12-pve x64 LE
13 Sep 21:33:43 - [info] Loading palette nodes
13 Sep 21:33:45 - [info] Dashboard version 3.5.0 started at /ui
13 Sep 21:33:45 - [info] Settings file : /data/settings.js
13 Sep 21:33:45 - [info] Context store : 'default' [module=memory]
13 Sep 21:33:45 - [info] User directory : /data
13 Sep 21:33:45 - [warn] Projects disabled : editorTheme.projects.enabled=false
13 Sep 21:33:45 - [info] Flows file : /data/flows.json
13 Sep 21:33:45 - [warn]
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
13 Sep 21:33:45 - [info] Server now running at http://*.*.*.*
13 Sep 21:33:45 - [info] Starting flows
13 Sep 21:33:45 - [info] Started flows
13 Sep 21:33:45 - [info] [server:Home Assistant] Connecting to http://*.*.*.*
13 Sep 21:33:45 - [info] [mqtt-broker:mqtt] Connected to broker: mqtt://*.*.*.*
13 Sep 21:33:45 - [info] [server:Home Assistant] Connected to http://*.*.*.*
13 Sep 21:35:05 - [info] Upgrading module: node-red-dashboard to version: 3.6.0
13 Sep 21:36:16 - [warn] Installation of module node-red-dashboard failed:
13 Sep 21:36:16 - [warn] ------------------------------------------
13 Sep 21:36:16 - [warn] npm WARN config production Use `--omit=dev` instead.
npm ERR! code ETARGET
npm ERR! notarget No matching version found for [email protected].
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! A complete log of this run can be found in:
npm ERR! /data/.npm/_logs/2023-09-13T19_35_05_895Z-debug-0.log
13 Sep 21:36:16 - [warn] ------------------------------------------
Error: Install failed
at /usr/src/node-red/node_modules/@node-red/registry/lib/installer.js:285:25
at processTicksAndRejections (node:internal/process/task_queues:96:5)
13 Sep 21:36:16 - [error] Error: Install failed
13 Sep 22:02:14 - [warn]
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
13 Sep 22:02:14 - [info] Stopping flows
13 Sep 22:02:14 - [info] [server:Home Assistant] Closing connection to http://*.*.*.*
13 Sep 22:02:14 - [info] Stopped flows
13 Sep 22:02:14 - [info] Starting flows
13 Sep 22:02:14 - [info] Started flows
13 Sep 22:02:14 - [info] [server:Home Assistant] Connecting to http://*.*.*.*
13 Sep 22:02:14 - [info] [mqtt-broker:mqtt] Connected to broker: mqtt://*.*.*.*
13 Sep 22:02:14 - [info] [server:Home Assistant] Connected to http://*.*.*.*
from node-red-docker.
hardillb
commented on June 24, 2024
Are you behind a HTTP proxy? Is there anything that may be intercepting/changing http requests to https://registry.npmjs.org?
from node-red-docker.
Robert126
commented on June 24, 2024
No, I am not behind a HTTP proxy
I can pin g any public website
from node-red-docker.
hardillb
commented on June 24, 2024
The errors are explicitly the result of npmjs.org saying the version doesn't exist, unless there is an intermittent error at npmjs.org I am not sure what the problem could be.
I have tried installing those nodes into the standard NR container without error.
from node-red-docker.
Robert126
commented on June 24, 2024
Every thing was working perfectly before updating my system
It even blocks to install another palette in Node red
2023-09-14T15:43:23.318Z Install : node-red-contrib-telegrambot 15.1.6
2023-09-14T15:43:23.336Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict [email protected]
2023-09-14T15:43:23.824Z [err] npm
2023-09-14T15:43:23.824Z [err] WARN
2023-09-14T15:43:23.824Z [err] config production Use `--omit=dev` instead.
2023-09-14T15:44:34.306Z [err] npm
2023-09-14T15:44:34.306Z [err] ERR! code
2023-09-14T15:44:34.306Z [err] DEPTH_ZERO_SELF_SIGNED_CERT
2023-09-14T15:44:34.306Z [err] npm ERR!
2023-09-14T15:44:34.306Z [err] errno DEPTH_ZERO_SELF_SIGNED_CERT
2023-09-14T15:44:34.308Z [err] npm
2023-09-14T15:44:34.308Z [err] ERR!
2023-09-14T15:44:34.308Z [err] request to https://registry.npmjs.org/node-red-contrib-telegrambot failed, reason: self signed certificate
2023-09-14T15:44:34.311Z [err]
2023-09-14T15:44:34.311Z [err] npm ERR! A complete log of this run can be found in:
2023-09-14T15:44:34.311Z [err] npm ERR! /data/.npm/_logs/2023-09-14T15_43_23_786Z-debug-0.log
2023-09-14T15:44:34.321Z rc=1
from node-red-docker.
hardillb
commented on June 24, 2024
What did you change apart from the Node-RED container version? Is there a .npmrc file in /data?
from node-red-docker.
hardillb
commented on June 24, 2024
There IS a proxy (or something else) in the way:
request to https://registry.npmjs.org/node-red-contrib-telegrambot failed, reason: self signed certificate
Means that something is between you and the registry.npmjs.org machine that is pretending to be that machine.
from node-red-docker.
Robert126
commented on June 24, 2024
Interesting, do you have an idea how I can find it? Or solve the issue?
from node-red-docker.
hardillb
commented on June 24, 2024
Not without full access to your system to dig around. Things I would look at would be
- Check the DNS on the host machine is pointing at what you expect
- Check what other containers are running in the same docker network
- What happens if you try and install those nodes in another fresh container (both Node-RED and just a NodeJS container)
from node-red-docker.
hardillb
commented on June 24, 2024
I'm going to close this as it's been over 6 months and the errors are definitely local network related.
from node-red-docker.
Related Issues (20)
- Docker images on the Hub are 9 months out of date / not regularly published even when there isn't a Node Red update HOT 21
- No matching manifest for windows/amd64 HOT 2
- NPM fails to install due to running node v14 instead of recommend v16 HOT 6
- TensorFlow nodes can't be installed due to Alpine image incompatibilty HOT 2
- ERROR: failed to solve: process "/bin/sh -c ./known_hosts.sh /etc/ssh/ssh_known_hosts && rm /usr/src/node-red/known_hosts.sh" HOT 8
- latest is actually -16, shouldn't it be -18? HOT 1
- Cannot load external flows for env var FLOWS=http... HOT 1
- Image with Debian and 18 HOT 8
- Crashing on RPi3 armv7l after latest build HOT 8
- docker pull 'missing signature key' HOT 4
- Support Node 20 HOT 4
- Problems accessing the ttyS2 HOT 5
- unhealthy state since v3.0.0 HOT 9
- Docker image with node 18.x core dumped HOT 12
- I'm not able to create mountpath: /data HOT 4
- Cannot install new nodes on fresh Docker image HOT 9
- Node-Red image v3.1.6-18 has CVE-2023-42282 vulnerability HOT 3
- Node-red image has security vulnerabilities HOT 7
- docker-debian.sh always fails because known_hosts.sh fails with "ssh-keyscan failed, no more retries left" HOT 7
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from node-red-docker.