# Node red stopped due to interruption and reconnection of internet connection

**URL:** <https://discourse.nodered.org/t/node-red-stopped-due-to-interruption-and-reconnection-of-internet-connection/91155>\
**Category:** General\
**Created:** [21 September 2024 04:06 UTC](https://discourse.nodered.org/t/node-red-stopped-due-to-interruption-and-reconnection-of-internet-connection/91155 "2024-09-21T04:06:33Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![delei](https://avatars.discourse-cdn.com/v4/letter/d/ecae2f/32.png) [@delei](https://discourse.nodered.org/u/delei)\
**Post date:** [21 September 2024 04:06 UTC](https://discourse.nodered.org/t/node-red-stopped-due-to-interruption-and-reconnection-of-internet-connection/91155/1 "2024-09-21T04:06:33Z")

</div>

I have installed node-red on a windows 11 PC which is running 24/7. Node-red is started by the autostart function of windows.

Problem is, node-red will closed automatically without any failure in flows or the installation itself.

Result of checking was, at the same time the internet connection was disconnected and re-established by the provider automatically during night time. That happened several times in the last weeks.

Is it possible that Windows make a reset of user rights as result of the new internet connection? The windows auto update function is disabled btw.

Is there any way to keep node-red running by using and "auto restarter" which is checking wheater node-red is running all time? In case node-red was stopped it should be restarted automatically.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [21 September 2024 20:15 UTC](https://discourse.nodered.org/t/node-red-stopped-due-to-interruption-and-reconnection-of-internet-connection/91155/2 "2024-09-21T20:15:49Z")

</div>

> [@delei](#):
>
> Is it possible that Windows make a reset of user rights as result of the new internet connection?

No.

You need to view the Node-RED logs to see what is going wrong.

> [@delei](#):
>
> Is there any way to keep node-red running by using and "auto restarter" which is checking wheater node-red is running all time? In case node-red was stopped it should be restarted automatically.

Yes, there are several ways on Windows. It is easier on Linux though.

- Run node-red as a service by registering it using the nssm app.
- Run it using the Windows scheduler with the appropriate auto-restart options.
- Run it via PM2.
- Run it behind IIS (as a reverse proxy) using [iisnode](https://github.com/tjanczuk/iisnode)

I don't run my live service using Windows. My Windows PC is a dev PC for Node-RED and I use PM2 which has the advantage of not only making the Node-RED logs easier to deal with but I can use its watch capabilities to auto-restart Node-RED when I change config or node package files.

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [21 September 2024 20:38 UTC](https://discourse.nodered.org/t/node-red-stopped-due-to-interruption-and-reconnection-of-internet-connection/91155/3 "2024-09-21T20:38:02Z")

</div>

> [@TotallyInformation](#):
>
> Run it using the Windows scheduler with the appropriate auto-restart options.

We do this - and its the easiest way IMO.

BUT! - ensure you **deselect** to "stop if the task is running for 3 days" - been burnt many times, leaving this checked

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [21 September 2024 20:39 UTC](https://discourse.nodered.org/t/node-red-stopped-due-to-interruption-and-reconnection-of-internet-connection/91155/4 "2024-09-21T20:39:01Z")

</div>

> [@marcus-j-davies](#):
>
> BUT! - ensure you **deselect** to "stop if running the task for 3 days" - been burnt many times, leaving this checked

🤣

Too true.

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [21 September 2024 20:42 UTC](https://discourse.nodered.org/t/node-red-stopped-due-to-interruption-and-reconnection-of-internet-connection/91155/5 "2024-09-21T20:42:30Z")

</div>

Yup - took us a few hours to work out why a task was stopping after so many days 😬

If going do this route, we usually create a limited/local account, with "Logon on as a Batch Job" rights

---

<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:** [20 December 2024 20:43 UTC](https://discourse.nodered.org/t/node-red-stopped-due-to-interruption-and-reconnection-of-internet-connection/91155/6 "2024-12-20T20:43:29Z")

</div>

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