after installing “node-red-contrib-whatsapp-link” node red won’t start anymore. i think the installation of the node is not the cause, but i experienced this issue after installing. Can anybody help me with this problem? i can’t disable the node on the normal way because NR won’t start.
this is the log:
Add-on version: 14.0.1
You are running the latest version of this add-on.
System: Home Assistant OS 9.4 (amd64 / qemux86-64)
Home Assistant Core: 2023.1.2
Home Assistant Supervisor: 2022.12.1
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-customizations: starting
s6-rc: info: service init-customizations successfully started
s6-rc: info: service init-nodered: starting
patching file nodes/ui_base.html
Hunk #1 succeeded at 1164 (offset 633 lines).
s6-rc: info: service init-nginx successfully started
changed 1 package, and audited 145 packages in 530ms
10 packages are looking for funding
run npm fund for details
found 0 vulnerabilities
s6-rc: info: service init-nodered successfully started
s6-rc: info: service nodered: starting
s6-rc: info: service nodered successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[11:58:03] INFO: Starting Node-RED…
start
node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js
10 Jan 11:58:03 - [info]
Welcome to Node-RED
===================
10 Jan 11:58:03 - [info] Node-RED version: v3.0.2
10 Jan 11:58:03 - [info] Node.js version: v18.12.1
10 Jan 11:58:03 - [info] Linux 5.15.80 x64 LE
10 Jan 11:58:04 - [info] Loading palette nodes
10 Jan 11:58:05 - [info] Dashboard version 3.3.0 started at /endpoint/ui
10 Jan 11:58:05 - [info] Settings file : /etc/node-red/config.js
10 Jan 11:58:05 - [info] Context store : ‘default’ [module=memory]
10 Jan 11:58:05 - [info] User directory : /config/node-red/
10 Jan 11:58:05 - [warn] Projects disabled : editorTheme.projects.enabled=false
10 Jan 11:58:05 - [info] Flows file : /config/node-red/flows.json
10 Jan 11:58:05 - [info] Server now running at http://127.0.0.1:46836/
10 Jan 11:58:05 - [info] Starting flows
10 Jan 11:58:05 - [info] [whatsappLink:Web] Status : Initializing Whatsapp…
[11:58:05] INFO: Starting NGinx…
10 Jan 11:58:05 - [info] Started flows
10 Jan 11:58:05 - [red] Uncaught Exception:
10 Jan 11:58:05 - [error] Error: Failed to launch the browser process! spawn /config/node-red/node_modules/puppeteer/.local-chromium/linux-982053/chrome-linux/chrome ENOENT
TROUBLESHOOTING: puppeteer/docs/troubleshooting.md at 7620cb30c359ebd509680c24cb384c052d891b16 · puppeteer/puppeteer · GitHub
at onClose (/config/node-red/node_modules/puppeteer/src/node/BrowserRunner.ts:268:9)
at ChildProcess. (/config/node-red/node_modules/puppeteer/src/node/BrowserRunner.ts:257:9)
at ChildProcess.emit (node:events:513:28)
at Process.ChildProcess._handle.onexit (node:internal/child_process:289:12)
at onErrorNT (node:internal/child_process:476:16)
at processTicksAndRejections (node:internal/process/task_queues:82:21)
[11:58:05] INFO: Service Node-RED exited with code 1 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service nginx: stopping
[11:58:05] INFO: Service NGINX exited with code 256 (by signal 15)
s6-rc: info: service nginx successfully stopped
s6-rc: info: service init-nginx: stopping
s6-rc: info: service nodered: stopping
s6-rc: info: service init-nginx successfully stopped
[11:58:05] INFO: Service Node-RED exited with code 256 (by signal 15)
s6-rc: info: service nodered successfully stopped
s6-rc: info: service init-nodered: stopping
s6-rc: info: service init-nodered successfully stopped
s6-rc: info: service init-customizations: stopping
s6-rc: info: service init-customizations successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped