19
submitted 9 months ago by rambos@lemm.ee to c/selfhosted@lemmy.world

Hello selfhosters, I've been using different remote desktop apps to support few friends and family members with their Windows or Linux desktop machines. Sometimes I also use phone (Android) when I'm away from home.

I tried 3 services so far:

  1. TeamViewer - its amazing, but it recognized me as non-private user and asking for money...
  2. AnyDesk - even better experience than TeamViewer. It also started with non-private use and messages to buy a license (after creating account it stopped doing that). It works perfectly fine, but sometimes it gets super slow and it tends to reduce stream quality by too much
  3. RustDesk - finally found open source solution and it has the same features like others I tried. The problem with RustDesk is simmilar to AnyDesk, sometimes its super slow, laggy and with reduced stream quality and sometimes connection breaks. It has permanent message on the bottom:

Ready, For faster connection, please set up your own server.

Sounds like a perfect task for my server on fiber network.

I checked self hosted RustDesk service, but it requires opening ports. I have open wireguard port to my home server to connect to home network when needed. I don't like idea of opening more ports just because it doesn't feel safe in my hands, but maybe I'm wrong. Am I missing something? What do you use for remote desktop? Do you have the same experience with any service I mentioned here? Is anyone selfhosting RustDesk server? Are there better (free or affordable) alternatives available? I prefer selfhosted if possible. 10$ a month is kinda steep for me and my needs. I don't need super high quality stream, but would be nice to have simple solution that just works

All tips are welcome

you are viewing a single comment's thread
view the rest of the comments
[-] Boring@lemmy.ml 9 points 9 months ago

You can tunnel RDP over SSH. Then you'd only open a port that requires authentication to access and is encrypted.

[-] rambos@lemm.ee 1 points 9 months ago

Do I need to open port on client pc for that? Ill take a look anyway, thx

[-] Boring@lemmy.ml 2 points 9 months ago

No only the server, you can host an openssh server and have clients connect remotely.

Sorta like how you can host a webserver and a client doesn't need 443 open. Except a reverse shell is possible with ssh, allowing a client to be controlled without their port 22 open.

[-] rambos@lemm.ee 2 points 9 months ago

Nice thx, Ill read more about that

[-] MangoPenguin@lemmy.blahaj.zone 1 points 9 months ago

Only for SSH which is safe.

this post was submitted on 05 Oct 2023
19 points (88.0% liked)

Selfhosted

37771 readers
437 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 posting.

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

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

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS