[SOLVED] Kdeconnect does not connect pc <-> phone. How to troubleshoot?
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
------------*****---------------------------------******----------------------------******---------------
Troubleshooting is #7 in this Guide: https://community.kde.org/KDEConnect
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,634
Original Poster
Rep:
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 .
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,634
Original Poster
Rep:
GOTCHA . 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.
GOTCHA . 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.
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,634
Original Poster
Rep:
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
.
. 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.
.
