Node-RED: Safe Mode: Resolve Node-RED Flows Errors (502 Error)

This documentation is part of the Getting Started guide. You can view the complete guide here: How to Get Started with Node-RED.

Welcome to the Stackhero documentation

Stackhero offers a fully managed Node-RED cloud environment designed to help you build workflows quickly:

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

You can have a secure, production-ready Node-RED cloud hosting instance up and running in about 5 minutes. Stackhero takes care of installation, updates, and infrastructure so you can focus on building your 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.