KDE Connect not finding phone/phone not finding devices

I’m running CachyOS on both a laptop and my desktop, with KDE Connect installed and setup on both. I’ve disabled UFW, as well as opened both the TCP and UDP ports, however KDE Connect just refuses to find either of the machines.

If I manually add the IP for either one, I can see the ping responds in milliseconds, but outside of that I am not able to link the phone to either device. I’ve seen others reporting this issue before, and most say simply adding the ports to UFW fixes it, however that’s not working for me.

I’ve installed KDE Connect off of F-Droid, and it’s version 1.33.4.

@Offspring:

First, welcome to the KDE Discuss forums.


A very stupid and dumb question:

Yes, there is an iOS version in the Apple App Store but, I’m not sure as to it’s current status – <KDE connect on the App Store>

Yeah. After updating GUFW on one of the machines to allow KDE Connect, I was able to get it to pair but only after also manually adding the IP. The other machine still cannot connect to KDE Connect on the phone, even though the IP has also been manually added and I’ve allowed it through the UFW firewall using GUFW.

@Offspring:

Then, something isn’t happening with respect to DNS on your LAN …

For some Linux systems, this applies:

 > cat /etc/resolv.conf 
### /etc/resolv.conf is a symlink to /run/netconfig/resolv.conf
### autogenerated by netconfig!
#
# Before you change this file manually, consider to define the
# static DNS configuration using the following variables in the
# /etc/sysconfig/network/config file:
#     NETCONFIG_DNS_STATIC_SEARCHLIST
#     NETCONFIG_DNS_STATIC_SERVERS
#     NETCONFIG_DNS_FORWARDER
# or disable DNS configuration updates via netconfig by setting:
#     NETCONFIG_DNS_POLICY=''
#
# See also the netconfig(8) manual page and other documentation.
#
### Call "netconfig update -f" to force adjusting of /etc/resolv.conf.
search fritz.box
nameserver 192.168.178.1
nameserver fda5:b1e5:3a56:0:62b5:8dff:fefe:ca0e
nameserver 2001:9e8:ab46:9000:62b5:8dff:fefe:ca0e
 >

For systems using the Systemd Network And Network Name Resolution Managers it’s different but, pretty much the same.

  • Bottom line, there has to be a box on your LAN which provides DNS services.
    Without that, KDE Connect doesn’t have a chance to do what it has to do …