Losing config node data overnight


I have NR running in docker on a Synology NAS. I use it with Home Assistant and a config node has the URL and key to connect.

This has been working fine for a long time, but for the last few days (perhaps the start of the year?) I am finding that connection to Home Assistant has been lost overnight.

The NR log shows that something seems to happen around 2024/01/04 22:30 and 2024/01/03 23:22 where the flows are Stopped, Updated and then Started followed by errors saying that "No credentials provided" and "Server config node not found"

In the morning I update the config again and it works fine for the rest of the day. I updated the HomeAssistant integration yesterday in the hope that that would resolve the issue but it didn't.

I am on version v3.1.3 of NR, 0.62.2 of node-red-contrib-home-assistant-websocket, v3.1.2 of the Home Assistant Node-RED Companion.

I do have Watchtower updating mu docker components but that only runs on a Friday night, and it hasn't lost config in the past.

I have attached my log:
nodered.csv.txt (141.5 KB)

Any ideas on what could be causing this?


Is your NR open to the Web? It looks like an intrusion.
Have you checked what your flows.json file contains?
Read this thread urgently:

1 Like

Hi, thanks for getting back to me. I had a good look through flows.json and didn't find anything suspicious - no hidden nodes executing code, all the nodes in there were ones I had added. I also checked /dev and /dev/shm for unusual files.

I am not exposing NR to the internet, but other services on the NAS are.

So, hopefully not a hack.

Your flow is not supposed to deploy itself - it can if you call the api (from a node), is that the case?

If not, a contrib node or someone did it

No, I don't anything like that, but I guess it's possible that the Home Assistant integration is doing something it shouldn't. I'll cross post in their forums to see if anyone has come across this.

Regarding the "flow deploying itself". I assume you are referring to these parts of the log where it looks like they are stopped, updated and restarted:

stdout,3 Jan 23:22:20 - [error] [server:8543beb1656653ec] Error: No credentials provided
2024/01/03 23:22:20,stdout,3 Jan 23:22:20 - [info] Starting flows
2024/01/03 23:22:20,stdout,3 Jan 23:22:20 - [info] Updated flows
2024/01/03 23:22:20,stdout,3 Jan 23:22:20 - [info] Stopped flows
2024/01/03 23:22:20,stdout,3 Jan 23:22:20 - [info] Stopping flows
2024/01/03 23:22:15,stdout,3 Jan 23:22:15 - [info] Started flows
2024/01/03 23:22:15,stdout,3 Jan 23:22:15 - [info] Starting flows
2024/01/03 23:22:15,stdout,3 Jan 23:22:15 - [info] Updated flows
2024/01/03 23:22:15,stdout,3 Jan 23:22:15 - [info] Stopped flows
2024/01/03 23:22:15,stdout,3 Jan 23:22:15 - [info] Stopping flows

Yes, at this time of night I wouldn't have been doing that so it is concerning.


I fear there has been an intrusion by something other than NR :grimacing:

Well it didn't happen last night. HA was automatically updated at 03:00. Hopefully the issue has just gone away! :man_shrugging:

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