New installation : Docker Let's encrypt

Hello everyone,

i just migrate to HASS this week, importing my zwave network with my key and everything is going well.

I use a tutorial to install HASS in a docker container, in my provider’s box using a virtual Debian machine.

So far everything is running, i try now to open my installation to the outside in a secure manner.
creating a * domain. Redirect port 80 to 80 and port 443 to port 8123. Installing let’s encrypt.

My options :

email: ***

  • ***
    certfile: fullchain.pem
    keyfile: privkey.pem
    challenge: http
    dns: {}

I get certificates i think :

[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] executing…
[cont-init.d] exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[12:24:47] INFO: Selected http verification
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator standalone, Installer None
Cert not yet due for renewal
Keeping the existing certificate

Certificate not yet due for renewal; no action taken.

[cont-finish.d] executing container finish scripts…
[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.

What do i need to do after this step ? When i try to connect via https, there is a SSL_ERROR_RX_RECORD_TOO_LONG message.

Thank you so much for your help guys.


Did you configure HA to use those certificates?

No, how can i do that ?

Thanks a lot.

That’s handled by either your proxy server (if you want to use plain http locally), or the http integration (at which point you have to use the full domain name and SSL all the time.

  ssl_certificate: /path/to/fullchain.pem
  ssl_key: /path/to/privkey.pem