# Node-red update from 1.35 to 3.x

**URL:** <https://discourse.nodered.org/t/node-red-update-from-1-35-to-3-x/80690>\
**Category:** General\
**Created:** [21 August 2023 12:25 UTC](https://discourse.nodered.org/t/node-red-update-from-1-35-to-3-x/80690 "2023-08-21T12:25:49Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Aivaras1](https://avatars.discourse-cdn.com/v4/letter/a/8797f3/32.png) [@Aivaras1](https://discourse.nodered.org/u/Aivaras1)\
**Post date:** [21 August 2023 12:25 UTC](https://discourse.nodered.org/t/node-red-update-from-1-35-to-3-x/80690/1 "2023-08-21T12:25:49Z")

</div>

How to properly upgrade node-red on beaglebone blue that uses debian 10 ?

---

<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:** [21 August 2023 12:38 UTC](https://discourse.nodered.org/t/node-red-update-from-1-35-to-3-x/80690/2 "2023-08-21T12:38:03Z")

</div>

Using the normal installation script should work, unless you have anything weird about your system (installed as root, non-standard installation directory etc)  
You might need to force it to update node.js to v18 too.

```auto
cd
bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered) --node18

```

Obviously take a backup of anything important first.

---

<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:** [21 August 2023 12:48 UTC](https://discourse.nodered.org/t/node-red-update-from-1-35-to-3-x/80690/3 "2023-08-21T12:48:59Z")

</div>

> [@jbudd](#):
>
> Using the normal installation script should work

Is that right for Beaglebone? This doesn't mention using the script [Running on BeagleBone Boards : Node-RED](https://nodered.org/docs/getting-started/beaglebone)

---

<div class="post-metadata">

**Author:** ![Aivaras1](https://avatars.discourse-cdn.com/v4/letter/a/8797f3/32.png) [@Aivaras1](https://discourse.nodered.org/u/Aivaras1)\
**Post date:** [21 August 2023 13:08 UTC](https://discourse.nodered.org/t/node-red-update-from-1-35-to-3-x/80690/4 "2023-08-21T13:08:17Z")

</div>

Node-red flow is in /var/lib/node-red/.node-red/  
Owner of a folder is node-red

Did a node.js and npm update  
nvm install 18.17.1  
nvm alias default 18.17.1  
n=$(which node);n=${n%/bin/node}; chmod -R 755 $n/bin/\*; sudo cp -r $n/{bin,lib,share} /usr/local

---

<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:** [21 August 2023 13:26 UTC](https://discourse.nodered.org/t/node-red-update-from-1-35-to-3-x/80690/5 "2023-08-21T13:26:04Z")

</div>

> [@Colin](#):
>
> Is that right for Beaglebone?

To be honest I'm not sure. Your link, which I've never previously seen, begins

> If you want the latest Node-RED 1.x

So it is clearly very out of date.

It does state

> **Note** : Do NOT use the Raspberry Pi / Debian upgrade script

while the page for the Raspberry Pi script says

> This script will work on any **Debian-based** operating system, including **Ubuntu** and **Diet-Pi**. You may need to run `sudo apt install build-essential git curl` first to ensure npm is able to fetch and build any binary modules it needs to install.

I do not have a beaglebone to test and in the absense of clearer documentation I suggest @Aivaras1 is probably right to ignore my suggestion about the script (but not about the backup 😁 )

---

<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:** [21 August 2023 13:40 UTC](https://discourse.nodered.org/t/node-red-update-from-1-35-to-3-x/80690/6 "2023-08-21T13:40:57Z")

</div>

After you update nodejs you must go into your .node-red folder and run  
`npm install`  
to make sure that any nodes that need compiling are built against the current nodejs version.

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [21 August 2023 17:58 UTC](https://discourse.nodered.org/t/node-red-update-from-1-35-to-3-x/80690/7 "2023-08-21T17:58:29Z")

</div>

The Beaglebone boards have their own set of packages... Unfortunately the bb-node-red-installer they have that is still included on their latest bullseye image still relies on the debian nodejs 12 package so Node-RED is somewhat stuck.

You should be able to move to the install script... BUT - a) backup first... :-)... b) you will need to fully remove the bb-node-red-installer package and any existing traces of nodejs and Node-RED - and then run the install script...

You will lose access to GPIO pins and such like as the BB install had nodes that were specific to them. I can't recall if they are generally available via the flows site to be pulled in or not. IE - If you need GPIO then you are likely better off not upgrading - or doing lots of homework first.

---

<div class="post-metadata">

**Author:** ![Aivaras1](https://avatars.discourse-cdn.com/v4/letter/a/8797f3/32.png) [@Aivaras1](https://discourse.nodered.org/u/Aivaras1)\
**Post date:** [22 August 2023 14:40 UTC](https://discourse.nodered.org/t/node-red-update-from-1-35-to-3-x/80690/8 "2023-08-22T14:40:18Z")

</div>

Okay. It's possible to update node-red while it's running on device. Like, update packages and do a restart ?

---

<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 August 2023 15:12 UTC](https://discourse.nodered.org/t/node-red-update-from-1-35-to-3-x/80690/9 "2023-08-22T15:12:01Z")

</div>

In theory yes, and with normal simple upgrade on a Pi for example that is no problem. With such a massive change as Dave has suggested the chances of you getting it exactly right first time is low I think. There is bound to be a good chance it will be non-functional for a time.

---

<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:** [21 October 2023 15:12 UTC](https://discourse.nodered.org/t/node-red-update-from-1-35-to-3-x/80690/10 "2023-10-21T15:12:18Z")

</div>

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