Use standard ports 80, 443?

[jeffshead]

Maybe I missed it but I haven't found any info or instructions on making RD use standard ports. Most properly configured LAN's in a business environment limit end user traffic in/out of their gateway firewall to ports 80, 443 and maybe a couple others.

Has anyone installed RD server and set it up to use standard ports so that you can remotely connect and support end users (behind firewalls blocking all but port 80 and 443) over the Internet?

[dkanzlemar]

I second this. I can use Teamviewer at my office to connect to my home server, but not RustDesk for this very reason.

[deajan]

Configuring HBBS & HBBR to listen on standard ports is easy.
But where to configure rustdesk client to use them ?
Any news on this ?

Ports 2111x aren't generally open outbound on any network. Thus using standard ports 80 & 443 is a reasonable claim.

[pedjas]

I support this. Only ports 80 and 443 are safe to use. Others may be (and often are) blocked by routers.
The key to success of remote access platform is its ability to work without requirement for special settings on routers.

[phyzjqkl]

no one can answer this?

[deajan]

Looks like the documentation now show how to change hbbr and hbbs client side ports

As for the hbbs and hbbr server modules, just NAT them via your local firewall.

[shensmobile]

This is only possible when you self-host right? You can't connect to the public servers using that technique since you can't actually specify them in the ID/Relay server fields, unless there's a list of their IP/Web addresses out there?

[phyzjqkl]

yes. but what is the procedure? 获取Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: shensmobile ***@***.***> Sent: Thursday, March 16, 2023 2:33:59 PM To: rustdesk/rustdesk ***@***.***> Cc: phyzjqkl ***@***.***>; Comment ***@***.***> Subject: Re: [rustdesk/rustdesk] Use standard ports 80, 443? (Discussion #984) This is only possible when you self-host right? You can't connect to the public servers using that technique since you can't actually specify them in the ID/Relay server fields, unless there's a list of their IP/Web addresses out there? ― Reply to this email directly, view it on GitHub<#984 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AIYLTSA24FPR4Q4ZIR3JQHDW4NMJPANCNFSM53YELLRQ>. You are receiving this because you commented.Message ID: ***@***.***>

[shensmobile]

To be honest, I'm not sure. I'm tinkering with it now but I'm not convinced that this will allow us to force the client to listen/communicate through ports 443 and 80.

[phyzjqkl]

I think if i am the owner of host, i can let user know i am using private server. i wonder for portable host (run rustdesk without install), it can talk to name server with 80 ports? I hv a job site computer which need to be host but only 80 port open2023年3月16日 14:41，shensmobile ***@***.***>写道： To be honest, I'm not sure. I'm tinkering with it now but I'm not convinced that this will allow us to force the client to listen/communicate through ports 443 and 80. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[deajan]

I am too trying to use standard ports right now.
I can successfully connect to my selfhosted rustdesk server using hbbs port 21116.
I've made a NAT src port 21116 dst port 21116 to my hbbs server.
I've also made a NAT src port 80 dst port 21116 to my hbbs server.
Both NATs are for TCP and UDP connections.

Rustdesk logs show that the hbbs connection work on both ports 21116 or 80, but the desktop app writes Not ready. Please check your connection when using port 80. I've also tried port 443, same results.

I'm quite puzzled actually. I think rustdesk client calculates other ports by doing addiing or substracting integers to the current hbbs port number, hence rendering it not usable for anything else.
Anyone got rustdesk to work with standard ports ?

I've also changed hbbs port with --port 443 directive in hbbs executable, and made NAT port 443:443. No results.

My firewall sees incomming TCP connections on port 443 but never any UDP connections. Of course they're allowed.
Using standard port 21116 in rustdesk client will trigger both TCP and UDP connections to port 21116.

Created an issue at #4260

[deajan]

My issue has been closed with a wontfix badge, without any further explanation.
There has to be an obvious problem, but I don't really get it.

[rustdesk]

I am sorry to make you unhappy, to avoid confusion, we make this decision, #4331, this discussion will be the first one.

[deajan]

I am sorry to make you unhappy, to avoid confusion, we make this decision, #4331, this discussion will be the first one.

Okay, makes sense.
I'll allow myself to copy the issue text here.

[deajan]

Since rustdesk works with specific ports 21115-21119, a great number of public wifi networks as well as some corporate environment will not allow rustdesk connections.

Most networks always allow ports 80, 110, 143 and 443 but filter anything else.
It would be great if rustdesk could make usage of those default ports, 80 and 443 being the best, for both self hosted or public hbbs/hbbr servers.

As ideal scenario, rustdesk would try to connect to port 21116, and fallback to 443 then to 80 if not successful.
Teamviewer for example uses this exact connection schema, with a proprietary port and then some fallback ports, see https://community.teamviewer.com/English/kb/articles/4139-ports-utilises-par-teamviewer

Anybody that ever used a filtered network like a wifi hotspot in a café in Europe for example will enjoy this feature ;-D
It doesn't seem that rustdesk can be configured to use those ports properly as of today.

[Kofl]

Absolutely, it would increase the usage of Rustdesk tremendous with fallback to 443/80
All commercial products like Teamviewer, AnyDesk, WiseConnect use that technique as nowadays outgoing any ports is rare.

[IAMBUDE]

This missing feature sadly is a deal breaker for us.
I'm still looking for a decent self-hosted remote support solution and rustdesk was fairing great so far but many of our customers block outgoing connections except for http or https.

[kragil]

This should be the default.

[My1]

the fun question is also is it using Protocols a firewall can understand (even if it cant see the actual contents because encryption) because not sure if firewalls check for the traffic being HTTP and HTTPS (or at the very least TLS in general) on 80&443

[ben-kuhn]

Good firewalls inspect at layer 7 (application) as well as layer 3 (TCP or UDP port) so just changing the port isn't always going to help. The firewall will see non-HTTP(S) traffic on 80 or 443 and drop it.

[Logic-Bits]

we also experienced some problems not using the "default" open Ports... then always have to switch to TeamViewer.

[djordans]

Hello,
Ports 443 and 80 work but UDP 443 does not work on all internet connections
I tested with Server ID on 443 and Relay on 80, it works but you have to open ports 443 TCP & UDP on the firewall

[deajan]

Considering HTTP/2 uses TCP and UDP, that's a fair configuration that should be used widely.

[Kofl]

Yes, but note, that Enterprise Networks block http/2 (UDP) as most security appliances are still not yet able to scan the traffic.