# Cannot stop node-red after update

**URL:** <https://discourse.nodered.org/t/cannot-stop-node-red-after-update/49546>\
**Category:** General\
**Created:** [9 August 2021 21:04 UTC](https://discourse.nodered.org/t/cannot-stop-node-red-after-update/49546 "2021-08-09T21:04:46Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![myWa](https://avatars.discourse-cdn.com/v4/letter/m/b782af/32.png) [@myWa](https://discourse.nodered.org/u/myWa)\
**Post date:** [9 August 2021 21:04 UTC](https://discourse.nodered.org/t/cannot-stop-node-red-after-update/49546/1 "2021-08-09T21:04:46Z")

</div>

Dear node-red forum,  
With very little experience, I successfully performed the Node-Red update to version v2.0.5 on my Debian. I am happy.

The instructions helped me a lot:  
`https://nodered.org/docs/getting-started/raspberrypi`

Then I imported and adjusted my flows and everything worked wonderfully.

Now I also wanted to use the new editor "Monaco". For this I have according to the following instructions:  
`https://nodered.org/blog/2021/07/20/version-2-0-released#node-red-admin-init-command`

and select the new editor:  
`node-red admin init`

My 1st problem is: it didn't work. I am not getting the Monaco Editor.

AND: the last changes to the flows are no longer available.

The 2nd problem is:  
I cannot stop node-red or the service with "node-red stop" or "node-red-stop". This means that even if I use the two commands, I can call up Node-red and the dashboard in the browser.

I suspect that I have a second instance running unintentionally.

Can someone give me a hint how I can find out why the node-red is still running? Or where I made a mistake while trying to activate "Monaco"?

Many greetings,  
wam

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [9 August 2021 21:42 UTC](https://discourse.nodered.org/t/cannot-stop-node-red-after-update/49546/2 "2021-08-09T21:42:56Z")

</div>

> [@myWa](#):
>
> "node-red stop"

`node-red stop` will start node-red with a flows file called `"stop"` - which is obviously not present - so you get no flows.

Also, this starts node-red in user mode (not service mode) so issuing `node-red-stop` wont stop that instance!

Either kill the node-red process or reboot the pi & the service will auto start,

* * *

for future readers, the commands are `node-red-stop` and `node-red-start`. Specifying `node-red stop` or node-red anything` will start node-red and use the argument as the flow file to load.

---

<div class="post-metadata">

**Author:** ![myWa](https://avatars.discourse-cdn.com/v4/letter/m/b782af/32.png) [@myWa](https://discourse.nodered.org/u/myWa)\
**Post date:** [10 August 2021 19:28 UTC](https://discourse.nodered.org/t/cannot-stop-node-red-after-update/49546/3 "2021-08-10T19:28:48Z")

</div>

Hello Steve-Mcl,  
many thanks for the help. That was the mistake.

I was able to stop the service with:  
`systemctl stop node-red`

Now the nice new Monaco Editor works too, perfect!

Thank you

---

<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:** [10 August 2021 20:20 UTC](https://discourse.nodered.org/t/cannot-stop-node-red-after-update/49546/4 "2021-08-10T20:20:16Z")

</div>

> [@myWa](#):
>
> systemctl stop node-red

That is what `node-red-stop` does.

---

<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:** [24 August 2021 20:20 UTC](https://discourse.nodered.org/t/cannot-stop-node-red-after-update/49546/5 "2021-08-24T20:20:43Z")

</div>

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