Getting this error message when checking config

Installation Home Assistant OS
1

Hi, I had HA hassio working then I broke it tweaking with one of the .yaml files. I started from scratch and now can’t get back up and running. Here is the error message I’m getting when checking configuration.

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 29). Please check the docs at https://home-assistant.io/components/http/

-Keith

2

I’ll assume that you did put quotes around the file path, but without an excerpt from your configuration, this is only a guess.

3

Hello, I have followed several examples. Can you post an example?

-Keith

4

Show us the relevant part of your configuration.yaml, where you configure the http component …

5

Here are the excerpts for configuration.yaml DuckDNS config and Let’s Encrypt config.

configuration.yaml entry:
http:
base_url: https://myname.duckdns.org:8123
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem

Secrets are defined in the file secrets.yaml

api_password: !secret http_password

DuckDNS config:
{
“lets_encrypt”: {
“accept_terms”: true,
“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”
},
“token”: “my token”,
“domains”: [
“myname.duckdns.org”
],
“seconds”: 300
}

Let’s Encrypt config:
{
“email”: null,
“domains”: [
null
],
“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”
}

6

The DuckDNS add-on takes care of both the dynamic DNS stuff and the certificate - so you do not need the Lets-Encrypt add-on.

7

Thanks for your input… I’m not sure why I’m getting an error when checking config.

8

I finally figured out the problem…
Check config does not seem to catch syntax issues in customize.yaml.
It allows duplicate names and which after a pi restart bad things happen.