Kdeconnect does not connect pc <-> phone. How to troubleshoot?
Kdeconnect is running both in tumbleweed on my pc and my phone (Motorola G3, LineageOS). Some time ago this worked.
I checked the firewall on the pc and ports according to these sources: https://community.kde.org/KDEConnect https://en.opensuse.org/SDB:KDE_Connect On the phone I tried entering the IP of my PC in the local net (192.168.178.27), no change. Where can I look to get a handle on this? |
Hi:
I wasn't able to get KDE Connect to work on my Android phone either. An alternative would be to try using Air Droid-;) https://play.google.com/store/apps/d...droid&hl=en_US ------------*****---------------------------------******----------------------------******--------------- Troubleshooting is #7 in this Guide: https://community.kde.org/KDEConnect |
Quote:
Quote:
Quote:
|
What did you do to get KDE Connect working again?
|
Looks like f-droid has Nitro Share and Treble Shot for file transfer.
https://search.f-droid.org/?q=file+t...cation&lang=en |
That is a misunderstanding, it is not working. Kdeconnect is a lot more than file transfer. And before I give up I'd really like to lick this problem I hate to chicken out like this.
As I see it the most probable stumbling blocks are the router and the firewall. OpenSUSE's firewall has an excessive amount of zones, no idea whether they just forgot to mention others besides public (where I opened the ports). On the other hand documentation of SUSE-firewall is abysmal :(. |
AHA. It is the firewall. I stopped it and Kdeconnect works. Now where is that blasted piece of software interfering where it shouldn't...
|
Quote:
Sorry I don't know how to find the piece of software that is interfering. FWIW I couldn't get KDE Connect to work at all on my phone but it works on my Lenovo Android Tablet. Good luck:- |
GOTCHA :D. That blasted documentation is not up to date. I just took my time to click myself through the menus of YAST's firewall program. There I noted that my ethernet interface is in the internal zone. I then opened the necessary port range (1714-1764 tcp and udp) for the internal zone and lo and behold -- the problem vanished. Marking this thread as solved.
Thanks for your prodding ;) and help, Ztcoracat :). |
Quote:
Have a good weekend-;) |
Some additional information: The phone connects with the router via WiFi (WLAN), the pc connects with the router via ethernet (cable). Thus I needed to know in which zone the ethernet interface of the pc resides (from the point of view of the firewall of the pc). In my case that is "internal". HTH for any others with the same problem.
|
Thanks for the details.
|
All times are GMT -5. The time now is 07:48 AM. |