From c2908824921b0886966b1831f6f73742ad829f71 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Murat=20=C3=96ZDEM=C4=B0R?= Date: Fri, 26 Jun 2026 23:54:20 +0300 Subject: [PATCH] fix(monitoring): add missing conditions array to DNS monitors Uptime Kuma 1.23+ evaluates monitor.conditions.length internally. While HTTP monitors seem to bypass this check safely if conditions is null, DNS monitors crash the NodeJS backend with 'Cannot read properties of null (reading length)' if conditions is not explicitly initialized as an empty array. --- health-agent/scripts/setup_uptime_kuma.py | 2 ++ 1 file changed, 2 insertions(+) diff --git a/health-agent/scripts/setup_uptime_kuma.py b/health-agent/scripts/setup_uptime_kuma.py index 65b0726..d34830c 100644 --- a/health-agent/scripts/setup_uptime_kuma.py +++ b/health-agent/scripts/setup_uptime_kuma.py @@ -265,6 +265,7 @@ def setup_uptime_kuma(dry_run=False, only=None): "dns_resolve_type": dns_resolve_type, "interval": interval, "url": "https://", + "conditions": [], } if parent_group_id is not None: kwargs["parent"] = parent_group_id @@ -286,6 +287,7 @@ def setup_uptime_kuma(dry_run=False, only=None): "dns_resolve_type": dns_resolve_type, "interval": interval, "url": "https://", + "conditions": [], } if parent_group_id is not None: kwargs["parent"] = parent_group_id