Bug 499951

Summary:	[Feature Request} Allow configuration of communication port - change 1716 port
Product:	[Applications] kdeconnect	Reporter:	Rigoberto Leyva Salmeron <rleyvasal>
Component:	common	Assignee:	Albert Vaca Cintora <albertvaka>
Status:	REPORTED ---
Severity:	wishlist	CC:	andrew.g.r.holmes, ilikefoss
Priority:	NOR
Version First Reported In:	24.12.2
Target Milestone:	---
Platform:	Other
OS:	Other
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Rigoberto Leyva Salmeron 2025-02-13 04:20:43 UTC

SUMMARY
KDE connect often fails to connect on public networks because port 1716 is blocked by public firewalls . It would be beneficial for users to have the ability to change the communication port so that Kdeconnect can be used on any network. This could be an option in the desktop and mobile apps. 

STEPS TO REPRODUCE
1. Connect computer and phone to public network
2. Kde connect cannot communicate

OBSERVED RESULT
1. Connect computer and phone to public network
2. Kde connect cannot communicate

EXPECTED RESULT
1. Connect computer and phone to public network
2. Kde connect cannot communicate
3. Change communication port so the communication can be established

ADDITIONAL INFORMATION

Comment 1 John 2025-02-13 08:38:58 UTC

While I cannot confirm this problem as I have until now connected only to my private networks, having problems connecting the apps to the computers from time to time, I think it would be great to be able to choose the port number to be used both in computer and in the mobile app.
And it's a good idea anyway to be able to do that.
Maybe some past or future program / game needs to use that port and that could be an important thing we need or want to run.
For privacy and security is also good to be able to define our custom port to use instead of the default one.