- docs
- FlowFuse User Manuals
- Using FlowFuse
-
- Getting Started
- Static asset service
- Bill of Materials
- FlowFuse Concepts
- Instance States
- Changing the Stack
- Custom Hostnames
- Custom Node Packages
- DevOps Pipelines
- Environment Variables
- FlowFuse Expert
- FlowFuse File Nodes
- FlowFuse MQTT Nodes
- FlowFuse Project Nodes
- FlowFuse Tables
- Groups
- High Availability mode
- HTTP Access Tokens
- Instance Settings
- Logging
- persistent-context
- Role-Based Access Control
- Shared Team Library
- Snapshots
- Team Broker
- Teams
- User Settings
- FlowFuse API
- Migrating a Node-RED project to FlowFuse
- Device Agent
- Device Agent
- Hardware Guides
- FlowFuse Cloud
- FlowFuse Cloud
- FlowFuse Self-Hosted
- Quick Start
- Installing FlowFuse
- Upgrading FlowFuse
- Administering FlowFuse
- Support
- Community Support
- Premium Support
- Debugging Node-RED issues
- Contributing
- Contributing to FlowFuse
Node-RED Safe Mode
When a Node-RED instance is unresponsive, for example due to an infinite loop, it can be put into Safe Mode.
- Edit the instance's Environment Variables
- Add a variable called
NODE_RED_ENABLE_SAFE_MODEtotrue. - Save the changes then suspend/restart the instance.
When starting up in Safe Mode, Node-RED will provide access to the editor without starting the flows. You can log in to the editor, make any necessary changes and then deploy to restart the flows.
Once recovered you should delete the NODE_RED_ENABLE_SAFE_MODE environment variable to prevent it entering Safe Mode the next time it is restarted.
Updated: 11 May, 2026
