Node-RED: Safe mode: resolve Node-RED flows errors (502 error)

This documentation is part of the Getting started guide. View the full guide here: How to get started with Node-RED.

Welcome to the Stackhero documentation

Stackhero provides a fully managed Node-RED cloud environment designed to get you building workflows quickly:

• Built-in MQTT server (Mosquitto) for seamless IoT integration.
• Full access to the Node-RED admin UI for managing flows and settings.
• Node-RED Dashboard included for real-time visualization.
• Dedicated SMTP email server included, with no limits on sending.
• Effortless one-click updates to keep your instance current.
• Custom domain names with automatic HTTPS: for example, https://node-red.your-company.com.
• High performance and strong security with private, dedicated infrastructure.

You can have a secure, production-ready Node-RED cloud hosting instance running in about 5 minutes. Stackhero handles setup, updates, and infrastructure so you can focus on building automations.

If you encounter a 502 error when accessing your admin dashboard, start by checking your instance logs. You can find these logs in the Stackhero dashboard under the "Logs" tab after selecting your Node-RED service.

The logs may contain Node-RED errors that prevent it from starting correctly. Collect as much information as possible to help debug your flows.

After reviewing your logs, go to your service configuration in the Stackhero dashboard and enable the "Safe mode" option. In safe mode, Node-RED will restart without automatically starting your flows.

This allows you to access the admin dashboard, fix your flow errors, and deploy your changes. Once everything is working smoothly, remember to disable safe mode in your service configuration so that your flows start automatically on Node-RED restart.