# Error when starting Node-Red
**URL:** https://discourse.nodered.org/t/error-when-starting-node-red/101582
**Category:** General
**Created:** [2 August 2026 11:42 UTC](https://discourse.nodered.org/t/error-when-starting-node-red/101582 "2026-08-02T11:42:09Z")
**Posts on this page:** 18
**Page:** 1
### Author:  [@warnert](https://discourse.nodered.org/u/warnert)
#### Post date: [2 August 2026 11:42 UTC](https://discourse.nodered.org/t/error-when-starting-node-red/101582/1 "2026-08-02T11:42:09Z")
I run Node-Red on a vm (proxmox) on Debian13. I just updated with the script.
I already added the line Environment="NODE\_RED\_OPTIONS=" in nodered.service.
But I still get the following error:
warner@nodered3:~$ node-red-start
Start Node-RED
Once Node-RED has started, point a browser at [http://192.168.17.220:1880](http://192.168.17.220:1880)
On Pi Node-RED works better with the Firefox or Chrome browser
Use node-red-stop to stop Node-RED
Use node-red-start to start Node-RED again
Use node-red-log to view the recent log output
Use sudo systemctl enable nodered.service to autostart Node-RED at every boot
Use sudo systemctl disable nodered.service to disable autostart on boot
To find more nodes and example flows - go to [http://flows.nodered.org](http://flows.nodered.org)
Starting as a systemd service.
Stopped nodered.service - Node-RED graphical event wiring tool.
Started nodered.service - Node-RED graphical event wiring tool.
nodered.service: Main process exited, code=killed, status=4/ILL
nodered.service: Failed with result 'signal'.
and that keeps on repeating till node-red-stop
---
### Author:  [@warnert](https://discourse.nodered.org/u/warnert)
#### Post date: [2 August 2026 13:29 UTC](https://discourse.nodered.org/t/error-when-starting-node-red/101582/2 "2026-08-02T13:29:59Z")
Addition:
When I use a vm on VirtualBox everything works. I tried again a vm on Proxmox with a clean install of Debian13 and that also gives the error and "illegal instruction".
That is with an QEMU64 cpu.
I'll try a different one...
edit: makes no difference
---
### Author:  [@jbudd](https://discourse.nodered.org/u/jbudd)
#### Post date: [2 August 2026 13:38 UTC](https://discourse.nodered.org/t/error-when-starting-node-red/101582/3 "2026-08-02T13:38:51Z")
Instead of `node-red-start`, does it give you any different output if you use `node-red`, which does not run the systemd script?
---
### Author:  [@warnert](https://discourse.nodered.org/u/warnert)
#### Post date: [2 August 2026 14:02 UTC](https://discourse.nodered.org/t/error-when-starting-node-red/101582/4 "2026-08-02T14:02:08Z")
node-red just gives "illegal instruction" back (in Dutch)
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [2 August 2026 14:36 UTC](https://discourse.nodered.org/t/error-when-starting-node-red/101582/5 "2026-08-02T14:36:32Z")
What do these commands show?
`npm -v`
`node -v`
---
### Author:  [@jbudd](https://discourse.nodered.org/u/jbudd)
#### Post date: [2 August 2026 15:10 UTC](https://discourse.nodered.org/t/error-when-starting-node-red/101582/6 "2026-08-02T15:10:06Z")
Assuming that you have up to date but not bleeding-edge versions of npm (?), node.js (24) and node-red (5.0.4) it might be sensible to re-run the install script.
Note that the script name was recently changed. Be sure to run the command as given in "Getting started" on the website.
---
### Author:  [@warnert](https://discourse.nodered.org/u/warnert)
#### Post date: [2 August 2026 15:26 UTC](https://discourse.nodered.org/t/error-when-starting-node-red/101582/7 "2026-08-02T15:26:53Z")
npm -v: 11.16.0
node -v: 24.18.1
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [2 August 2026 15:48 UTC](https://discourse.nodered.org/t/error-when-starting-node-red/101582/8 "2026-08-02T15:48:20Z")
Another thing to try is to rename the .node-red folder temporarily and then try to start node-red. It will recreate the folder and start with a clean slate. If it starts up ok then it is something about the flow or nodes that you have installed. If it does work then put the .node-red folder back, delete the node\_modules folder in there and, in the .node-red folder run
`npm install`
which will re-install all extra nodes that you have used in your flow. Then restart node-red again.
---
### Author:  [@warnert](https://discourse.nodered.org/u/warnert)
#### Post date: [2 August 2026 17:16 UTC](https://discourse.nodered.org/t/error-when-starting-node-red/101582/9 "2026-08-02T17:16:03Z")
The thing is it goes wrong while installing. And the machine I run Proxmox on is an AMD.Phenom II X4. So I took an Intel machine that was available, an I5-2400.
There I could install Node-Red with no errors on Proxmox.
So what must I conclude: I think there is something wrong with the AMD installation. But there are 35 vm's installed on it. So re-install will be a challenge (at least the backup and restore of these vm's).
But I think that is the way to go...
To test if the conclusion is right I might takeout all disks and put in some other and install...
---
### Author:  [@warnert](https://discourse.nodered.org/u/warnert)
#### Post date: [2 August 2026 17:28 UTC](https://discourse.nodered.org/t/error-when-starting-node-red/101582/10 "2026-08-02T17:28:06Z")
I realize now that I had not updated the intel machine to the latest Proxmox...
I will do that and test again.
And maybe move the working vm from the intel to the amd...
edit: the working vm from the updated intel moved to the amd does not work....
---
### Author:  [@jbudd](https://discourse.nodered.org/u/jbudd)
#### Post date: [2 August 2026 19:21 UTC](https://discourse.nodered.org/t/error-when-starting-node-red/101582/11 "2026-08-02T19:21:36Z")
> [@warnert](#):
>
> The thing is it goes wrong while installing. ...
> So I took an Intel machine that was available, an I5-2400.
> There I could install Node-Red with no errors on Proxmox.
I think that's the first we've heard about errors during install?
> [@warnert](#):
>
> So what must I conclude: I think there is something wrong with the AMD installation. But there are 35 vm's installed on it.
> I think there is something wrong with the AMD installation.
It seems a bit drastic to consider reinstalling 35 working VMs because you can't get NR working?
But i know nothing about VMs or proxmox, so I'll hush up.
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [2 August 2026 20:35 UTC](https://discourse.nodered.org/t/error-when-starting-node-red/101582/12 "2026-08-02T20:35:11Z")
> [@warnert](#):
>
> The thing is it goes wrong while installing
Why did you describe the problem as an error when starting node-red instead of an error while installing it?
What error are you seeing while installing? Show us the install log (which is mentioned at the end of the install).
Did you try what I suggested, renaming .node-red?
> [@warnert](#):
>
> the working vm from the updated intel moved to the amd does not work
I would not really expect it to work if the processors have different instruction sets, though like @jbudd I don't know about VMs used like that.
---
### Author:  [@hardillb](https://discourse.nodered.org/u/hardillb)
#### Post date: [3 August 2026 08:30 UTC](https://discourse.nodered.org/t/error-when-starting-node-red/101582/13 "2026-08-03T08:30:34Z")
If the NodeJS is failing with a SIGILL under proxymox but not VirtualBox then this implies a problem in the virtualization layer.
SIGILL/Illigal Instruction most likely means that the Just In Time Compiler in NodeJS has generated an instruction that is not supported by the virtual CPU that proxmox is providing.
I would suggest you need to work out how to enable your Debian instance to create full core files ([systemd-coredump(8) — systemd-coredump — Debian trixie — Debian Manpages](https://manpages.debian.org/trixie/systemd-coredump/systemd-coredump.8.en.html))on a failure and then probably open a NodeJS GitHub Issue ([GitHub - nodejs/node: Node.js JavaScript runtime ✨🐢🚀✨ · GitHub](http://github.com/nodejs/node)) where they should be able to work out what instruction is being generated and why.
---
### Author:  [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [3 August 2026 08:42 UTC](https://discourse.nodered.org/t/error-when-starting-node-red/101582/14 "2026-08-03T08:42:56Z")
while doing that you may also be able to try tweaking the virtual CPU settings to select other/older? types... and then re-install nodejs again - but yes could be a slow process of elimination.
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [3 August 2026 10:58 UTC](https://discourse.nodered.org/t/error-when-starting-node-red/101582/15 "2026-08-03T10:58:59Z")
> [@warnert](#):
>
> illegal instruction
So, assuming that we actually now now the exact error, this is clearly not a Node-RED issue.
I can see others have had similar issues in the past:
>
>
> \* \*\*Version\*\*: v13.12.0
> \* \*\*Platform\*\*: Linux Centos 7.7.1908 3.10.0-1062.12.1.…el7.x86\_64 #1 SMP Tue Feb 4 23:02:59 UTC 2020 x86\_64 x86\_64 x86\_64 GNU/Linux
> \* \*\*Subsystem\*\*:
>
> \### What steps will reproduce the bug?
>
> Just install node 13 from nodesource (https://rpm.nodesource.com/pub\_13.x/el/7/x86\_64)
> Or builder from source. Onto ~old AMD CPU.
> \`\`\`
> npm install any-module-name
> \`\`\`
>
> With CPU:
>
> \### How often does it reproduce? Is there a required condition?
>
> Every time.
>
> \### What is the expected behavior?
>
> Install packages
>
> \### What do you see instead?
>
> \`\`\`
> Illegal instruction\] - rollbackFailedOptional: verb npm-session 549900aa043a9abd
> \`\`\`
>
> \### Additional information
>
> Checked CPU:
>
> \* AMD Phenom(tm) II X6 1100T Processor
> Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr\_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant\_tsc art rep\_good nopl nonstop\_tsc extd\_apicid aperfmperf pni monitor cx16 popcnt lahf\_lm cmp\_legacy svm extapic cr8\_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt cpb hw\_pstate retpoline\_amd ibp\_disable vmmcall npt lbrv svm\_lock nrip\_save pausefilter
>
> \* AMD Sempron(tm) 140 Processor
>
> \* Also checked with same CPUs and qemu+kvm with Ubuntu 18.04 guest
>
> Node 12 work correct.
Leo AI said this:
The **"Illegal instruction (core dumped)"** error in **Node.js** on **Proxmox** is primarily caused by **CPU instruction set mismatches** , specifically the lack of **AVX** or **AVX2** support being passed to the virtual machine.
**Common Causes and Solutions:**
- **Default CPU Model Limitations** : Proxmox defaults to the **KVM64** CPU model for Linux guests, which **does not support AVX** instructions. Modern versions of Node.js (especially v16+) often require AVX.
- **Virtualization Passthrough** : If using **KVM** or **QEMU** , the default settings may hide advanced CPU features.
- **Old Hardware Compatibility** : If running on older hardware (e.g., **AMD Phenom II** or **Opteron 23xx** ) that lacks AVX, newer Node.js binaries will crash.
- **Architecture Mismatch** : Ensure the Node.js binary matches the guest architecture (e.g., **x86\_64** vs **ARM** ). Installing ARM packages on x86 systems or vice versa will cause this error.
**Recommended Step** : Change the Proxmox VM CPU type to **Host** in the hardware settings, restart the VM, and reinstall Node.js.
---
### Author:  [@warnert](https://discourse.nodered.org/u/warnert)
#### Post date: [3 August 2026 19:39 UTC](https://discourse.nodered.org/t/error-when-starting-node-red/101582/16 "2026-08-03T19:39:01Z")
I already used cputype Host but that does not solve the problem.
I decided to use temporary a different host where I have the node running.
My workaround is now to put later another motherboard in the original machine.
I have one at another place temporarily that will do I think.
Maybe a Phenom is too old....
---
### Author:  [@bakman2](https://discourse.nodered.org/u/bakman2)
#### Post date: [4 August 2026 07:16 UTC](https://discourse.nodered.org/t/error-when-starting-node-red/101582/17 "2026-08-04T07:16:52Z")
Have you tried an LXC (CT) instead of a VM (why use VM's when you have LXC at your disposal, those are much more efficient and tiny) ?
---
### Author:  [@warnert](https://discourse.nodered.org/u/warnert)
#### Post date: [4 August 2026 15:33 UTC](https://discourse.nodered.org/t/error-when-starting-node-red/101582/18 "2026-08-04T15:33:15Z")
Yes, a CT gives the same problems. I discovered the error with a CT because I used a ProxMox-VE-helperscript and that uses a CT.
Im going to swap the motherbord for a newer one to get things working again.
I am convinced it is due to the CPU not having the instructions that are used as someone said before.