Community SSH node

[Esmewieringa]

Summary

Community SSH nodes (e.g. node-red-contrib-ssh, node-red-node-ssh2) suffer from timeout issues that cause Node-RED instance reboots. A customer running FlowFuse at high transaction volume (10,000 tx/sec) reported this in October 2025 as a production problem blocking their network automation use case.

Problem

Existing community SSH nodes:

• Have timeout issues that cause Node-RED instances to crash and reboot unexpectedly
• Are not maintained to enterprise reliability standards
• Have no official FlowFuse support or SLA

Customer Context

[customer] (https://app-eu1.hubspot.com/contacts/26586079/record/0-2/11137477601) uses FlowFuse for network monitoring automation — integrating monitoring systems with ticketing, automating network equipment tasks via SSH, and connecting to infrastructure APIs. The SSH timeout issue directly impacts their production flows.

Proposed Solution

Related

[hardillb]

Going to need a lot more context here.

• Need to understand better what they mean by "timeout issues" is this blocking the event loop in NodeJS?
• What to the Logs show? Is this the instance being killed by the nr-launcher for exceeding health check?
• Hosted or Remote Instance?
• Self Hosted or FFC?
• Have they raised this with the nodes' authors, if so we need the issue links?
• Assuming Hosted instance, how much CPU/RAM have they given the instance and have they tried increasing it?
• Have they tried increasing the health check interval for a Hosted instance?
• Need to know more about 10,000 messages/tx per second, do these come in bursts or continuous?