Docs / Common problems
This page separates real failures from wrong expectations. NodalDesk touches network, capture, audio, input and system permissions; it helps to look at the symptom in parts.
NodalDesk discovers hosts via UDP broadcast on port 19876. Check that host
and client are on the same network, that the host is running, and that the firewall
isn't blocking discovery or the host's port.
The web client requires WebCodecs. Use an up-to-date Chrome, Edge or Opera. If the browser doesn't support WebCodecs, the web client may load but not render video correctly.
That's correct in the current state. macOS, for now, is only a self-contained desktop client to connect to other machines, not a host yet. The supported desktop hosts today are Linux and Windows; Android has its host mode inside the APK.
Check BIOS/UEFI, power saving, stored MAC and wired networking. From Android, the app only tries to send WoL if the phone is on Wi-Fi. Remember that today it's a local-network signal: from outside you need another machine already on in that same network to send the packet for you.
KDE, GNOME and wlroots don't behave the same. Some capture indicators belong to the system, not to NodalDesk. Not every visual notice can be removed from the app's UI.
The relay or mobile route can have more latency and less bitrate headroom than a LAN. NodalDesk avoids aggressive changes that restart capture on delicate routes, especially on Wayland.
The technical PIN is 6 digits and rotates every 5 minutes by default. If you take too long, read the QR again or request a new PIN from the host.
The documented headless mode depends on KDE Wayland and KWin D-Bus. On other desktops, behavior with screens off may need a different path or not be covered yet.