This configuration.yaml again

Configuration
1

Last time with hassio I gave up. Now it’s the braver me trying again. Got most parts up but the remote thingy. It should all be set up correctly but DuckDNS add-on is complaining about:

INFO: Using main config file /data/workdir/config

ERROR: Lock file ‘/data/workdir/lock’ present, aborting.

and configuration.yaml is complaining about:

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

It looks like this (with two white spaces at everything below http):

http:
base_url: https://xxxxx.duckdns.org:8123
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem

Now I’ve tried everything I can think of… Probably something easy that I just can’t see.

Appreciate the help!

Thanks

F

2

Home Assistant uses a file named configuration.yaml It would ignore a file named config.yaml

There are normally instructions at the top of the forum page showing now to properly format configuration file pieces for this forum.

3

Sorry, i was lazy. It’s configuration.yaml :slight_smile:

Will edit my post as well…