Configurator access with Duckdns

Well you should bloody ask then!!

Here is my config…

{
  "username": "my-user-name-here",
  "password": "my-password-here",
  "ssl": false,
  "certfile": "fullchain.pem",
  "keyfile": "privkey.pem",
  "allowed_networks": [
    "172.30.0.0/16"
  ],
  "banned_ips": [
    ""
  ],
  "banlimit": 5,
  "ignore_pattern": [
    "__pycache__"
  ],
  "dirsfirst": true,
  "enforce_basepath": false,
  "notify_service": "persistent_notification.create",
  "sesame": "secret-sesame-here"
}

Then it’s accessed like this:
https://domain.duckdns.org:3218/secret-sesame-here

If you want to, I have a blog entry here on using the Caddy add-on and securing Home Assistant and configuring this. Take a look.

sweet, got Sesame all up and running too.

now to get stuck into making some of this stuff actually work

thanks David so much for all your help getting me set up!

1 Like

Something happened to my Configurator since last update, I can only access it via the Add-On “Open WebUI” link, but when I click on the shortcut in the left pan menu I get an error: myplace.duckdns.org refused to connect.

Did you have a look at the numerous threads regarding the configurator with recent activity? You’ll find explanations and solutions there. :+1:

The Configurator add-on now has Ingress suppport. You now can edit files remotely from within Home Assistant!