tomspark wrote:
This isn't the updater itself — it's host DNS. Could not resolve host: get.tomsparkbox.com (Timeout while contacting DNS servers) means the box can't resolve anything; the update just happens to be where you hit it. Given your Pi-hole port-53 thread, I'd bet these are the same root cause — a half-up Pi-hole or a confused systemd-resolved on WSL2 leaves the host with no working resolver. On the box: cat /etc/resolv.conf then nslookup get.tomsparkbox.com (or curl -v https://get.tomsparkbox.com). If nslookup also fails, DNS is broken host-wide; quickest unblock is temporarily putting a real resolver (nameserver 1.1.1.1 in /etc/resolv.conf) so the update can pull, then fixing the Pi-hole/53 conflict so it sticks. Let's keep the actual DNS fix in the port-53 thread — sort that one and this clears with it.