# Update issues with NR 4.1.1

**URL:** <https://discourse.nodered.org/t/update-issues-with-nr-4-1-1/99473>\
**Category:** General\
**Created:** [21 October 2025 22:09 UTC](https://discourse.nodered.org/t/update-issues-with-nr-4-1-1/99473 "2025-10-21T22:09:45Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![RueCo](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/rueco/32/765_2.png) [@RueCo](https://discourse.nodered.org/u/RueCo)\
**Post date:** [21 October 2025 22:09 UTC](https://discourse.nodered.org/t/update-issues-with-nr-4-1-1/99473/1 "2025-10-21T22:09:45Z")

</div>

Having updated to NR 4.1.1 on a debian bullseye pi machine and trying to remove a note in the pallet manager I get the following error:

```auto
2025-10-21T21:31:44.596Z remove: node-red-contrib-enocean
2025-10-21T21:31:43.613Z npm remove --no-audit --no-update-notifier --no-fund --save node-red-contrib-enocean
2025-10-21T21:31:48.277Z [err] npm error code ENOTEMPTY
2025-10-21T21:31:48.278Z [err] npm error syscall rename
2025-10-21T21:31:48.279Z [err] npm error path /home/pi/.node-red/node_modules/esm
2025-10-21T21:31:48.282Z [err] npm error dest /home/pi/.node-red/node_modules/.esm-muDamFlX
2025-10-21T21:31:48.282Z [err] npm error errno -39
2025-10-21T21:31:48.286Z [err] npm error ENOTEMPTY: directory not empty, rename '/home/pi/.node-red/node_modules/esm' -> '/home/pi/.node-red/node_modules/.esm-muDamFlX'
2025-10-21T21:31:48.296Z [err] npm error A complete log of this run can be found in: /home/pi/.npm/_logs/2025-10-21T21_31_44_232Z-debug-0.log
2025-10-21T21:31:48.349Z rc=217

```

Trying to install @flowfuse/node-red-dashboard 1.29.0 I get the following error:

```auto
2025-10-21T21:33:31.901Z install: @flowfuse/node-red-dashboard 1.29.0
2025-10-21T21:33:30.875Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --omit=dev --engine-strict @flowfuse/node-red-dashboard@1.29.0
2025-10-21T21:33:43.031Z [err] npm error code ENOTEMPTY
2025-10-21T21:33:43.032Z [err] npm error syscall rename
2025-10-21T21:33:43.032Z [err] npm error path /home/pi/.node-red/node_modules/undici
2025-10-21T21:33:43.034Z [err] npm error dest /home/pi/.node-red/node_modules/.undici-pZNij1KU
2025-10-21T21:33:43.035Z [err] npm error errno -39
2025-10-21T21:33:43.036Z [err] npm error ENOTEMPTY: directory not empty, rename '/home/pi/.node-red/node_modules/undici' -> '/home/pi/.node-red/node_modules/.undici-pZNij1KU'
2025-10-21T21:33:43.046Z [err] npm error A complete log of this run can be found in: /home/pi/.npm/_logs/2025-10-21T21_33_31_544Z-debug-0.log
2025-10-21T21:33:43.076Z rc=217

```

Node V 22.21.0  
Nodejs V 20.19.1  
nmp V 10.9.4  
nvm V 0.40.3

last update which started ok  
bash \<(curl -sL [https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered](https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered)) --confirm-root --confirm-install --confirm-pi --restart --allow-low-ports --update-nodes

However this create startup issues and would not run NR anymore  
bash \<(curl -sL [https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered](https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered)) --confirm-root --confirm-install --confirm-pi --restart --allow-low-ports --update-nodes --node22

Any help or recommendations, thank you?

---

<div class="post-metadata">

**Author:** ![Sean-McG](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sean-mcg/32/54677_2.png) [@Sean-McG](https://discourse.nodered.org/u/Sean-McG)\
**Post date:** [21 October 2025 23:39 UTC](https://discourse.nodered.org/t/update-issues-with-nr-4-1-1/99473/2 "2025-10-21T23:39:38Z")

</div>

Try deleting these directories -

> [@RueCo](#):
>
> `.undici-pZNij1KU`

> [@RueCo](#):
>
> `.esm-muDamFlX`

---

<div class="post-metadata">

**Author:** ![RueCo](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/rueco/32/765_2.png) [@RueCo](https://discourse.nodered.org/u/RueCo)\
**Post date:** [22 October 2025 03:37 UTC](https://discourse.nodered.org/t/update-issues-with-nr-4-1-1/99473/3 "2025-10-22T03:37:49Z")

</div>

Thank you very much for this super fast reply and support.

I was able to delete the `.undici-pZNij1KU` directory and the `.esm-muDamFlX`.

It looks like that node-red-contrib-enocean has been removed from the pallet manager.

However, trying to install @flowfuse/node-red-dashboard 1.29.0 via the pallet manager gives me now the following error

```auto
2025-10-22T03:05:07.457Z Install : @flowfuse/node-red-dashboard 1.29.0

2025-10-22T03:05:06.731Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --omit=dev --engine-strict @flowfuse/node-red-dashboard@1.29.0
2025-10-22T03:05:49.033Z [err] npm error code EACCES
2025-10-22T03:05:49.034Z [err] npm error syscall open
2025-10-22T03:05:49.035Z [err] npm error path /home/pi/.node-red/package.json
2025-10-22T03:05:49.036Z [err] npm error errno -13
2025-10-22T03:05:49.045Z [err] npm error Error: EACCES: permission denied, open '/home/pi/.node-red/package.json'
2025-10-22T03:05:49.045Z [err] npm error at async open (node:internal/fs/promises:639:25)
2025-10-22T03:05:49.045Z [err] npm error at async writeFile (node:internal/fs/promises:1216:14)
2025-10-22T03:05:49.045Z [err] npm error at async PackageJson.save (/usr/lib/node_modules/npm/node_modules/@npmcli/package-json/lib/index.js:259:23)
2025-10-22T03:05:49.045Z [err] npm error at async [saveIdealTree] (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:1528:9)
2025-10-22T03:05:49.045Z [err] npm error at async Arborist.reify (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:134:5)
2025-10-22T03:05:49.045Z [err] npm error at async Install.exec (/usr/lib/node_modules/npm/lib/commands/install.js:150:5)
2025-10-22T03:05:49.045Z [err] npm error at async Npm.exec (/usr/lib/node_modules/npm/lib/npm.js:208:9)
2025-10-22T03:05:49.045Z [err] npm error at async module.exports (/usr/lib/node_modules/npm/lib/cli/entry.js:67:5) {
2025-10-22T03:05:49.045Z [err] npm error errno: -13,
2025-10-22T03:05:49.045Z [err] npm error code: 'EACCES',
2025-10-22T03:05:49.045Z [err] npm error syscall: 'open',
2025-10-22T03:05:49.045Z [err] npm error path: '/home/pi/.node-red/package.json'
2025-10-22T03:05:49.045Z [err] npm error }
2025-10-22T03:05:49.053Z [err] npm error
2025-10-22T03:05:49.053Z [err] npm error The operation was rejected by your operating system.
2025-10-22T03:05:49.053Z [err] npm error It is likely you do not have the permissions to access this file as the current user
2025-10-22T03:05:49.053Z [err] npm error
2025-10-22T03:05:49.053Z [err] npm error If you believe this might be a permissions issue, please double-check the
2025-10-22T03:05:49.053Z [err] npm error permissions of the file and its containing directories, or try running
2025-10-22T03:05:49.053Z [err] npm error the command again as root/Administrator.
2025-10-22T03:05:49.072Z [err] npm error A complete log of this run can be found in: /home/pi/.npm/_logs/2025-10-22T03_05_07_343Z-debug-0.log
2025-10-22T03:05:49.115Z rc=243

```

For some unknown reason this seems to be now a permission issue.  
How do I need to proceed to install @flowfuse/node-red-dashboard 1.29.0 properly and also future notes without any issues?

---

<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:** [22 October 2025 06:57 UTC](https://discourse.nodered.org/t/update-issues-with-nr-4-1-1/99473/4 "2025-10-22T06:57:03Z")

</div>

It looks as if you have used sudo (root) to do something in the .node-red directory so have ended up with the node red user unable to update the files.

You can probably fix it by restoring ownership by logging on as the user pi and running  
`sudo chown -R pi:pi ~/.node-red`

---

<div class="post-metadata">

**Author:** ![RueCo](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/rueco/32/765_2.png) [@RueCo](https://discourse.nodered.org/u/RueCo)\
**Post date:** [22 October 2025 08:06 UTC](https://discourse.nodered.org/t/update-issues-with-nr-4-1-1/99473/5 "2025-10-22T08:06:09Z")

</div>

Yes, Colin you are right. I found a few files in ~/.node-red with root ownership.

This must have happened some times to end last year when I had NR update issues.

Whenever I tried to update with your script:

`bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered) --confirm-root --confirm-install --confirm-pi --restart --allow-low-ports --update-nodes --node22`

NR would then not start anymore, so I always moved back to run the update without the option --node22. May be the update issue has always been related to the ownership after all.

Finally I was able to remove some old or not required notes and NR now starts again without any issue:

22 Oct 09:19:08 - [info] Node-RED version: v4.1.1  
22 Oct 09:19:08 - [info] Node.js version: v20.19.1  
22 Oct 09:19:08 - [info] Linux 5.10.103-v7l+ arm LE  
22 Oct 09:19:09 - [info] Loading palette nodes  
22 Oct 09:19:13 - [info] Dashboard version 3.6.6 started at /ui

Anyhow guys thanks again for all your support.  
Let's see how far I get till I'm stuck again.

---

<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:** [22 October 2025 08:27 UTC](https://discourse.nodered.org/t/update-issues-with-nr-4-1-1/99473/6 "2025-10-22T08:27:09Z")

</div>

Why have you got --confirm-root in your options? You should not run the install script as root.

---

<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:** [22 October 2025 08:27 UTC](https://discourse.nodered.org/t/update-issues-with-nr-4-1-1/99473/7 "2025-10-22T08:27:28Z")

</div>

> [@RueCo](#):
>
> bash \<(curl -sL [https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered](https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered)) --confirm-root --confirm-install --confirm-pi --restart --allow-low-ports --update-nodes --node22

Can you explain your reason for picking each of that long list of flags, especially --confirm-root and --allow\_low\_ports?

Edit: snap!

---

<div class="post-metadata">

**Author:** ![RueCo](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/rueco/32/765_2.png) [@RueCo](https://discourse.nodered.org/u/RueCo)\
**Post date:** [23 October 2025 10:54 UTC](https://discourse.nodered.org/t/update-issues-with-nr-4-1-1/99473/8 "2025-10-23T10:54:56Z")

</div>

Thank you for indicating these aspects and making your points. Since this goes a long way back when I started with NR, at some point I never questioned again my setting. I assumed I made the right choices. Anyhow thanks again for your support.

---

<div class="post-metadata">

**Author:** ![RueCo](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/rueco/32/765_2.png) [@RueCo](https://discourse.nodered.org/u/RueCo)\
**Post date:** [22 December 2025 10:02 UTC](https://discourse.nodered.org/t/update-issues-with-nr-4-1-1/99473/9 "2025-12-22T10:02:31Z")

</div>

Now I remember again the reason for applying the --allow-low-ports parameter, it was due to some issues with alexa nodes which required port 80.  
At the time I did not understand yet the iptables command sudo iptables -D PREROUTING -t nat -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 8000.  
There is always room to learn more and improve the knowledge in particular with linux, nodered, permissions, firewalls, networking, certificates etc.  
Well as we say in German, work hard in order not to die stupid, but sometimes it seems realy difficult to understand some of the documentation offered in the linux world. Anyhow, constructive recommendations, solutions or help is always welcome.  
So thanks again for pointing out these various issues!

---

<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:** [22 March 2026 10:03 UTC](https://discourse.nodered.org/t/update-issues-with-nr-4-1-1/99473/10 "2026-03-22T10:03:23Z")

</div>

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