Duck DNS Crashes when added to configuration.yaml

Configuration
1

Hi, I added a Duck DNS to my (hash.io hassos_rpi2-2.10) clear setup, only configurator addon added. I did step by step, as on this video https://www.youtube.com/watch?v=VUTPAoB27iQ
I added duckdns, created account, changed forwarding added token atc, and started it, than in Log was written " Done! "
Than I added these lines in configuration.yaml same as on video time 3:45 :

http:
  base_url: https://xxxxxxx.duckdns.org:8123
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem

And now the Home Assistant doesnt work, I cant connect to it using local ip and DuckDNS, when I change the yaml file back using by congifurator in browser, after rebooting it, it boot back as before :exploding_head:
What should I do to make it work ?

Error Log:
https://justpaste.it/7s8g3

2

Please elaborate.

You can’t connect to it using your DuckDNS URL, or local IP?

Can you connect remotely from outside your network?

What do the logs say?

1 Like
3

DuckDNS and local IP doesnt work.
I will try to get the report and poste it here.
(I added it into the main post.)

4

Please try following the official Hassio instructions and report back.

1 Like
5

I also tried that, now I noticed this
“Restart Home Assistant for the configured changes to take effect. When you access the Home Assistant frontend you will now need to use https , even when accessing local instances, for example at https://192.168.0.1:8123 .”
For me the ip never worked, my hassio has this ip : 192.168.0.103:8123 I use it for tasmota mqtt and it works.
But I always used hassio.local:8123 because its only way I can connect to my HA
I will check the log, post it here, and try it again.

Or hassio.local:8123 should still work with Duck installed ?
Also I wonder why configurator addon still work even I cant enter the HA.

6

You would need to use https://hassio.local:8123 and you will get a certificate error because the ssl certificate does not have hassio.local in it. Using the outside name avoids that.

1 Like
7

https://justpaste.it/7s8g3

8

I just reinstall it many times and now, I have just this error, and local connection seems to work as fine.

2019-03-12 22:01:20 ERROR (MainThread) [homeassistant.components.device_tracker] Unable to load /config/known_devices.yaml: Config file not found: /config/known_devices.yaml

The duck dns doesnt work for me, the log seems to by ok:

INFO: Using main config file /data/workdir/config

  • Account already registered!
    Tue Mar 12 21:48:01 CET 2019: OK
    78.108.97.57
    NOCHANGE

INFO: Using main config file /data/workdir/config

Processing xxxx.duckdns.org

  • Checking domain name(s) of existing cert… unchanged.
  • Checking expire date of existing cert…
  • Valid till Jun 10 19:20:39 2019 GMT Certificate will not expire
    (Longer than 30 days). Skipping renew!
    Tue Mar 12 21:53:13 CET 2019: OK
    xxxxxxxxx
    NOCHANGE
    Tue Mar 12 21:58:14 CET 2019: OK
    xxxxxxxxx
    NOCHANGE
9

The main problem was solved, the others is different problem :slight_smile: thank you

10

@xxgmxxI wish you’d share your results and what worked in the end. I experience the exact same symptoms as you, and if you shared your solution it would help the whole community and all us struggling with this problem.

11

Hi, sorry for replying this late. It has been quite some time and I think the only problem was not using the https:// If I use http:// I get the same error I originally mentioned. So just try using https:// with your IP, try not to use https://hassio.local:8123 It was the main problem for me, that this no longer works for me. I was used to use it, but not anymore since it stopped working. Try the https:// with IP or the duckdns.

12

Had the same issue. But using HTTPS://IP:8123 doesn’t work… it tries but never connects. Can anyone help?

13

Had to connect the raspberry with ethernet cable and it worked.