DuckDNS configurator problem

Configuration
1

Hello all
Have scanned this forum (and others) for a solution without any luck, hope anyone can help me out because I really cant wrap my head around this. Trying to setup DuckDNS and got it to work but I have some remaining problems related to accsessing the configurator.
https://mydns.duckdns.org:8123 works flawlessly. When pressing the configurator panel i get a grey panel with message mydns.duckdns.org sent an invalid response (translated from swedish to english).
This is how my panel looks like in the configurator:

    panel_iframe:
      configurator:
        title: Configurator
        icon: mdi:wrench
        url: https://mydns.duckdns.org:3218

In a separate tab im not able to accsess the configurator with http**s**://mydns.duckdns.org:3218 but with http://mydns.duckdns.org:3218 I can.

Heres my configurator config:

{
  "username": "greatusername",
  "password": "greatpassword",
  "ssl": true,
  "certfile": "fullchain.pem",
  "keyfile": "privkey.pem",
  "allowed_networks": [
    "192.168.0.0/16",
    "172.30.0.0/16",
    "0.0.0.0/0"
  ],
  "banned_ips": [
    "8.8.8.8"
  ],
  "banlimit": 0,
  "ignore_pattern": [
    "__pycache__"
  ],
  "dirsfirst": false,
  "enforce_basepath": false,
  "notify_service": "persistent_notification.create"
}

Running version 0.84.6.

Any hint given in the right direction is greatly appreciated!

2

Your missing the single quotes; maybe that’s it?

panel_iframe:
  otherapp:
    title: 'Configurator'
    icon: mdi:wrench
    url: 'https://mydns.duckdns.org:3218' <--------------- missing it here
3

Try it with the IP address of your HA instance instead of using your duck dns url, I had the same issue but changing to the IP address fixed it for me (I also don’t have any single quotes so my instance is exactly like below)

panel_iframe:
      configurator:
        title: Configurator
        icon: mdi:wrench
        url: https://IP address of your HA:3218
4

Thanks for your replies,
Tried with and without single quotes, no difference. Also tried with my local HA ip, no difference.

Actually im starting to think theres something wrong with my portforwarding or maybe SSL certificate.
this is what my browser says when trying to access configurator with https://mydns.duckdns.org:

ERR_SSL_PROTOCOL_ERROR

Same goes with https://192.168.1.x
Sorry if that was unclear in my first post.

5

Then SSL does not work. The configurator by itself can not operate in both modes. So if plain http works, then it has trouble loading the certificate / private key. Have a look at the startup logs of the configurator. That might point you to where the problem is.

6

Got it to work!
What i did was the following. In configurator config i removed 192.168.0./16 and 172.30.0.0/16 from allowed_networks and restarted the configurator add-on.
This is how my config looks like now:

    {
      "username": "myusername",
      "password": "mypassword",
      "ssl": true,
      "certfile": "fullchain.pem",
      "keyfile": "privkey.pem",
      "allowed_networks": [
        "0.0.0.0/0"
      ],
      "banned_ips": [
        "8.8.8.8"
      ],
      "banlimit": 10,
      "ignore_pattern": [
        "__pycache__"
      ],
      "dirsfirst": false,
      "enforce_basepath": false,
      "notify_service": "persistent_notification.create"
    }

Those addresses i removed should not make any difference since i allow all networks with 0.0.0.0/0? If anyone has a clue what i just did, please share!

7

That was going to be my next suggestion :slight_smile: I changed mine as well after I couldn’t get into the configuration utility.