Setting up letsencrypt

Installation Home Assistant OS
1

Having problems , receiving this message

2017-07-26 20:25:47 ERROR (MainThread) [homeassistant.config] Invalid config for [http]: not a file for dictionary value @ data[‘http’][‘ssl_certificate’]. Got ‘/ssl/fullchain.pem’
not a file for dictionary value @ data[‘http’][‘ssl_key’]. Got ‘/ssl/privkey.pem’. (See /config/configuration.yaml, line 24). Please check the docs at https://home-assistant.io/components/http/

http:
  # Uncomment this to add a password (recommended!)
  api_password: xxx
  # Uncomment this if you are using SSL or running in Docker etc
  base_url: xxx.duckdns.org:8123
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem
2

this in option

{
“challenge”: “https”,
“email”: “[email protected]”,
“domains”: [
“xxx.duckdns.com”,
“xxx.duckdns.com”,
“xxx-mqtt.duckdns.org”,
“xxx-synology.duckdns.org”,
“xxx-qnap3.duckdns.org”
],
“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”
}

3

Duckdns.com ??

4

I had this problem at first too, the error “not a file for dictionary value” means it can’t find the files at the path you specified.

for me this was concurring because the Let’sEncrypt addin was not able to validate my domain and create the keys for me. you need to have port 80 and 443 forwarded to 80 and 443 on your HASS.io device, not 8123 (i had this set up for a previous install and it caused issues). The Let’sEncrypt addin appears to open ports 80/443 when you start it so that Let’sEncrypt can validate your domain and download certs.

check the Logs section of the Let’sEncrypt addin and see if it’s failing for some reason.

5

yes I did that before installing it. Now I am back to HASSBIAN, next time I will check

6

I set LE up following Bruh’s video on the AIO installer.
It has been working great since December. The port forwarding left open AFTER cert validation is 443 forwarding to 8123. Are you saying with HASS.IO / LE add-on that the port forwarding needs to remain as 443 to 443 even after install? Is this because it renews automatically after 60 days?

7

Letsencrypt has driven me crazy every time I’ve tried to set it up. Makes me feel stupid.

I have set it up with the following config in admin:

{ "challenge": "https", "email": "**.**@gmail.com", "domains": [ "random.duckdns.org" ], "certfile": "fullchain.pem", "keyfile": "privkey.pem" }

and in the config file

http: api_password: random base_url: random.duckdns.org:8123 ssl_certificate: /ssl/fullchain.pem ssl_key: /ssl/privkey.pem

I know it fetched the certificate, but to a different path according to the logs (dont have them any more) so i guess that the paths in the docs are symlinks.

Still, it breaks home-assistant when i restart it.

8

so, u cant run emulated hue on port 80 for google home? even if u temporarily disable emulated hue for first time run, the renewal process after 60 days still need port 80 ?

9

hey guys hope someone can help me i got duckdns setup and now im about to install lestencript add-on
after intall and putting my info here what should be on the yaml file? and do i have to stop all add-on runing before hitting the star button? thanks

    {
      "challenge": "https",
      "email": "[email protected]",
      "domains": ["my.duckdns.org"]
    }