cant start on a fresh install as it is missing ssl cert

[MansM]

Problem/Motivation

After a fresh install (as in writen image to disk, booted it, waited, created user, installed zwave2mqtt plugin and hit start) it wont start because the log complains about missing SSL cert

Expected behavior

started addon

Actual behavior

not so started plugin

Steps to reproduce

pi3b+

1. write image to disk
2. booted it
3. wait for setup to complete
4. create user
5. installe zwave2mqtt plugin
6. hit start

Proposed changes

(If you have a proposed change, workaround or fix, describe the rationale behind it)

Log:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Hass.io Add-on: Z-Wave to MQTT
 Fully configurable Z-Wave to MQTT gateway and control panel
-----------------------------------------------------------
 Add-on version: 0.4.2
 You are running the latest version of this add-on.
 System: HassOS 3.7  (armv7 / raspberrypi3)
 Home Assistant version: 0.103.5
 Supervisor version: 193
-----------------------------------------------------------
 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... 
[14:46:54] FATAL: 
[14:46:54] FATAL: SSL has been enabled using the 'ssl' option,
[14:46:54] FATAL: this requires a SSL certificate file which is
[14:46:54] FATAL: configured using the 'certfile' option in the
[14:46:54] FATAL: add-on configuration.
[14:46:54] FATAL: 
[14:46:54] FATAL: Unfortunately, the file specified in the
[14:46:54] FATAL: 'certfile' option does not exists.
[14:46:54] FATAL: 
[14:46:54] FATAL: Please ensure the certificate file exists and
[14:46:54] FATAL: is placed in the Hass.io '/ssl/' directory.
[14:46:54] FATAL: 
[14:46:54] FATAL: In case you don't have SSL yet, consider getting
[14:46:54] FATAL: a SSL certificate or setting the 'ssl' option
[14:46:54] FATAL: to 'false' in case you are not planning on using
[14:46:54] FATAL: SSL with this add-on.
[14:46:54] FATAL: 
[14:46:54] FATAL: Check the add-on manual for more information.
[14:46:54] 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.

[addons-assistant[bot]]

: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.

[frenck]

So? Please read the error message.

Add-ons have a sane and secure default. If you don't wish to use SSL, that is up to you.

[MansM]

my suggestion is: put it in the install part of the docs... or generate a cert file

[frenck]

Certificate management is not part of add-ons, and are fetched from the Hass.io system if present. The option is documented.

[addons-assistant[bot]]

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.