hassio-addons/addon-node-red

docker ssl error #620

madman43 posted onGitHub

20-07-16 08:59:28 INFO (SyncWorker_3) [supervisor.docker.addon] Start Docker add-on hassioaddons/node-red-aarch64 with version 7.0.0 20-07-16 08:59:33 INFO (MainThread) [supervisor.api.security] /host/info access from a0d7b954_nodered 20-07-16 08:59:40 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.32.1:62153 ssl:None [Connection refused] 20-07-16 08:59:49 INFO (SyncWorker_2) [supervisor.docker.interface] Clean addon_a0d7b954_nodered application 20-07-16 08:59:55 INFO (SyncWorker_2) [supervisor.docker.addon] Start Docker add-on hassioaddons/node-red-aarch64 with version 7.0.0 20-07-16 09:00:00 INFO (MainThread) [supervisor.api.security] /host/info access from a0d7b954_nodered 20-07-16 09:00:08 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.32.1:62153 ssl:None [Connection refused] 20-07-16 09:02:20 INFO (SyncWorker_0) [supervisor.docker.interface] Clean addon_a0d7b954_nodered application 20-07-16 09:02:22 INFO (MainThread) [supervisor.ingress] Update Ingress as panel for a0d7b954_nodered 20-07-16 09:02:23 ERROR (MainThread) [supervisor.utils] Can't execute run while a task is in progress


:wave: Thanks for opening your first issue here! If you're reporting a :bug: bug, please make sure you include steps to reproduce it. Also, logs, error messages and information about your hardware might be useful.

posted by addons-assistant[bot] almost 5 years ago

Please provide system details on your setup. Thanks!

posted by frenck almost 5 years ago

1 2 3 4

posted by madman43 almost 5 years ago

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


Add-on version: 7.0.0 You are running the latest version of this add-on. System: null (aarch64 / qemuarm-64) Home Assistant Core: 0.112.4 Home Assistant Supervisor: 230


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


[cont-init.d] 00-banner.sh: exited 0. [cont-init.d] 01-log-level.sh: executing... [cont-init.d] 01-log-level.sh: exited 0. [cont-init.d] nginx.sh: executing... [18:48:45] FATAL: [18:48:45] FATAL: SSL has been enabled using the 'ssl' option, [18:48:45] FATAL: this requires a SSL certificate file which is [18:48:45] FATAL: configured using the 'certfile' option in the [18:48:45] FATAL: add-on configuration. [18:48:45] FATAL: [18:48:45] FATAL: Unfortunately, the file specified in the [18:48:45] FATAL: 'certfile' option does not exists. [18:48:45] FATAL: [18:48:45] FATAL: Please ensure the certificate file exists and [18:48:45] FATAL: is placed in the '/ssl/' directory. [18:48:45] FATAL: [18:48:45] FATAL: In case you don't have SSL yet, consider getting [18:48:45] FATAL: a SSL certificate or setting the 'ssl' option [18:48:45] FATAL: to 'false' in case you are not planning on using [18:48:45] FATAL: SSL with this add-on. [18:48:45] FATAL: [18:48:45] FATAL: Check the add-on manual for more information. [18:48:45] FATAL: [cont-init.d] nginx.sh: exited 1. [cont-finish.d] executing container finish scripts... [cont-finish.d] 99-message.sh: executing...


            Oops! Something went wrong.

We are so sorry, but something went terribly wrong when starting or running this add-on.

Be sure to check the log above, line by line, for hints.

[cont-finish.d] 99-message.sh: exited 0. [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting.

posted by madman43 almost 5 years ago

Please read the logs you just posted.

Thanks 👍

posted by frenck almost 5 years ago

Closed ssl still like this

posted by madman43 almost 5 years ago

@madman43

[18:48:45] FATAL: SSL has been enabled using the 'ssl' option,
[18:48:45] FATAL: this requires a SSL certificate file which is
[18:48:45] FATAL: configured using the 'certfile' option in the
[18:48:45] FATAL: add-on configuration.
[18:48:45] FATAL:
[18:48:45] FATAL: Unfortunately, the file specified in the
[18:48:45] FATAL: 'certfile' option does not exists.
[18:48:45] FATAL:
[18:48:45] FATAL: Please ensure the certificate file exists and
[18:48:45] FATAL: is placed in the '/ssl/' directory.
[18:48:45] FATAL:
[18:48:45] FATAL: In case you don't have SSL yet, consider getting
[18:48:45] FATAL: a SSL certificate or setting the 'ssl' option
[18:48:45] FATAL: to 'false' in case you are not planning on using
[18:48:45] FATAL: SSL with this add-on.
[18:48:45] FATAL:
[18:48:45] FATAL: Check the add-on manual for more information.

It is written there... ☝️ In your log. Read it.

posted by frenck almost 5 years ago

Fund this Issue

$0.00
Funded

Pull requests