# Problem with nodes when internet not working. Discussion

**URL:** https://discourse.nodered.org/t/problem-with-nodes-when-internet-not-working-discussion/97453
**Category:** General
**Created:** [6 June 2025 22:32 UTC](https://discourse.nodered.org/t/problem-with-nodes-when-internet-not-working-discussion/97453 "2025-06-06T22:32:46Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [7 June 2025 21:06 UTC](https://discourse.nodered.org/t/problem-with-nodes-when-internet-not-working-discussion/97453/5 "2025-06-07T21:06:51Z")

</div>

This comes from a very recent post of mine....

> [@Sudden severe failure of entire flow on machine](https://discourse.nodered.org/t/sudden-severe-failure-of-entire-flow-on-machine/97428):
>
> Hey folks. Bad new where I am: One of my machines now won't run the old NR flow it did a couple of days ago. Situation - bigger picture: RasPi 3B+ running Buster. It is my NTP server, MQTT broker and a WAP. Weirdly, it loads, starts and runs, but keeps restarting NR. (NOT rebooting!) I tweaked something (wrongly) with the NTP stuff and realised it wasn't needed. Alas between doing it and realising it: all hell broke loose. Where the machine usually runs at 12% CPU load, it maxed out at…

(Wave to @Sean-McG)

# So here's the existing way I was thinking I would mitigate such failures:

Quick walk through the machines:  
TimePi - NTP, Voice, open weather.  
TelePi - overall monitor of all machines.  
BedPi - DHCP/DNS server. Real world controller.

_TimePi_  
Voice flow  
`wait` node. 30 seconds delay all messages.  
(stuff)  
`tts node`  
play ~~sound~~ voice - local speaker  
end signal  
loop back to `wait` node to send next message

(Else where on same flow)  
`status` node watching the `tts` node  
notes status.  
`switch` node to detect _problems_ (aka if NOT **OK** )  
`change` node - sets things up  
signals to `wait` node to dump all queued messages  
blocks any more messages getting through.

Which I actually did test and it worked. In my given situation at the time.  
Granted there is also the `open weather` node on that machine too.

So, I stupidly lost my DHCP and DNS machine. (ANOTHER machine)  
So the network was DOWN.

The machines were sending through messages indicating this.  
(Not too many. I have `filter` nodes to stop the same message coming through twice.)

## So at this stage:

I saw the DHCP machine die. BedPi ☹  
Then the machine with the voice load went from 12% to like 70%.  
Not too bad, but worrying.  
It stayed there and I WAS getting (voice) messages. So not sure how bad the crash was or not.  
I quickly went in and tried to stop all the logging.  
Suddenly on TimePi  
`no response from server`  
Soon after dashboard refresh. NR had restarted. 😕  
Started again, repeat.

Tried copying old versions to the machine. No change.

Steve then suggested disabling the `tts` node.  
BINGO!  
That was it.  
(Lost a bit of work, but....)

Now the `open weather` node is only used (automatically) once a day.  
In the morning to give the weather at that time.  
It wasn't morning and wasn't being called.

I could post extracts from the `voice` flow if _you_ want.  
But I think the main part would be the failure part.  
The rest is kind of all over the place because there are a few other things happen between the reception of the message and it going to the `tts` node.  
Nothing critical to this.  
(Ok, I can have the messages prefixed with a notification bell/sound. If it is detected, that sound is played prior to the voice being heard)

---

_[View the full topic](https://discourse.nodered.org/t/problem-with-nodes-when-internet-not-working-discussion/97453)._