Just set up DynDNS an host rustdesk on docker. It requires two docker containers, exchanging secret keys and opening firewall ports
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
You can get a free subdomain from https://desec.io/ so maybe that could help? I did that for a while before buying a cheap domain. You'll get something like stuff.dedyn.io
I host rustdesk on my own domain and it works. I don't have my tinfoil hat all the way on though.
I'm not familiar with what's been said or done regarding bots, but I'd be surprised if they were planning to shutdown the self-hosting part? But I can see how they might shutdown the free cloud auth aspect.
As RD consists of the server/client software and the authentication software, the latter is also made available online to all with no reliability promises. But there's nothing stopping people from hosting both parts locally, and is how I implemented it. No traffic to third parties, etc.
Can't advise on domain-based setup, as I've not tried it, but depending on how you're planning to use it, there may be no need for a domain. I only used mine locally (or via WireGuard when outside), with hbbr and hbbs hosted in Docker on my NAS, and it worked fine with my mobile devices and PCs.
I have not set it up yet but plan to do so soon. I could imagine a requirement of owning a host name so that you can have a certificate, but I imagine an IP address would work just as well. You will need to open ports on your router according to the documentation; I haven't looked into reverse proxy options or anything to prevent the firewall changes being necessary.
But yeah, my understanding is it's totally doable for "free" (i.e. using your existing infrastructure).