node-red

To restart Node-RED after deploying flows, use the service management commands for your environment (systemd, PM2, or Docker) to stop and start the runtime, then verify the service status to ensure the new flows are active.

Node-RED flow persistence failures after a restart typically stem from incorrect deployment commands or configuration issues. You need to properly export and back up flows, then ensure the runtime service correctly loads the saved flow file upon startup.

Yes, you can manage palette node installations across Docker environments. The Skill assists with adding, removing, and configuring palette nodes within your Node-RED instance, ensuring modules resolve correctly and persist across container restarts.

Troubleshooting Node-RED module resolution and port accessibility errors involves checking the runtime configuration, verifying service status across systemd or Docker, and reviewing debug logs to identify missing dependencies or port conflicts blocking the automation runtime.

Yes, managing Node-RED instances under PM2 is fully supported. You can check service status, deploy flows, and configure settings for Node-RED automation runtimes specifically orchestrated through the PM2 process manager.

To back up Node-RED flows before configuration changes, use the flow operations to export your current flow configuration to a file. This ensures you can import and restore the previous flow state if debugging or palette installation causes issues.