SSL Configurator and DuckDNS

Configuration
1

Just bought another RPI to set up HA, very eager and slightly frustrated so far.

So I’ve tried to find other posts about this. Maybe I have but I just didn’t understand…

DuckDNS is set up and after reinstalling it, everything works as it should, according to the log anyway.

Now comes where I’m stuck. Even if DuckDNS is installed and ok, I can’t access it through mydomain.duckdns.org. I’ve forwarded 443 to 8213 and 3218 to 3218( for Configurator).

When I try to access the duckdns url, I still end up viewing my routers (google wifi) welcome page. It’s close, but I’m stuck.

Problem two (probably related…) is with the Configurator. I get these error messages:

Configuration invalid CHECK CONFIG
Component not found: base_url
Component not found: ssl_key
Component not found: ssl_certificate

In configurator it looks like this:

“username”: “xxxx”,
“password”: “xxxx”,
“ssl”: true,
“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”,
“allowed_networks”: [
“192.168.0.0/16”,
“172.30.0.0/16”

and

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

So before I actually start to set things up, I want thee basics done.

It’s probably and easy fix but I’m out of options here…

Thanks in advance!

S

2

You should properly format your config (link at the top of every site here at the forum). However, judging by the error messages you’r configuration.yaml is not properly indented. If it really looks exactly like the part of it you have posted, that that’s invalid yaml. The whitespace in front of all those options it important. So instead your config should look more like this:

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

Notice, that the indentation tells the software, that base_url etc. are children of the http-section.

3

Thanks a lot! The whitespace did it! :slight_smile: Woho :slight_smile: