Issue Installing Palette in FlowFuse

Vendors FlowFuse
1

I have installed FlowFuse version 2.17.0 self-hosted community edition on a Docker Platform. The application is running perfectly, however I faced some error while trying to install palettes for example ' node-red-dashboard '.

For better understanding I attached the error log below:

6/2/2025 2:48:37 PM  [info]    Installing module: node-red-dashboard, version: 3.6.5
6/2/2025 2:50:19 PM  [warn]    Installation of module node-red-dashboard failed:
6/2/2025 2:50:19 PM  [warn]    ------------------------------------------
6/2/2025 2:50:19 PM  [warn]    npm error code ENOTEMPTY
npm error syscall rename
npm error path /data/node_modules/node-red-contrib-opcua-server
npm error dest /data/node_modules/.node-red-contrib-opcua-server-htzdEQuA
npm error errno -39
npm error ENOTEMPTY: directory not empty, rename '/data/node_modules/node-red-contrib-opcua-server' -> '/data/node_modules/.node-red-contrib-opcua-server-htzdEQuA'
npm error A complete log of this run can be found in: /data/.npm/_logs/2025-06-02T08_48_38_322Z-debug-0.log

6/2/2025 2:50:19 PM  [warn]    ------------------------------------------
6/2/2025 2:50:19 PM  []        Error: Install failed
6/2/2025 2:50:19 PM  []            at /usr/src/node-red/node_modules/@node-red/registry/lib/installer.js:290:25
6/2/2025 2:50:19 PM  []            at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
6/2/2025 2:50:19 PM  [error]   {"status":400}

But one more thing it doesn't give error for a single node. While trying to install any external nodes I get that error. So if anyone can give any idea it will be great help for me. My node red version is 4.0.9 and the Node.js version is 20.19.0

Thanks.

2

This is (or used to be) quite common (lots of answers on the forum and around the internet for why this can happen) but the resolution is to delete the offending directory...

pretty much any directory in '/data/node_modules/... that ends with - followed by 8 RaNDom ChaRacTErS is a failed install and can be deleted.

3

Still has the problem. Can anyone give any other suggestions?

4

Are you saying that after deleting the folder mentioned in the error that you still get exactly the same error? That seems unlikely. If you are getting it on other similarly named folders then delete all of them.

5

I can't find that folder you talking about. Do I have to look that folder into docker container or in my host machine. I look both into it but can't find anything like that.

6

It will be in the docker container. Also since it's name starts with a . it is hidden.

Follow this thread...

7

An alternative option here is to try suspending the instance and starting it again.

This will tear down the container and build it from scratch again which will remove any lingering directories from failed installs.

1 Like