Flowise: Script installs old version (1.6.0) of Flowise

[johnparklee]

The installerscript (https://github.com/community-scripts/ProxmoxVE/raw/main/ct/flowiseai.sh) installs an old version of Flowise (v 1.6; latest version is 2.2.7p1) and drops a lot of warnings. Anyone knows how to fix this?

[tremor021]

i just installed it. its the correct version

the script doesn't choose which version to install, its always the latest

[johnparklee]

Hey Tremor021,

Thank you for your prompt response. I attempted a fresh installation (please see the attached log), which resulted in Flowise version 1.6.0. I noticed that Node.js v20.19.0 was installed on your end, whereas the script installed Node.js v22.14.0 on my side. I suspect this version discrepancy might be causing the issue, as there are some indications that Node.js v22 can lead to problems (see: FlowiseAI/Flowise#3757 )

flowise.txt

[tremor021]

You might be right. Its a bug in Node 22 it seems. i'm quite sure we wont backtrack to Node 20 in the script, we would most likely wait for the fix from the devs.

In the meantime, you can use something like this to go back to Node 20 and install flowise 2.2.7

apt-get remove nodejs
rm -f /etc/apt/sources.list.d/nodesource.list
curl -fsSL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | gpg --dearmor -o /etc/apt/keyrings/nodesource.gpg
    echo "deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_20.x nodistro main" >/etc/apt/sources.list.d/nodesource.list
apt-get update
apt-get install -y nodejs
npm install -g flowise

[johnparklee]

I can confirm that the issue was indeed caused by Node.js v22. Backtracking to v20, as you suggested above, resolved the problem. I completely understand that you’re not modifying the script, and I hope the devs will fix the Node v22 bug soon.

I’ll go ahead and mark this thread as resolved — thanks again for the quick help!

[tremor021]

Yea, don't get me wrong. Fix from our side would be just to switch the Node installation part in the script to target Node v20 instead of v22. But after devs fix the Node bug, we would have to fix the script again and make it target Node v22. So instead of doing multiple changes to our script, we can just hold on a bit and wait for a proper fix from their devs.

I'm sure it wont take long for them to find whats wrong there