Describe the issue you are experiencing
Watchdog is on however it doesn't work in that scenario.
A few minutes without internet connection makes HA unavailable from WAN as new IP isn't delivered do duckdns service.
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which app are you reporting an issue with?
Duck DNS
What is the version of the app?
2.0.0
Steps to reproduce the issue
...
System Health information
System Information
| version |
core-2026.4.3 |
| installation_type |
Home Assistant OS |
| dev |
false |
| hassio |
true |
| docker |
true |
| container_arch |
amd64 |
| user |
root |
| virtualenv |
false |
| python_version |
3.14.2 |
| os_name |
Linux |
| os_version |
6.12.77-haos |
| arch |
x86_64 |
| timezone |
Europe/Warsaw |
| config_dir |
/config |
Home Assistant Community Store
| GitHub API |
ok |
| GitHub Content |
ok |
| GitHub Web |
ok |
| HACS Data |
ok |
| GitHub API Calls Remaining |
5000 |
| Installed Version |
2.0.5 |
| Stage |
running |
| Available Repositories |
2997 |
| Downloaded Repositories |
18 |
Home Assistant Cloud
| logged_in |
false |
| can_reach_cert_server |
ok |
| can_reach_cloud_auth |
ok |
| can_reach_cloud |
ok |
GIOŚ
Home Assistant Supervisor
| host_os |
Home Assistant OS 17.2 |
| update_channel |
stable |
| supervisor_version |
supervisor-2026.04.0 |
| agent_version |
1.8.1 |
| docker_version |
29.3.1 |
| disk_total |
229.2 GB |
| disk_used |
69.5 GB |
| nameservers |
192.168.2.1, 192.168.2.251 |
| healthy |
true |
| supported |
true |
| host_connectivity |
true |
| supervisor_connectivity |
true |
| ntp_synchronized |
false |
| virtualization |
|
| board |
generic-x86-64 |
| supervisor_api |
ok |
| version_api |
ok |
| installed_addons |
Matter Server (8.4.0), Get HACS (1.3.1), File editor (6.0.0), Mosquitto broker (7.0.1), Terminal & SSH (10.1.0), Meross Local Broker Addon (0.0.1-alpha50), ESPHome Device Builder (2026.4.0), Duck DNS (2.0.0), MariaDB (2.7.2) |
Dashboards
| dashboards |
8 |
| resources |
11 |
| views |
22 |
| mode |
storage |
Network Configuration
| adapters |
lo (disabled), enp1s0 (enabled, default, auto), docker0 (disabled), hassio (disabled), veth903d9fb (disabled), veth09abb04 (disabled), veth8d55908 (disabled), veth1a09771 (disabled), veth52de570 (disabled), veth2a4f9b4 (disabled), veth7c5332b (disabled), vethbfd8d18 (disabled), vethe0b37dd (disabled), vethaa33f38 (disabled), veth7c12c15 (disabled) |
| ipv4_addresses |
lo (127.0.0.1/8), enp1s0 (192.168.2.201/24), docker0 (172.30.232.1/23), hassio (172.30.32.1/23), veth903d9fb (), veth09abb04 (), veth8d55908 (), veth1a09771 (), veth52de570 (), veth2a4f9b4 (), veth7c5332b (), vethbfd8d18 (), vethe0b37dd (), vethaa33f38 (), veth7c12c15 () |
| ipv6_addresses |
lo (::1/128), enp1s0 (fe80::ab83:eddb:889d:6a0c/64), docker0 (fe80::2087:faff:feef:bfe4/64), hassio (fd0c:ac1e:2100::1/48, fe80::38ff:97ff:febb:7125/64), veth903d9fb (fe80::34b8:a0ff:fe7a:e12f/64), veth09abb04 (fe80::9c15:e5ff:fed3:5f9f/64), veth8d55908 (fe80::b86f:4ff:fe2b:82ed/64), veth1a09771 (fe80::d87b:40ff:fe40:bc7c/64), veth52de570 (fe80::4424:d7ff:fef5:7b1f/64), veth2a4f9b4 (fe80::d094:64ff:fe5c:175b/64), veth7c5332b (fe80::a447:adff:feb2:85cc/64), vethbfd8d18 (fe80::8890:56ff:fefb:f7c2/64), vethe0b37dd (fe80::10c4:9bff:fe7d:919e/64), vethaa33f38 (fe80::948b:55ff:fe12:e300/64), veth7c12c15 (fe80::9055:bdff:fefd:abca/64) |
| announce_addresses |
192.168.2.201, fe80::ab83:eddb:889d:6a0c |
Recorder
| oldest_recorder_run |
13 kwietnia 2026 18:55 |
| current_recorder_run |
18 kwietnia 2026 17:32 |
| estimated_db_size |
1669.44 MiB |
| database_engine |
mysql |
| database_version |
10.11.6 |
Anything in the Supervisor logs that might be useful for us?
Anything in the app logs that might be useful for us?
ERROR: Problem connecting to server (get for https://acme-v02.api.letsencrypt.org/directory; curl returned with 6)
EXPECTED value GOT EOF
[17:00:33] INFO: Service duckdns exited with code 1 (by signal 0)
Additional information
No response
Describe the issue you are experiencing
Watchdog is on however it doesn't work in that scenario.
A few minutes without internet connection makes HA unavailable from WAN as new IP isn't delivered do duckdns service.
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which app are you reporting an issue with?
Duck DNS
What is the version of the app?
2.0.0
Steps to reproduce the issue
...
System Health information
System Information
Home Assistant Community Store
Home Assistant Cloud
GIOŚ
Home Assistant Supervisor
Dashboards
Network Configuration
Recorder
Anything in the Supervisor logs that might be useful for us?
Anything in the app logs that might be useful for us?
Additional information
No response