Have you considered just using a cloud host, I put my rustdesk on linode. $5.60 a month, easy to deploy
I have. But, since I’m already paying for static IPs and not likely use Ruskdesk more than a few times a year, the home lab is likely fine.
If the Docker container isn’t exposing any ports, you need to check your Docker run command or Docker Compose configuration to ensure the ports are properly mapped.
For Rustdesk, you’ll make sure that the necessary ports (21115 for TCP and 21116 for UDP) are exposed in your container settings. Additionally, verify that your firewall settings allow traffic on those ports.
Hi Pasterms, first off thanks for the reply. My Docker container seems to be working as advertised since I can connect to boxes on my LAN just fine using the ID Server. I also believe I’ve created the appropriate NAT entries/firewall rules in pFsense since canyouseeme.org tells me the RuskDesk ports are open. I’m really at a loss at the moment.
I’ve used the amazing HAproxy guides to achieve connectivity to https/https which are signed/self-signed boxes behind a cert on 443. I can server all kinds of services on 443 including openVPN.
The next big challenge is to create a HAproxy config to RUSTDESK (pro) server on 443- this means console on 443/ and relay and signal websocket (21118/21119).
No prob getting the console to appear on 443.
In my opinion, a great complement to the videos about rustdesk and haproxy would be to “complete” this package. Yes, correctly I read that proxy stuff is no needed if using normal ports. That works perfect. But more and more of the world is blocking outbound non-https ports, making it necessary to work within that limitation.
I also find this a good resource:
and this is what I’m using to “try” things
Anyone dabbling with proxying rustdesk, chime on in