# Node-Red crashes internally since updated to latest version of Node.JS

**URL:** <https://discourse.nodered.org/t/node-red-crashes-internally-since-updated-to-latest-version-of-node-js/100366>\
**Category:** General\
**Created:** [12 February 2026 06:51 UTC](https://discourse.nodered.org/t/node-red-crashes-internally-since-updated-to-latest-version-of-node-js/100366 "2026-02-12T06:51:35Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![QQ-1978](https://avatars.discourse-cdn.com/v4/letter/q/c68b51/32.png) [@QQ-1978](https://discourse.nodered.org/u/QQ-1978)\
**Post date:** [12 February 2026 06:51 UTC](https://discourse.nodered.org/t/node-red-crashes-internally-since-updated-to-latest-version-of-node-js/100366/1 "2026-02-12T06:51:35Z")

</div>

Hello guys,

perhaps you can help me with an issue.  
We run node-red to simplify company processes with low-code. so far it was working well.  
Since we updated due to IT-security demands to the latest version of Node.JS the windows service that was setup with admin account and NSSM crashes and the server address of node-red like localhost:1880 is not reachable anymore and all flows have stopped working.

In the windows event logs I found the following error message:  
Error attaching to console for service Node-Red. AttachConsole() failed: No process is on the other end of the pipe.

I have already done the following:  
-removed any local file access (reading and writing)  
-removed stderr / stdout as well stdin from NSSM

When observing the Node.exe with sysinternals procmon.exe I have found this error message:  
The server {... server name ...} did not register with DCOM within the required timeout.  
Whatever that means.

After that crash I noticed the CPU load of Node.Exe is at 50%

Perhaps you guys can help and give me a hint what to do.

Thanks very much in advance.

---

<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:** [12 February 2026 07:21 UTC](https://discourse.nodered.org/t/node-red-crashes-internally-since-updated-to-latest-version-of-node-js/100366/2 "2026-02-12T07:21:33Z")

</div>

What version of nodejs?

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [12 February 2026 07:31 UTC](https://discourse.nodered.org/t/node-red-crashes-internally-since-updated-to-latest-version-of-node-js/100366/3 "2026-02-12T07:31:13Z")

</div>

And what version of node-red?

Also, after upgrading nodejs, you may need to rebuild any binary artifacts that node modules created on the previous version of node. You may need to do this in the node-red installation directory as well as your user directory.

How you do this ^ will depend on how you installed node-red and the command line you use to start node-red.

---

<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:** [12 February 2026 07:35 UTC](https://discourse.nodered.org/t/node-red-crashes-internally-since-updated-to-latest-version-of-node-js/100366/4 "2026-02-12T07:35:25Z")

</div>

Also show us the node red startup log.

---

<div class="post-metadata">

**Author:** ![QQ-1978](https://avatars.discourse-cdn.com/v4/letter/q/c68b51/32.png) [@QQ-1978](https://discourse.nodered.org/u/QQ-1978)\
**Post date:** [12 February 2026 07:39 UTC](https://discourse.nodered.org/t/node-red-crashes-internally-since-updated-to-latest-version-of-node-js/100366/5 "2026-02-12T07:39:35Z")

</div>

Node JS current version: node-v25.2.1  
Node-Red Version compare start-up  
12 Feb 08:36:55 - [info] Node-RED version: v4.1.2  
12 Feb 08:36:55 - [info] Node.js version: v25.2.1  
12 Feb 08:36:55 - [info] Windows\_NT 10.0.20348 x64 LE  
12 Feb 08:36:56 - [info] Loading palette nodes  
12 Feb 08:36:59 - [info] Settings file : C:\Users\xxx.node-red\settings.js  
12 Feb 08:36:59 - [info] Context store : 'default' [module=memory]  
12 Feb 08:36:59 - [info] User directory : \Users\xxx.node-red  
12 Feb 08:36:59 - [warn] Projects disabled : editorTheme.projects.enabled=false  
12 Feb 08:36:59 - [info] Flows file : \Users\xxx.node-red\flows.json

Node-Red has been installed via npm

Node-Red runs as windows service via NSSM

---

<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:** [12 February 2026 10:32 UTC](https://discourse.nodered.org/t/node-red-crashes-internally-since-updated-to-latest-version-of-node-js/100366/6 "2026-02-12T10:32:20Z")

</div>

You are using an experimental version of Node.js.

Odd numbered Node.js versions are not considered useful for "live" use. You should always stick to LTS (Long Term Support) versions of which there are usually 3 to choose from.

I do note that I had to make some changes to UIBUILDER to allow some edge-case issues with node.js v24 so it is possible that you might also see some issues with Node-RED but I've not actually found any as yet. v22 is certainly a safe bet for now.

As mentioned, you should do a `npm rebuild` on your userDir folder to make sure any binaries are rebuilt.

---

<div class="post-metadata">

**Author:** ![QQ-1978](https://avatars.discourse-cdn.com/v4/letter/q/c68b51/32.png) [@QQ-1978](https://discourse.nodered.org/u/QQ-1978)\
**Post date:** [12 February 2026 10:55 UTC](https://discourse.nodered.org/t/node-red-crashes-internally-since-updated-to-latest-version-of-node-js/100366/7 "2026-02-12T10:55:23Z")

</div>

Thank you very much for the fast answer.

I will consult with our IT-Security department to grand an exception for Node-JS v22.  
I think actually it was v22 that was running before without issues - though our IT-Security department demanded to upgrade to the latest version of Node-JS due to security purposes and since that the trouble began.

Thank you guys for your help!  
Kind regards

---

<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:** [12 February 2026 11:05 UTC](https://discourse.nodered.org/t/node-red-crashes-internally-since-updated-to-latest-version-of-node-js/100366/8 "2026-02-12T11:05:15Z")

</div>

> [@QQ-1978](#):
>
> our IT-Security department demanded to upgrade to the latest version of Node-JS due to security purposes and since that the trouble began.

Node.js is very good at applying security fixes to ALL current LTS versions, not just the latest. Your IT department should never be using non-LTS versions of _anything_. And, they should be regularly updating things such as node.js for point updates so that they apply security and bug fixes rapidly. So they should be regularly updating v22. Moving to a new major version should involve a conversation with node.js app developers as there may be breaking changes. They certainly should know better than to implement a development version of something like node.js!

---

<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 May 2026 11:06 UTC](https://discourse.nodered.org/t/node-red-crashes-internally-since-updated-to-latest-version-of-node-js/100366/9 "2026-05-13T11:06:12Z")

</div>

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