New Node Red Install Fails On Start

Third party integrations Node-RED
1

Hey folks - I have a pretty fresh HAOS install and installed NodeRed. When I try to start it with all defaults and no out of the box customization, it fails to launch. This is in the log. I looked in the description and I see configuration attributes, but there was nothing on basic install that said required that I expected to be required to support a basic install. Did I miss a required step?

s6-rc: info: service nodered: starting
[11:08:27] FATAL: is placed in the ‘/ssl/’ directory.
[11:08:27] FATAL:
s6-rc: info: service nodered successfully started
[11:08:27] FATAL: In case you don’t have SSL yet, consider getting
[11:08:27] FATAL: an SSL certificate or setting the ‘ssl’ option
[11:08:27] FATAL: to ‘false’ in case you are not planning on using
[11:08:27] FATAL: SSL with this add-on.
[11:08:27] FATAL:
[11:08:27] FATAL: Check the add-on manual for more information.
[11:08:27] FATAL:
s6-rc: warning: unable to start service init-nginx: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service nodered: stopping
[11:08:27] INFO: Service Node-RED exited with code 256 (by signal 15)
s6-rc: info: service nodered successfully stopped
s6-rc: info: service init-nodered: stopping
s6-rc: info: service init-nodered successfully stopped
s6-rc: info: service init-customizations: stopping
s6-rc: info: service init-customizations successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

Add-on: Node-RED
Flow-based programming for the Internet of Things

Add-on version: 17.0.13
You are running the latest version of this add-on.
System: Home Assistant OS 12.3 (amd64 / generic-x86-64)
Home Assistant Core: 2024.5.5
Home Assistant Supervisor: 2024.05.1

Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.

s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-customizations: starting
s6-rc: info: service init-customizations successfully started
s6-rc: info: service init-nodered: starting
[11:08:30] FATAL:
[11:08:30] FATAL: SSL has been enabled using the ‘ssl’ option,
[11:08:30] FATAL: this requires an SSL certificate file which is
[11:08:30] FATAL: configured using the ‘certfile’ option in the
[11:08:30] FATAL: add-on configuration.
[11:08:30] FATAL:
[11:08:30] FATAL: Unfortunately, the file specified in the
[11:08:30] FATAL: ‘certfile’ option does not exist.
[11:08:30] FATAL:
[11:08:30] FATAL: Please ensure the certificate file exists and
[11:08:30] FATAL: is placed in the ‘/ssl/’ directory.
[11:08:30] FATAL:
s6-rc: info: service init-nodered successfully started
s6-rc: info: service nodered: starting
[11:08:30] FATAL: In case you don’t have SSL yet, consider getting
s6-rc: info: service nodered successfully started
[11:08:30] FATAL: an SSL certificate or setting the ‘ssl’ option
[11:08:30] FATAL: to ‘false’ in case you are not planning on using
[11:08:30] FATAL: SSL with this add-on.
[11:08:30] FATAL:
[11:08:30] FATAL: Check the add-on manual for more information.
[11:08:30] FATAL:
s6-rc: warning: unable to start service init-nginx: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service nodered: stopping
[11:08:30] INFO: Service Node-RED exited with code 256 (by signal 15)
s6-rc: info: service nodered successfully stopped
s6-rc: info: service init-nodered: stopping
s6-rc: info: service init-nodered successfully stopped
s6-rc: info: service init-customizations: stopping
s6-rc: info: service init-customizations successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

2

Is SSL on in the Node Red Configuration tab?

3

Oh - yikes. Yes. That defaults to on. I flipped it off and that made it start. Do I lose any security by turning it off if it’s all running on box? And/or got a link to simple steps to configuring it and grabbing a cert to protect?

4

SSL settings are at your discretion and documentation can be found on the Node Red Documentation tab.