# Cannot install any node with palette error

**URL:** <https://discourse.nodered.org/t/cannot-install-any-node-with-palette-error/96011>\
**Category:** General\
**Created:** [14 March 2025 18:53 UTC](https://discourse.nodered.org/t/cannot-install-any-node-with-palette-error/96011 "2025-03-14T18:53:55Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![MPELectronique](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mpelectronique/32/99492_2.png) [@MPELectronique](https://discourse.nodered.org/u/MPELectronique)\
**Post date:** [14 March 2025 18:53 UTC](https://discourse.nodered.org/t/cannot-install-any-node-with-palette-error/96011/1 "2025-03-14T18:53:55Z")

</div>

Hello. i cannot install any node with the palette manager.

here's the error.  
Hope you can help me.

```auto
2025-03-14T17:55:20.946Z Installer : node-red-contrib-google-calendar 0.1.5

2025-03-14T17:55:20.637Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --omit=dev --engine-strict node-red-contrib-google-calendar@0.1.5

2025-03-14T17:55:38.662Z [err] (node:18109) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.

2025-03-14T17:55:50.827Z [err] npm

2025-03-14T17:55:50.827Z [err] WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@3. I'll try to do my best with it!

2025-03-14T17:55:56.763Z [err] npm

2025-03-14T17:55:56.763Z [err] WARN deprecated sinon@8.0.4: 16.1.1

2025-03-14T17:56:30.774Z [err] npm

2025-03-14T17:56:30.775Z [err] WARN deprecated superagent@3.8.3: Please upgrade to v9.0.0+ as we have fixed a public vulnerability with formidable dependency. Note that v9.0.0+ requires Node.js v14.18.0+. See https://github.com/ladjs/superagent/pull/1800 for insight. This project is supported and maintained by the team at Forward Email @ https://forwardemail.net

2025-03-14T17:56:36.492Z [err] npm

2025-03-14T17:56:36.493Z [err] ERR! code ENOTSUP

2025-03-14T17:56:36.515Z [err] npm ERR! notsup Unsupported engine for mime@4.0.6: wanted: {"node":">=16"} (current: {"node":"12.22.12","npm":"6.14.16"})

2025-03-14T17:56:36.515Z [err] npm

2025-03-14T17:56:36.516Z [err] ERR! notsup Not compatible with your version of node/npm: mime@4.0.6

2025-03-14T17:56:36.516Z [err] npm ERR! notsup Not compatible with your version of node/npm: mime@4.0.6

2025-03-14T17:56:36.516Z [err] npm ERR!

2025-03-14T17:56:36.517Z [err] notsup Required: {"node":">=16"}

2025-03-14T17:56:36.517Z [err] npm ERR! notsup Actual: {"npm":"6.14.16","node":"12.22.12"}

2025-03-14T17:56:36.948Z [err]

2025-03-14T17:56:36.949Z [err] npm ERR! A complete log of this run can be found in:

2025-03-14T17:56:36.949Z [err] npm ERR! /home/pi/.npm/_logs/2025-03-14T17_56_36_534Z-debug.log

2025-03-14T17:56:37.020Z rc=1

-----------------------------------------------------------

2025-03-14T18:01:43.976Z Installer : node-red-contrib-google-calendar 0.1.5

2025-03-14T18:01:43.669Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --omit=dev --engine-strict node-red-contrib-google-calendar@0.1.5

2025-03-14T18:01:57.597Z [err] (node:18185) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.

2025-03-14T18:02:08.200Z [err] npm

2025-03-14T18:02:08.200Z [err] WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@3. I'll try to do my best with it!

2025-03-14T18:02:13.743Z [err] npm

2025-03-14T18:02:13.743Z [err] WARN deprecated sinon@8.0.4: 16.1.1

2025-03-14T18:02:46.807Z [err] npm

2025-03-14T18:02:46.807Z [err] WARN deprecated superagent@3.8.3: Please upgrade to v9.0.0+ as we have fixed a public vulnerability with formidable dependency. Note that v9.0.0+ requires Node.js v14.18.0+. See https://github.com/ladjs/superagent/pull/1800 for insight. This project is supported and maintained by the team at Forward Email @ https://forwardemail.net

2025-03-14T18:02:52.825Z [err] npm

2025-03-14T18:02:52.826Z [err] ERR! code ENOTSUP

2025-03-14T18:02:52.847Z [err] npm ERR!

2025-03-14T18:02:52.847Z [err] notsup Unsupported engine for mime@4.0.6: wanted: {"node":">=16"} (current: {"node":"12.22.12","npm":"6.14.16"})

2025-03-14T18:02:52.847Z [err] npm ERR! notsup Not compatible with your version of node/npm: mime@4.0.6

2025-03-14T18:02:52.848Z [err] npm ERR! notsup

2025-03-14T18:02:52.848Z [err] Not compatible with your version of node/npm: mime@4.0.6

2025-03-14T18:02:52.848Z [err] npm

2025-03-14T18:02:52.848Z [err] ERR! notsup Required: {"node":">=16"}

2025-03-14T18:02:52.848Z [err] npm ERR!

2025-03-14T18:02:52.848Z [err] notsup Actual: {"npm":"6.14.16","node":"12.22.12"}

2025-03-14T18:02:52.892Z [err]

2025-03-14T18:02:52.893Z [err] npm ERR! A complete log of this run can be found in:

2025-03-14T18:02:52.893Z [err] npm ERR!

2025-03-14T18:02:52.893Z [err] /home/pi/.npm/_logs/2025-03-14T18_02_52_865Z-debug.log

2025-03-14T18:02:52.929Z rc=1

```

Thanks!  
Marc.

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [14 March 2025 19:00 UTC](https://discourse.nodered.org/t/cannot-install-any-node-with-palette-error/96011/2 "2025-03-14T19:00:00Z")

</div>

Hi @MPELectronique

Some of the clue(s) are in the error message(s)

```auto
wanted: {"node":">=16"}
current: {"node":"12.22.12"}

```

You really should look at updating Node RED & importantly your Node version.  
if you use the latest Node RED Install script, it can all be updated.

```auto
bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered) --node20 

```

---

<div class="post-metadata">

**Author:** ![MPELectronique](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mpelectronique/32/99492_2.png) [@MPELectronique](https://discourse.nodered.org/u/MPELectronique)\
**Post date:** [14 March 2025 19:31 UTC](https://discourse.nodered.org/t/cannot-install-any-node-with-palette-error/96011/3 "2025-03-14T19:31:54Z")

</div>

It uninstall node-red completly.  
Can i get it back?

thank you.  
Marc.

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [14 March 2025 19:34 UTC](https://discourse.nodered.org/t/cannot-install-any-node-with-palette-error/96011/4 "2025-03-14T19:34:57Z")

</div>

> [@MPELectronique](#):
>
> It uninstall node-red completly.

Really - first we have heard, how did you install Node RED originally?  
I cant imagine that it removed Node RED, unless you installed Node RED using non traditional methods

---

<div class="post-metadata">

**Author:** ![MPELectronique](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mpelectronique/32/99492_2.png) [@MPELectronique](https://discourse.nodered.org/u/MPELectronique)\
**Post date:** [14 March 2025 19:36 UTC](https://discourse.nodered.org/t/cannot-install-any-node-with-palette-error/96011/5 "2025-03-14T19:36:12Z")

</div>

using the bash script

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [14 March 2025 19:38 UTC](https://discourse.nodered.org/t/cannot-install-any-node-with-palette-error/96011/6 "2025-03-14T19:38:10Z")

</div>

> [@MPELectronique](#):
>
> It uninstall node-red completly.

What did?

> [@MPELectronique](#):
>
> `node-red-contrib-google-calendar`

This node has not been updated in nearly 5 years, the Google API's have changed greatly in that time I think.

Also, that node's readme refers to a completely different package quite early on and it isn't clear as to why.

So I would say that you probably shouldn't be using that node. Especially since it (or something else) is disabling certificate checking which is a really bad idea.

---

<div class="post-metadata">

**Author:** ![MPELectronique](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mpelectronique/32/99492_2.png) [@MPELectronique](https://discourse.nodered.org/u/MPELectronique)\
**Post date:** [14 March 2025 20:05 UTC](https://discourse.nodered.org/t/cannot-install-any-node-with-palette-error/96011/7 "2025-03-14T20:05:34Z")

</div>

I managed to reinstall Node-Red using this command:

```auto
bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered) --node16

```

and i write in the adress bar: `http://10.0.0.160:1880/`

and it load and stops.  
what can i do?

Marc.

[Moderator edit to fix url and code formatting]

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [14 March 2025 20:19 UTC](https://discourse.nodered.org/t/cannot-install-any-node-with-palette-error/96011/8 "2025-03-14T20:19:07Z")

</div>

Without more information, we can't help.

Please share the node-red log, at least the startup and the part that stops.

Also, try stopping node-red then rename the `~/.node-red` folder to something different and restart node-red, it should recreate that folder with a clean config. You can rename back later if that works.

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [14 March 2025 20:20 UTC](https://discourse.nodered.org/t/cannot-install-any-node-with-palette-error/96011/9 "2025-03-14T20:20:09Z")

</div>

Once upon a time Node-red stored flows in a file flows\_hostname.json. In more modern releases the flows live in flows.json.

This might be the cause of a blank editor page with no flows.  
Either find your old flows and credentials files and rename them flows.json and flows\_cred.json or else edit settings.js to make Node-red point to the old style filename.

ps The current stable version of node.js is 22. Node-red works reliably with v20 or, on eg an old Raspberry Pi, v18.  
Why did you specify v16?

---

<div class="post-metadata">

**Author:** ![MPELectronique](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mpelectronique/32/99492_2.png) [@MPELectronique](https://discourse.nodered.org/u/MPELectronique)\
**Post date:** [14 March 2025 20:37 UTC](https://discourse.nodered.org/t/cannot-install-any-node-with-palette-error/96011/10 "2025-03-14T20:37:41Z")

</div>

can close the issue i got node-red back with node 20

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [14 March 2025 20:38 UTC](https://discourse.nodered.org/t/cannot-install-any-node-with-palette-error/96011/11 "2025-03-14T20:38:04Z")

</div>