# Node-RED must be restarted to enable upgraded modules

**URL:** <https://discourse.nodered.org/t/node-red-must-be-restarted-to-enable-upgraded-modules/7568>\
**Category:** General\
**Created:** [4 February 2019 11:11 UTC](https://discourse.nodered.org/t/node-red-must-be-restarted-to-enable-upgraded-modules/7568 "2019-02-04T11:11:28Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Barabba11](https://avatars.discourse-cdn.com/v4/letter/b/c89c15/32.png) [@Barabba11](https://discourse.nodered.org/u/Barabba11)\
**Post date:** [4 February 2019 11:11 UTC](https://discourse.nodered.org/t/node-red-must-be-restarted-to-enable-upgraded-modules/7568/1 "2019-02-04T11:11:28Z")

</div>

Hi, I tried to update a module but it doesn't and display this, I tried to typ in console node-red-stop, node-red,start dut it didn't help, then I did a sudo restart and it worked.  
How to restart then Node red without reboot? Thank you

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [4 February 2019 11:14 UTC](https://discourse.nodered.org/t/node-red-must-be-restarted-to-enable-upgraded-modules/7568/2 "2019-02-04T11:14:02Z")

</div>

depends what you are running Node-Red on and how you installed it.

---

<div class="post-metadata">

**Author:** ![Barabba11](https://avatars.discourse-cdn.com/v4/letter/b/c89c15/32.png) [@Barabba11](https://discourse.nodered.org/u/Barabba11)\
**Post date:** [4 February 2019 15:58 UTC](https://discourse.nodered.org/t/node-red-must-be-restarted-to-enable-upgraded-modules/7568/3 "2019-02-04T15:58:45Z")

</div>

I installed it as you suggested, without root,  
I used the command line to start it up automatically after reboot as you suggested.  
Thank you for help

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [4 February 2019 17:08 UTC](https://discourse.nodered.org/t/node-red-must-be-restarted-to-enable-upgraded-modules/7568/4 "2019-02-04T17:08:38Z")

</div>

I’m sorry I can’t remember ever suggesting to you how you should install Node-RED.  
Or suggesting a command line to start Node-RED automatically.

Is this on a Raspberry Pi?  
Do you mean the Instructions on the website? If so that isn’t me, I’m not that clever! I’m just a long term user of Node-RED who answer questions on the forum when I can.

---

<div class="post-metadata">

**Author:** ![Barabba11](https://avatars.discourse-cdn.com/v4/letter/b/c89c15/32.png) [@Barabba11](https://discourse.nodered.org/u/Barabba11)\
**Post date:** [4 February 2019 18:58 UTC](https://discourse.nodered.org/t/node-red-must-be-restarted-to-enable-upgraded-modules/7568/5 "2019-02-04T18:58:37Z")

</div>

Yes the instruction on the site, yes Raspberry )

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [4 February 2019 19:06 UTC](https://discourse.nodered.org/t/node-red-must-be-restarted-to-enable-upgraded-modules/7568/6 "2019-02-04T19:06:45Z")

</div>

What output do you get when you run `node-red-stop`?

---

<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:** [4 February 2019 19:29 UTC](https://discourse.nodered.org/t/node-red-must-be-restarted-to-enable-upgraded-modules/7568/7 "2019-02-04T19:29:57Z")

</div>

and `node-red-start` (not node-red,start )

---

<div class="post-metadata">

**Author:** ![Barabba11](https://avatars.discourse-cdn.com/v4/letter/b/c89c15/32.png) [@Barabba11](https://discourse.nodered.org/u/Barabba11)\
**Post date:** [6 February 2019 16:57 UTC](https://discourse.nodered.org/t/node-red-must-be-restarted-to-enable-upgraded-modules/7568/8 "2019-02-06T16:57:38Z")

</div>

Mates I don't create subflows, I'm a newbie and I'm using modules in the main flow only, I suppose it is something created by a module itself..

here it is: (i tried to remove // from links

pi@raspberrypi:~ $ node-red-stop

Stop Node-RED

Use node-red-start to start Node-RED again

pi@raspberrypi:~ $ node-red-start

Start Node-RED

Once Node-RED has started, point a browser at http: 192.168.1.251: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. Started Node-RED graphical event wiring tool. 6 Feb 19:54:29 - [info] Welcome to Node-RED

## 6 Feb 19:54:29 - [info] Node-RED version: v0.19.5 6 Feb 19:54:29 - [info] Node.js version: v10.15.0 6 Feb 19:54:29 - [info] Linux 4.14.79-v7+ arm LE 6 Feb 19:54:30 - [info] Loading palette nodes 6 Feb 19:54:40 - [info] Dashboard version 2.13.0 started at /ui 6 Feb 19:54:40 - [info] Settings file : /home/pi/.node-red/settings.js 6 Feb 19:54:40 - [info] Context store : 'default' [module=memory] 6 Feb 19:54:40 - [info] User directory : /home/pi/.node-red 6 Feb 19:54:40 - [warn] Projects disabled : editorTheme.projects.enabled=false 6 Feb 19:54:40 - [info] Flows file : /home/pi/.node-red/flows\_raspberrypi.json 6 Feb 19:54:40 - [info] Server now running at http: 127.0.0.1:1880/ 6 Feb 19:54:40 - [warn]

## Your flow credentials file is encrypted using a system-generated key. If the system-generated key is lost for any reason, your credentials file will not be recoverable, you will have to delete it and re-enter your credentials. You should set your own key using the 'credentialSecret' option in your settings file. Node-RED will then re-encrypt your credentials file using your chosen key the next time you deploy a change.

6 Feb 19:54:41 - [info] Starting flows  
pi : TTY=unknown ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/python -u /home/pi/.node-red/node\_modules/node-red-contrib-lcd20x4-i2c/LCD20x4-I2C/lcd20x4\_i2c.py writelcd 20x4 2  
pam\_unix(sudo:session): session opened for user root by (uid=0)  
6 Feb 19:54:42 - [info] [mosca in:50deaca8.77738c] Binding mosca mqtt server on port: 1883  
6 Feb 19:54:42 - [info] [tcp out:Dimmer WiFi Bridge] connecting to 192.168.1.254:8899  
6 Feb 19:54:42 - [info] [tcp out:Denon Amplificatore] connecting to 192.168.1.252:23  
6 Feb 19:54:43 - [info] Started flows  
6 Feb 19:54:43 - [info] [mqtt-broker:mqtt] Connection failed to broker: mqtt://192.168.1.251:1883  
6 Feb 19:54:43 - [info] [tcp out:Dimmer WiFi Bridge] connected to 192.168.1.254:8899  
6 Feb 19:54:43 - [info] [tcp out:Denon Amplificatore] connected to 192.168.1.252:23  
6 Feb 19:54:58 - [info] [mqtt-broker:mqtt] Connected to broker: mqtt: 192.168.1.251:1883

---

<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:** [6 February 2019 17:22 UTC](https://discourse.nodered.org/t/node-red-must-be-restarted-to-enable-upgraded-modules/7568/9 "2019-02-06T17:22:14Z")

</div>

> [@Barabba11](#):
>
> pi : TTY=unknown ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/python -u /home/pi/.node-red/node\_modules/node-red-contrib-lcd20x4-i2c/LCD20x4-I2C/lcd20x4\_i2c.py writelcd 20x4 2

As you can see, the node node-red-contrib-lcd20x4-i2c is showing an error. Did you follow the instructions for installing it in the readme?

> **[node-red-contrib-lcd20x4-i2c](https://www.npmjs.com/package/node-red-contrib-lcd20x4-i2c)**
>
> Driver for 20x4 HD44780 LCD Display connected via I2C PCF8574. Latest version: 0.1.1, last published: 4 years ago. Start using node-red-contrib-lcd20x4-i2c in your project by running \`npm i node-red-contrib-lcd20x4-i2c\`. There are no other projects...

**[Edit]** Actually I am not sure that is an error, it may just be informational. So what exactly is the problem that you are seeing?

---

<div class="post-metadata">

**Author:** ![Barabba11](https://avatars.discourse-cdn.com/v4/letter/b/c89c15/32.png) [@Barabba11](https://discourse.nodered.org/u/Barabba11)\
**Post date:** [7 February 2019 10:14 UTC](https://discourse.nodered.org/t/node-red-must-be-restarted-to-enable-upgraded-modules/7568/10 "2019-02-07T10:14:34Z")

</div>

Thank you for your help, anyway here I'm trying to figure how I can upgrade modules without a sudo reboot. node-red-stop and node-red-start are not enough. Thank you

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [7 February 2019 10:16 UTC](https://discourse.nodered.org/t/node-red-must-be-restarted-to-enable-upgraded-modules/7568/11 "2019-02-07T10:16:38Z")

</div>

> [@Barabba11](#):
>
> node-red-stop and node-red-start are not enough.

Well, yes they are enough. They stop the node-red process and restart it. That is all that is needed.

Did you reload the editor after restarting node-red?

---

<div class="post-metadata">

**Author:** ![Barabba11](https://avatars.discourse-cdn.com/v4/letter/b/c89c15/32.png) [@Barabba11](https://discourse.nodered.org/u/Barabba11)\
**Post date:** [7 February 2019 10:23 UTC](https://discourse.nodered.org/t/node-red-must-be-restarted-to-enable-upgraded-modules/7568/12 "2019-02-07T10:23:06Z")

</div>

Yes I did, and it keep say me that for upgrade neds to restart. I solved the problem only after sudo reboot.  
I suppose there is a service installed, which is not killing itself and reload, it keeps worjing and it just stop execute something (for example flow) but it is not killed. I suppose, the only answer why it needed reboot..

---

<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:** [7 February 2019 14:12 UTC](https://discourse.nodered.org/t/node-red-must-be-restarted-to-enable-upgraded-modules/7568/13 "2019-02-07T14:12:00Z")

</div>

> [@Barabba11](#):
>
> it keep say me that for upgrade neds to restart

Where is it saying that? That suggests you have upgraded or installed some system related software.

---

<div class="post-metadata">

**Author:** ![Barabba11](https://avatars.discourse-cdn.com/v4/letter/b/c89c15/32.png) [@Barabba11](https://discourse.nodered.org/u/Barabba11)\
**Post date:** [7 February 2019 16:45 UTC](https://discourse.nodered.org/t/node-red-must-be-restarted-to-enable-upgraded-modules/7568/14 "2019-02-07T16:45:08Z")

</div>

I wrote m that to upgrade modules I need to restart Node Red. Pity I haven't made a photo (  
stop and restart didn't help. It helped sudo reboot.  
Any chance to restart node red as it asked without reboot?  
Thank you

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [7 February 2019 16:50 UTC](https://discourse.nodered.org/t/node-red-must-be-restarted-to-enable-upgraded-modules/7568/15 "2019-02-07T16:50:28Z")

</div>

@Barabba11

> [@Barabba11](#):
>
> Any chance to restart node red as it asked without reboot?

Yes, as we have said many times, node-red-stop and node-red-start is what is needed. Those are the commands to stop and restart the node-red service. The flag to say a restart is needed is only held in memory - if the node process is stopped, the flag will be wiped.

So clearly something else is going on here.

After running `node-red-stop` can you check that node-red has really been stopped? Try reloading the editor - it should fail. Check the node process has been stopped (`ps -ef | grep node` will give you a list of node processes - there shouldn't be one).

---

<div class="post-metadata">

**Author:** ![Barabba11](https://avatars.discourse-cdn.com/v4/letter/b/c89c15/32.png) [@Barabba11](https://discourse.nodered.org/u/Barabba11)\
**Post date:** [7 February 2019 17:07 UTC](https://discourse.nodered.org/t/node-red-must-be-restarted-to-enable-upgraded-modules/7568/16 "2019-02-07T17:07:14Z")

</div>

Ok thanks for clear it, next time I'll check!

---

<div class="post-metadata">

**Author:** ![GiovanniG](https://avatars.discourse-cdn.com/v4/letter/g/ecd19e/32.png) [@GiovanniG](https://discourse.nodered.org/u/GiovanniG)\
**Post date:** [7 February 2019 21:47 UTC](https://discourse.nodered.org/t/node-red-must-be-restarted-to-enable-upgraded-modules/7568/17 "2019-02-07T21:47:18Z")

</div>

I have a dubt/question, if I load on boot node red with sudo systemctl enable nodered.service, can I stop it with node-red-stop in a SSH console just opened?  
I think I checked already that the web was not responding, and start it again from SSH, but it still display that error. I guess I did.. maybe was tha chache of browser?

PS: it's always me, with another laptop. I had to ask something in past and my password didn't work there, so I used github account for logging in

---

<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:** [7 February 2019 22:14 UTC](https://discourse.nodered.org/t/node-red-must-be-restarted-to-enable-upgraded-modules/7568/18 "2019-02-07T22:14:32Z")

</div>

> [@GiovanniG](#):
>
> f I load on boot node red with sudo systemctl enable nodered.service, can I stop it with node-red-stop in a SSH console just opened

Yes.  
After stopping you can `sudo systemctl status nodered` to check it is stopped. Do it before the stop aswell, to see the difference.

---

<div class="post-metadata">

**Author:** ![GiovanniG](https://avatars.discourse-cdn.com/v4/letter/g/ecd19e/32.png) [@GiovanniG](https://discourse.nodered.org/u/GiovanniG)\
**Post date:** [21 March 2019 21:28 UTC](https://discourse.nodered.org/t/node-red-must-be-restarted-to-enable-upgraded-modules/7568/19 "2019-03-21T21:28:23Z")

</div>

Hi, I confirm you it was just a mistake of browser, doing a node-red-stop, followed by a start and refreshing completely the browser page solved it. Thank you

---

<div class="post-metadata">

**Author:** ![rei\_vilo](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/rei_vilo/32/162_2.png) [@rei\_vilo](https://discourse.nodered.org/u/rei_vilo)\
**Post date:** [8 May 2020 10:13 UTC](https://discourse.nodered.org/t/node-red-must-be-restarted-to-enable-upgraded-modules/7568/20 "2020-05-08T10:13:16Z")

</div>

Updating the `node-red-dashboard` prompts this message:

 ![Capture 2020-05-08 à 08.23.04](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/9/b/9b5fbb031554400effcd46d934287c9fb7d2e0eb.png)

Is there a way to to restart Node-RED from the GUI?

[Next page](https://discourse.nodered.org/t/node-red-must-be-restarted-to-enable-upgraded-modules/7568.md?page=2)