Node-Red restarting several times a day

[WernerMa96]

Version

20.10.0

Platform

Debian GNU/Linux 11

Subsystem

No response

What steps will reproduce the bug?

No response

How often does it reproduce? Is there a required condition?

Some times a day.

What is the expected behavior? Why is that the expected behavior?

Jan 03 16:03:53 raspberrypi Node-RED[11605]: 3 Jan 16:03:53 - [error] [feedparse:c0c9652a36cbac1c] Error: ETIMEDOUT
Jan 03 16:03:53 raspberrypi Node-RED[11605]: 3 Jan 16:03:53 - [red] Uncaught Exception:
Jan 03 16:03:53 raspberrypi Node-RED[11605]: 3 Jan 16:03:53 - [error] Error [ERR_INTERNAL_ASSERTION]: This is caused by either a bug in Node.js or incorrect usage of Node.js internals.
Jan 03 16:03:53 raspberrypi Node-RED[11605]: Please open an issue with this stack trace at https://github.com/nodejs/node/issues
Jan 03 16:03:53 raspberrypi Node-RED[11605]: at assert (node:internal/assert:14:11)
Jan 03 16:03:53 raspberrypi Node-RED[11605]: at internalConnectMultiple (node:net:1118:3)
Jan 03 16:03:53 raspberrypi Node-RED[11605]: at Timeout.internalConnectMultipleTimeout (node:net:1687:3)
Jan 03 16:03:53 raspberrypi Node-RED[11605]: at listOnTimeout (node:internal/timers:575:11)
Jan 03 16:03:53 raspberrypi Node-RED[11605]: at process.processTimers (node:internal/timers:514:7)
Jan 03 16:03:53 raspberrypi systemd[1]: nodered.service: Main process exited, code=exited, status=1/FAILURE
Jan 03 16:03:53 raspberrypi systemd[1]: nodered.service: Failed with result 'exit-code'.

What do you see instead?

Restarting node-red

Additional information

No response

[aduh95]

Duplicate of #51354