That depends wether your router/modem supports nat loopback.
First thing to do is add https:// in front of your ip address.
go https://internal.ip.addres:port
That should help us make sure that everythning is working ok
(If that doesnt work, try pinging the device, to see if it responds)
Second, use your mobile phone (with 3g data) or have a friend outside your lan hit up your duckdns address again with httpS
https://yourname.duckdns.org:port and see if everything works
Then if both the above work, you have several choices.
Access hassio from the internal ip address whenever you are home and the external whenever you are out.
Check if your modem supports NAT loopback (which will translate the external ip addres into internal) so you can access hassio from the same shrotcut where ever you are.
Other workarounds, like getting another modem, using a DNSmasq (or pihole) addon on hassio which will do what your router couldnt or edit the hosts file on your pc accordingly
Let us know if the httpS thingy worked and we ll see how we go on from there
Also, in contrast to what @dap35 suggested, my configuration includes the port number:
A had similar case. The issue was on second firewall from my providers side. So there was firewall on router (443 was opened by mapping to 8123), but firewall from router was enabled and all ports were closed. That was pretty strange…
Ofcourse! How could i forget that (thanks for reminding me )
The log points to configuration.yaml:
2018-12-05 21:57:23 ERROR (SyncWorker_0) [homeassistant.util.yaml] while scanning a simple key
in “/config/configuration.yaml”, line 106, column 1
could not find expected ‘:’
in “/config/configuration.yaml”, line 107, column 3
2018-12-05 21:57:23 ERROR (MainThread) [homeassistant.bootstrap] Error loading /config/configuration.yaml: while scanning a simple key
in “/config/configuration.yaml”, line 106, column 1
could not find expected ‘:’
in “/config/configuration.yaml”, line 107, column 3