# Node-RED inaccessible 10-15 minutes after start up

**URL:** <https://discourse.nodered.org/t/node-red-inaccessible-10-15-minutes-after-start-up/90543>\
**Category:** General\
**Created:** [29 August 2024 22:05 UTC](https://discourse.nodered.org/t/node-red-inaccessible-10-15-minutes-after-start-up/90543 "2024-08-29T22:05:33Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![JohnnyPicnic](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/johnnypicnic/32/34787_2.png) [@JohnnyPicnic](https://discourse.nodered.org/u/JohnnyPicnic)\
**Post date:** [29 August 2024 22:05 UTC](https://discourse.nodered.org/t/node-red-inaccessible-10-15-minutes-after-start-up/90543/1 "2024-08-29T22:05:33Z")

</div>

Hi All,

I just started loosing access to the web interface sometime after Node-RED starts. All the flows still appear to be running and the logs show no indications of anything bad happening. When working I can access the service at [https://127.0.0.1/1880](https://127.0.0.1/1880)  
Anyone know what could be going on?  
After a restart it come back up for a short time.

---

<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:** [29 August 2024 22:31 UTC](https://discourse.nodered.org/t/node-red-inaccessible-10-15-minutes-after-start-up/90543/2 "2024-08-29T22:31:06Z")

</div>

Are you running on windows?  
Are you running node-red behind a proxy?  
Can you show us the log from start up to the first message after this delay?

---

<div class="post-metadata">

**Author:** ![JohnnyPicnic](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/johnnypicnic/32/34787_2.png) [@JohnnyPicnic](https://discourse.nodered.org/u/JohnnyPicnic)\
**Post date:** [29 August 2024 22:59 UTC](https://discourse.nodered.org/t/node-red-inaccessible-10-15-minutes-after-start-up/90543/3 "2024-08-29T22:59:01Z")

</div>

Sorry I have should have included some more detailed info.  
Yes running on windows.  
No proxy.  
I am away from the server so will have to get the log tomorrow.  
Node-RED v4  
Node JS 20.something

---

<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:** [30 August 2024 06:36 UTC](https://discourse.nodered.org/t/node-red-inaccessible-10-15-minutes-after-start-up/90543/4 "2024-08-30T06:36:16Z")

</div>

Also check the process monitor, or whatever it is called in Windows, to see if node red is hogging the processor when it stops responding.

---

<div class="post-metadata">

**Author:** ![JohnnyPicnic](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/johnnypicnic/32/34787_2.png) [@JohnnyPicnic](https://discourse.nodered.org/u/JohnnyPicnic)\
**Post date:** [30 August 2024 16:35 UTC](https://discourse.nodered.org/t/node-red-inaccessible-10-15-minutes-after-start-up/90543/5 "2024-08-30T16:35:51Z")

</div>

Here is the start of the log.

```auto
Welcome to Node-RED
===================

30 Aug 10:29:37 - [info] Node-RED version: v4.0.2
30 Aug 10:29:37 - [info] Node.js version: v22.7.0
30 Aug 10:29:37 - [info] Windows_NT 10.0.17763 x64 LE

```

Even with Trace on there was nothing in the log about what was ran or was running when the interface went down.  
Looking at the task manager when the interface was down NodeJS and Windows Defender had higher CPU usage than normal. Unfortunately I don't have high enough privileges to turn of Defender.  
With every flow and node disable it became stable again. Slowly starting to turn things back on...

---

<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:** [30 August 2024 17:01 UTC](https://discourse.nodered.org/t/node-red-inaccessible-10-15-minutes-after-start-up/90543/6 "2024-08-30T17:01:03Z")

</div>

Node v22 is not yet supported, so it may be that. Drop back to 20 and try again.

[https://nodered.org/docs/faq/node-versions](https://nodered.org/docs/faq/node-versions)

---

<div class="post-metadata">

**Author:** ![JohnnyPicnic](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/johnnypicnic/32/34787_2.png) [@JohnnyPicnic](https://discourse.nodered.org/u/JohnnyPicnic)\
**Post date:** [30 August 2024 17:04 UTC](https://discourse.nodered.org/t/node-red-inaccessible-10-15-minutes-after-start-up/90543/7 "2024-08-30T17:04:53Z")

</div>

Was on 20.17 and tried 22.7 to see if it made any difference.

---

<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:** [30 August 2024 17:08 UTC](https://discourse.nodered.org/t/node-red-inaccessible-10-15-minutes-after-start-up/90543/8 "2024-08-30T17:08:51Z")

</div>

OK, so not that. I still suggest going back because some nodes do have problems with 22.

When you said the CPU used by nodejs was higher than normal, what does it normally show and what did it change to?

Are you using dashboard charts? If so then disable those and see if it still happens. If that fixes it then over what time are the charts showing, how many lines on each and what sample rate? Add up the total number of points in the charts when they have filled up and see if it comes to tens of thousands.

---

<div class="post-metadata">

**Author:** ![JohnnyPicnic](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/johnnypicnic/32/34787_2.png) [@JohnnyPicnic](https://discourse.nodered.org/u/JohnnyPicnic)\
**Post date:** [30 August 2024 17:20 UTC](https://discourse.nodered.org/t/node-red-inaccessible-10-15-minutes-after-start-up/90543/9 "2024-08-30T17:20:09Z")

</div>

Node JS goes from idle 0% to 5-10% CPU  
Defender goes to 20-30% CPU

Dashboard is being used and so far all charts and graphs are re enabled and working.

---

<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:** [2 September 2024 10:48 UTC](https://discourse.nodered.org/t/node-red-inaccessible-10-15-minutes-after-start-up/90543/10 "2024-09-02T10:48:23Z")

</div>

Did you work out what was causing the problem?

---

<div class="post-metadata">

**Author:** ![JohnnyPicnic](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/johnnypicnic/32/34787_2.png) [@JohnnyPicnic](https://discourse.nodered.org/u/JohnnyPicnic)\
**Post date:** [3 September 2024 16:01 UTC](https://discourse.nodered.org/t/node-red-inaccessible-10-15-minutes-after-start-up/90543/11 "2024-09-03T16:01:07Z")

</div>

No not really, the system was stable over the weekend but I did not redeploy all the flows yet. We have NR running on a production and a development server so I may try copying over our current prod flows and seeing what happens.

---

<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:** [2 December 2024 16:01 UTC](https://discourse.nodered.org/t/node-red-inaccessible-10-15-minutes-after-start-up/90543/12 "2024-12-02T16:01:38Z")

</div>

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