Skip to main content

E62 — WS_DNS_RESOLVE_EMPTY

DNS resolution of the FKMTime server hostname returned no IPv4 addresses.

What happens​

The error is logged once per boot (subsequent failures in the same session are silently retried), the connection loop waits 1 second, and then retries the DNS lookup and WebSocket connection. The device keeps retrying indefinitely until it resolves the server address.

Possible causes​

  • The FKMTime server is not running or its mDNS advertisement has stopped.
  • The device's DNS resolver cannot reach the server — common on networks that do not support mDNS passthrough.
  • The device joined a different Wi-Fi network than the one the server is on.

How to fix​

  1. Verify the FKMTime server is running — Check the server process on the host machine.
  2. Check the Wi-Fi network — Ensure the device and server are on the same local network (not separated by VLANs or guest network isolation).
  3. Test mDNS on the network — Use an mDNS browser (e.g. Discovery - DNS-SD Browser on macOS/iOS, or avahi-browse -a on Linux) to check whether the FKMTime service is visible on the network.
  4. Configure a static server URL — If mDNS is unavailable, configure the device with the server's IP address directly.