Doing a RESTART now blows up everything! Just says reconnecting forever and I have to reinstall HA all over again.
If I RESTART before updating the configuration.yaml file the system restarts without a problem.
Also, before updating configuration.yaml I CAN access site on http://####.duckdns.org:8123 so I know that part is working.
You shouldn’t have to. If you have to specify port 8123, then you may not have it configured correctly. you have 443 from the outside directing to 8123 on the inside?
Is it possible to “install” double certificates?
Actually if I connect using duckdns httpS url all is ok. If I’m on local and try to connect using https://192.168.0.x:8123 i’m still connecting but I get browser warning about certificate.
I’d like to, when connect in local mode, not view this type of warning. I know I can ignore it… But if there is a workaround or the ability to add more than 1 certificate (one for duckdns and one for local)?
From what I have read you can do that with a local DNS like dnsmasq in add-ons, I haven’t tried it yet as I have the bigger issue of not being able to view https://mydomain.duckdns.org to solve first.
A ping of mydomain.duckdns.org from outside my network shows my network IP then a time out…
Any pointers how to debug this further?
Router is forwarding 443-8123 and has been restarted.
The bottom option, ports assigned externally, should both have 443 not 8123… you go to https://domain and that’s port 443 and forwards to 8123 internally
Thank you i’ve set it and it seem to work
Edit: after this, alexa and nodered stop working! I revert back to my old config port
Edit 2: ok i’ve modified nodered and haaska to work with new config 443->8123