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

Selfhosted

60048 readers
977 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam.

  3. Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.

  4. Don't duplicate the full text of your blog or git here. Just post the link for folks to click.

  5. Submission headline should match the article title.

  6. No trolling.

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
[–] ryokimball@infosec.pub 2 points 1 month ago

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).