# Return to Node-Red after a year and nothing works

**URL:** <https://discourse.nodered.org/t/return-to-node-red-after-a-year-and-nothing-works/86437>\
**Category:** General\
**Created:** [14 March 2024 18:29 UTC](https://discourse.nodered.org/t/return-to-node-red-after-a-year-and-nothing-works/86437 "2024-03-14T18:29:08Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Cathprotech](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cathprotech/32/7913_2.png) [@Cathprotech](https://discourse.nodered.org/u/Cathprotech)\
**Post date:** [14 March 2024 18:29 UTC](https://discourse.nodered.org/t/return-to-node-red-after-a-year-and-nothing-works/86437/1 "2024-03-14T18:29:08Z")

</div>

Hi all,  
I had been running Node-Red for a few years and have lots of flows and everthing worked fine.  
My Rpi 3 died and corrupted my Influxdb data.

I have now decided to start again with Node-Red on a Pi4 and I have installed from fresh.  
Now I have copied all the flows from the original Micro-SD card (they were not corrupted) and also all the modules, however vertually every flow won't run due to missing node types even though I have copied them over.

I suspect this is either to do with a much later and incompatable version of Node-Red or for some reason it is not seeing the node types.

Any pointers please?

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [14 March 2024 20:27 UTC](https://discourse.nodered.org/t/return-to-node-red-after-a-year-and-nothing-works/86437/2 "2024-03-14T20:27:44Z")

</div>

Copy across the file package.json from the .node-red folder, cd into that folder and delete the node\_modules folder. Then run  
`npm install`  
That will install all the missing nodes.

---

<div class="post-metadata">

**Author:** ![Cathprotech](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cathprotech/32/7913_2.png) [@Cathprotech](https://discourse.nodered.org/u/Cathprotech)\
**Post date:** [14 March 2024 22:17 UTC](https://discourse.nodered.org/t/return-to-node-red-after-a-year-and-nothing-works/86437/3 "2024-03-14T22:17:26Z")

</div>

Thanks Colin,

Unfortunatly that didn't work.

I get a lot of these errors...

npm WARN old lockfile at ClientRequest. (/usr/lib/node\_modules/np m/node\_modules/minipass-fetch/lib/index.js:130:14)  
npm WARN old lockfile at ClientRequest.emit (node:events:517:28)  
npm WARN old lockfile at \_destroy (node:\_http\_client:882:13)  
npm WARN old lockfile at onSocketNT (node:\_http\_client:902:5)  
npm WARN old lockfile at process.processTicksAndRejections (node:internal/pr ocess/task\_queues:83:21)

And a lot of these errors....

npm WARN deprecated har-validator@5.1.5: this library is no longer supported  
npm WARN deprecated is-data-descriptor@1.0.0: Please upgrade to v1.0.1  
npm WARN deprecated is-data-descriptor@1.0.0: Please upgrade to v1.0.1  
npm WARN deprecated is-accessor-descriptor@1.0.0: Please upgrade to v1.0.1  
npm WARN deprecated debug@4.1.1: Debug versions \>=3.2.0 \<3.2.7 || \>=4 \<4.3.1 hav

Any other ideas please?

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [15 March 2024 07:02 UTC](https://discourse.nodered.org/t/return-to-node-red-after-a-year-and-nothing-works/86437/4 "2024-03-15T07:02:46Z")

</div>

Those are just warnings. You can probably ignore them.

---

<div class="post-metadata">

**Author:** ![Cathprotech](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cathprotech/32/7913_2.png) [@Cathprotech](https://discourse.nodered.org/u/Cathprotech)\
**Post date:** [15 March 2024 09:09 UTC](https://discourse.nodered.org/t/return-to-node-red-after-a-year-and-nothing-works/86437/5 "2024-03-15T09:09:25Z")

</div>

Hi Colin,

Unfortunatly none of the node modules would update.  
I ended up removing Node-Red completely then re-installing it from scratch.  
I then copied my flows over to get the same errors as before and went through each individual missing node manually adding them.  
I know that npm install should have done this but it just wouldn't.  
There were a few modules that I couldn't find and one such as 'ttn' which just kept failing even with a manual download direct from the node site.  
I ended up deleting the flows that I could not get or update the modules for.

I found it annoying that node-red would not run ANY flows at all when there is a problem with just 1 flow, even with the offending flow being disabled, none of the others would run until that final offending flow was deleted.

Anyway, I'm up and running again now, I only lost about 10 flows in total but they were mostly just projects that didn't really do anything.

Anyway, thanks for taking the time to help.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [13 June 2024 09:10 UTC](https://discourse.nodered.org/t/return-to-node-red-after-a-year-and-nothing-works/86437/6 "2024-06-13T09:10:22Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.