DuckDNS not starting

Configuration
1

Running Hassio 75.1 and DuckDNS 1.5
Recently I am seeing duckDNS in the stop state, although it is set to auto start. Anyone facing similar issues?

1 Like
2

There is no ā€˜auto startā€™ option, only ā€˜start on bootā€™. This only starts the add-on when the host boots up.
If you experience the add-on stopping on itā€™s own, something else must be wrong.
Is there anything in the add-on or system logs indicating this?

3

This is the error I see

ERROR: Problem connecting to server (get for https://acme-v02.api.letsencrypt.org/directory; curl returned with 60)

4

Same here: I updated Duck DNS addon from v1.0 to 1.5. It will not start anymore.
I am on Hassio 0.69.1. Where did you find this error?

5

Found the issue, looks like my HA comes up 1st before the router after a powercut, since there is no internet its is not able to reach the url and duckdns fails to start.
to remedy I have disabled auto start duckdns and delay the start by 1 min after my HA comes up.

3 Likes
6

Hi ,
I have the same problem. please let me know how to delay start Duckdns . Iā€™m on Hassio 0.84.2

Thanks !

7

Setup an automation to add some delay when HA starts, below is what I have set

  • alias: Delay Duck DNS
    trigger:
    platform: homeassistant
    event: start
    action:
    • delay: 00:01:00
    • service: hassio.addon_restart
      data:
      addon: core_duckdns
1 Like
8

thanks for the reply. Iā€™m new to HA. add this to configuration.yaml file ?

9

how to add ā€œaddon: core_duckdnsā€ in automation ?

10

it should be in automation.yaml

11

i added an automation as you did but there is an error when ā€œcheck configā€ is run
see below

Configuration invalid

Invalid config for [automation]: [platform] is an invalid option for [automation]. Check: automation->platform. (See /config/configuration.yaml, line 91). Please check the docs at https://home-assistant.io/components/automation/

any help is much appreciated !

12

Hi Guys! I have the same problem. When i have a power outage, the problem is that my hassio starts first, and some minutes later, my internet router. Did you find another way than that in the automation yaml?

13

Thanks, this post helped me with DuckDNS not starting on boot after power failure. This automation syntax works so far but I have not simulated a full house power failure.

- alias: 'Delay_Duck_DNS'
  trigger:
    platform: homeassistant
    event: start
  action:
    - delay: 00:01:00
    - service: hassio.addon_restart
      data:
        addon: core_duckdns
  id: a4195fe6aef200b65
1 Like
14

d6065ab4-b5ec-4cee-b372-53fe4f9a8497

For everyone still searching for the solution to this problem. I wrote a detailled guide to the solution:

d6065ab4-b5ec-4cee-b372-53fe4f9a8497