Troubleshooting¶

Anyone who reaches Node-RED can view or change flows¶

This is expected — Node-RED has no sign-in by default on this gateway. See the security note. Restricting access requires a server-side adminAuth configuration change, not something set from the editor itself.

Deploy is greyed out¶

Nothing has changed since the last deploy — there's nothing to push. This is the normal state right after opening the editor or right after a successful deploy.

There's no dashboard at /ui¶

This gateway doesn't have node-red-dashboard (or similar UI package) installed — only node-red-contrib-aedes and node-red-contrib-modbus are added on top of the core nodes (see Managing the palette). Live dashboards on this gateway are built in SCADash instead; Node-RED's role here is the data/integration layer feeding it, not the visualization layer.

A Modbus node shows an error or won't connect¶

• Confirm the PLC's IP address/serial port, port number, and unit ID match what's configured on the Modbus connection.
• Confirm the gateway can actually reach the PLC on the network — the Modbus connection is a plain TCP (or serial) link, independent of anything in Cockpit's Network settings, but still subject to them (routing, firewalling, cabling).
• Check Debug messages in the sidebar and the node's own status text under it on the canvas for the specific error.

I made changes but they don't seem to have taken effect¶

Check whether you actually clicked Deploy — see The editor → Deploy. Edits in the canvas are local to your browser until deployed.