I currently have to access my configurator via the port either on my local IP or through duckdns. I cannot access my device via hassio.local for some reason, which I believe is related to the problem. I have been trying to add in node-red to the panel as well, but it does not show up and just throws and error in my config file, but it flags something wrong with my groups! line, which is weird, but such is coding. Any way, here is my config file:
configuration:
panel_iframe:
configurator:
title: Configurator
icon: mdi:wrench
url: mydomain.duckdns.org:3218
# nodered:
# title: Node-RED
# icon: mdi:sitemap
# url: http://mydomain.duckdns.org:1880
and here is the configurator settings:
"username": "me",
"password": "pswd",
"ssl": false,
"certfile": "fullchain.pem",
"keyfile": "privkey.pem",
"allowed_networks": [
"0.0.0.0/0"
],
"banned_ips": [
"8.8.8.8"
],
"banlimit": 5,
"ignore_pattern": [
"__pycache__"
],
"dirsfirst": false,
"enforce_basepath": false,
"notify_service": "persistent_notification.create"
}
I had configurator originally set to hassio.local:3218 but I can’t access hassio.local anymore. Is there something I need to set in my router? And is there a way I can set it to be able to be accessible from duckdns as well? I had to set the allowed networks to 0.0.0.0/0 be able to access it from mydomain.duckdns.org:3218 but I still don’t know how you would set it up to access it via the panel through duckdns.
my node-red config:
"log_level": "info",
"credential_secret": "xxxxxxx",
"http_node": {
"username": "xxxxxx",
"password": "xxxxx"
},
"http_static": {
"username": "xxxxxxxx",
"password": "xxxxxx"
},
"port": 1880,
"ssl": false,
"certfile": "fullchain.pem",
"keyfile": "privkey.pem",
"require_ssl": false,
"system_packages": [],
"npm_packages": [],
"init_commands": []
}