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 ready-to-use Node-RED cloud solution that provides a host of benefits, including:

• MQTT server included (Mosquitto).
• Full access to Node-RED admin UI.
• Node-RED Dashboard included.
• Unlimited and dedicated SMTP email server included.
• Effortless updates with just a click.
• Customizable domain name secured with HTTPS (for example, https://node-red.your-company.com).
• Optimal performance and robust security powered by a private and dedicated VM.

Save time and simplify your life: it only takes 5 minutes to try Stackhero's Node-RED cloud hosting solution!

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.