this post was submitted on 06 May 2026
45 points (95.9% liked)

Selfhosted

62103 readers
387 users here now

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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

I thought self-hosting requires, like, paid ownership of a website or something. I don't think I've ever self-hosted before and am lost with its guide.

My primary concern is RustDesk's warning about possibly shutting down its free self-hosting because of bot abuse, despite now requiring GitHub accounts. There seems to be nothing even remotely close to RustDesk, except possibly HopToDesk, which I heard is a fork of an older version or something.

It'd be nice to be able to keep this going just in case. Or are there free, E2EE servers out there that anyone knows of?

you are viewing a single comment's thread
view the rest of the comments
[–] Brewchin@lemmy.world 3 points 4 months ago

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.