Fix KDE Connect never finding the phone while everything else on the network is discoverable
Split out on 2026-09-11 from mdns-local-hostnames-fail-ufw-blocks-5353, which was re-audited that day, came back corrected and was then merged into mdns-local-hostname-not-resolving. KDE Connect was the one part of that record which survived its audit intact and which is not mDNS at all, so it became its own record rather than being carried by a record about name resolution. Every claim here was re-checked on omarchy 4.0.2-1 while splitting it: the 1714 to 1764 range on both protocols is stated by KDE's own documentation, retrieved 2026-09-11, install/config/firewall.sh opens only 53317, ufw status on this machine lists no rule for the range, and /etc/ufw/after.rules:27 is -A ufw-after-input -m addrtype --dst-type BROADCAST -j ufw-skip-to-policy-input under the comment don't log noisy broadcast. Not exercised: no KDE Connect client is installed here and no phone was paired, so the remedy rests on the port range being right rather than on a reproduction.
This opens 51 ports on two protocols to everything on the link, and KDE Connect's pairing is what stands between that and another device on the network. On a laptop that joins café, hotel or conference Wi-Fi, use the network-scoped form above rather than the open one.
Symptom
KDE Connect on the desktop and on the phone never see each other, while the rest of the local network is fine: .local names resolve, avahi-browse lists other machines and network printers appear. Pairing by typing the other device's address by hand also fails, or pairs and then goes unavailable. Both devices are on the same subnet and the phone app reports no devices found.
Cause
KDE Connect does not use mDNS, so everything that makes .local names and printer discovery work is irrelevant to it. It discovers over UDP broadcast and then connects on TCP, using ports 1714 to 1764 on both protocols, which its own documentation states.
Two things on Omarchy 4 then stop it, both confirmed on an omarchy 4.0.2-1 install:
/usr/share/omarchy/install/config/firewall.shopens only LocalSend's 53317 on both protocols. No Omarchy install step or migration opens the KDE Connect range, andufw statuson a stock machine shows no rule for it./etc/ufw/after.rules:27sends broadcast traffic toufw-skip-to-policy-inputunder the commentdon't log noisy broadcast, so the discovery packets reach the default deny policy and are dropped without a log line. Nothing appears in the journal to explain the silence.
This is why the symptom reads as a general network fault when nothing general is wrong.
Fix
Open the range on both protocols:
sudo ufw allow 1714:1764/udp comment 'KDE Connect'
sudo ufw allow 1714:1764/tcp comment 'KDE Connect'
sudo ufw status
Scope it to your own network if you use café or hotel Wi-Fi, which is the better habit on a laptop:
sudo ufw allow in proto udp from 192.168.0.0/16 to any port 1714:1764 comment 'KDE Connect, LAN only'
sudo ufw allow in proto tcp from 192.168.0.0/16 to any port 1714:1764 comment 'KDE Connect, LAN only'
Nothing else is needed on the Omarchy side, and in particular do not reach for 5353 or for anything about Avahi. If .local names or printer discovery are also failing, that is a different problem and mdns-local-hostname-not-resolving covers it.
Verify
sudo ufw status
Both 1714:1764/udp and 1714:1764/tcp are listed, and the phone appears in the KDE Connect app on the desktop within a few seconds of both apps being open on the same network. If it still does not, the fault is not the firewall: check that both devices are on the same subnet and that the phone is not on a guest network that isolates clients.