Outcome: You’ll set up RustDesk so you can start a free remote desktop session between your devices without creating an account.

Who this is for: Anyone who wants a simple cross-platform remote access tool for Windows, Mac, Linux, or Android.

Time required: About 5 to 10 minutes for direct use, or about 15 minutes if you also self-host the server with Docker.

Quick Answer

Download RustDesk, open it on both devices, then enter the remote device’s ID and temporary access code to connect right away. If you want more control, you can later point both clients to your own RustDesk server using the official Docker self-host guide.

If you want a free remote desktop app that works fast and does not force you through an account signup maze, RustDesk is one of the cleaner options around. It is open source, available on major desktop platforms, and its official site says you can either use the default service or run your own server for more control.

Prerequisites

Step 1: Install RustDesk on both devices

Install RustDesk on the computer you want to control and on the computer you will control it from. Launch the app on both devices.

Expected result: Each device shows a RustDesk window with its own ID and a temporary access code.

Step 2: Start a direct remote session

On your main computer, type the remote device’s RustDesk ID into the Remote ID field and start the connection. When prompted, enter the temporary access code shown on the other device.

This is the fast path that makes RustDesk useful for quick help sessions, accessing a second machine, or checking a home computer while you are away.

Expected result: The remote desktop opens and you can move the mouse, type, and see the other screen in real time.

Step 3: Test the features you actually care about

Before you call the setup done, test one or two real tasks:

  1. Open a folder or app on the remote machine.
  2. Resize the remote window or switch displays if the remote computer has more than one monitor.
  3. Try file transfer if that is part of your workflow.

Expected result: The connection feels responsive enough for normal desktop work and basic support tasks.

Step 4: Optional — self-host RustDesk with Docker for more control

If you want your own backend instead of relying on the default public infrastructure, RustDesk documents a self-hosted setup using two services:

  • hbbs for ID, rendezvous, and signaling
  • hbbr for relay traffic when direct hole punching fails

The official Docker documentation recommends Docker Compose with network_mode: "host" on Linux for the simplest setup. It also says the minimum required ports are centered around 21115 through 21117, with additional ports for web client support.

Example flow:

  1. Install Docker using the official Docker Engine guide.
  2. Follow the official RustDesk Server OSS Docker guide.
  3. Start hbbs and hbbr with Docker Compose.
  4. Point your RustDesk clients at your new server.

Expected result: Your clients register against your own RustDesk server, and relay traffic uses infrastructure you control.

Why this trick is worth using

RustDesk’s official site positions it as an open-source remote access tool with self-hosting support, and the project’s GitHub repository confirms that you can use the public rendezvous and relay service or set up your own. RustDesk’s self-host docs also explain that direct peer-to-peer hole punching is attempted first, with the relay server used only when direct connection fails.

That is the sweet spot here: easy enough for a quick connection, but flexible enough if you later want more control.

Common mistakes

  • Downloading RustDesk from unofficial domains instead of the official rustdesk.com site
  • Typing the wrong remote ID or using an expired temporary access code
  • Assuming self-hosting works without opening the required firewall ports
  • Forgetting that network_mode: "host" in the Docker docs is the recommended Linux path, not a universal setup for every platform

Troubleshooting

  • Connection starts but never opens: verify the remote device is still online and the RustDesk window is still open.
  • The session is slow: test on a better network first, then consider self-hosting if you want tighter control over routing.
  • Direct connection fails: this is exactly when the relay server matters; if you self-host, double-check the required ports from the official self-host overview.
  • Your Docker server works but clients do not register: confirm both hbbs and hbbr are running and that the client is pointed to the correct server address.

One more useful check

The RustDesk documentation says hbbs handles ID and signaling, while hbbr handles relay traffic. If you self-host, that means a good sanity check is simple: make sure clients can register, then try one connection from a different network. If registration works but the session never falls back cleanly, you probably still have a port or routing issue.

Takeaway

If you just want free remote desktop access without extra account friction, RustDesk is a solid first move. Start with the default direct connection workflow, make sure it works for your real tasks, and only add self-hosting when you actually need the extra control.

Next step

Install RustDesk on two of your own devices today and test one short session. If it fits your workflow, bookmark the official self-host Docker guide for the next upgrade.