If you want a fast, secure, and open-source remote desktop tool, Install RustDesk on Ubuntu 26.04 is a practical choice. This guide shows you how to set it up cleanly, why each step matters, and how to avoid the most common mistakes on modern Ubuntu systems. RustDesk’s official Linux documentation confirms the supported install flow for Debian-based systems like Ubuntu, including the .deb package method.

RustDesk is popular with Linux users because it gives you remote access without forcing you into a closed platform. It also supports self-hosting, so you can keep control of your remote connections instead of sending traffic through a third party by default. In this tutorial, you will learn how to install it, configure it, and troubleshoot the setup like a sysadmin would.

Prerequisites

Before you begin the Install RustDesk on Ubuntu 26.04 setup, make sure you have these basics ready:

• Ubuntu 26.04 LTS installed on a desktop or server with a GUI session.
• A user account with sudo access.
• Internet access for downloading the RustDesk package.
• Basic terminal skills.
• wget or curl installed.
• Enough disk space for the package and dependencies.
• Optional: UFW enabled if you plan to use self-hosted RustDesk servers.

RustDesk’s Linux docs recommend the .deb install path for Debian derivatives like Ubuntu, which keeps the process simple and consistent. If you plan to self-host later, you should also prepare firewall access for the RustDesk ports used by the server stack.

Step 1: Update Your System

Refresh package lists

Run this first:

sudo apt update

This command refreshes Ubuntu’s package index. You need that because package metadata gets stale fast, and stale metadata can cause failed installs or missing dependency warnings.

Upgrade installed packages

Next, apply current updates:

sudo apt upgrade -y

This updates your installed packages before you add new software. It matters because a clean, patched system reduces conflicts and lowers the chance of broken libraries during the RustDesk install.

Install helper tools

If you do not already have them, install these tools:

sudo apt install -y wget curl

You need wget or curl to fetch the latest RustDesk release package from the web. RustDesk’s official Linux documentation supports package-based installation on Ubuntu, so these tools make the download step easier and repeatable.

Step 2: Download RustDesk

Get the latest release tag

Use GitHub’s release API to pull the latest version:

VER_TAG=$(curl -s https://api.github.com/repos/rustdesk/rustdesk/releases/latest | grep tag_name | cut -d '"' -f 4 | sed 's/v//')
echo "$VER_TAG"

This command finds the current release tag automatically. That saves you from hardcoding an old version number, which is one of the most common mistakes in Linux server tutorial workflows.

Download the Debian package

Now fetch the .deb file:

wget https://github.com/rustdesk/rustdesk/releases/download/$VER_TAG/rustdesk-$VER_TAG-x86_64.deb

This downloads the Ubuntu-compatible package for 64-bit systems. RustDesk’s official docs show the same .deb install path for Ubuntu and other Debian-based distributions.

Check the file

Confirm that the download succeeded:

ls -lh rustdesk-*.deb

You should see a file size, not zero bytes. That check matters because broken downloads are easier to catch now than after a failed install.

Step 3: Install RustDesk on Ubuntu 26.04

Install the package

Run this command:

sudo apt install -fy ./rustdesk-$VER_TAG-x86_64.deb

This installs RustDesk and resolves missing dependencies at the same time. The RustDesk Linux docs specifically recommend apt install -fy for Ubuntu-based systems.

Why this command works

apt handles dependencies better than dpkg alone. That matters because RustDesk may need video and GUI libraries, and apt can pull them in automatically instead of stopping halfway.

Verify the install

Check that RustDesk is available:

rustdesk --version

If the command returns a version number, the install worked. That gives you a quick sanity check before moving to configuration.

Step 4: Launch RustDesk

Open the app

Start RustDesk from your app menu, or run:

rustdesk &

This opens the RustDesk client in the background. You should see the main window with your ID and password fields.

What you should see

On first launch, RustDesk generates a local ID and an access password. That ID is the key you share with another device when you want remote access.

Why first launch matters

This first run confirms that the GUI works, that RustDesk starts cleanly, and that your desktop session can support screen sharing. RustDesk’s docs also point users to client settings for choosing public or self-hosted servers later.

Step 5: Configure RustDesk on Ubuntu 26.04

Open security settings

Go to the menu and find the security section. Set a strong permanent password if you want unattended access.

RustDesk Menu > Security > Set permanent password

A permanent password is useful when you manage servers or remote desktops that must stay reachable after reboot. It also avoids the problem of the one-time password changing every time the app restarts.

Set network options if needed

If you use your own server, open the network settings and enter your ID server, relay server, and key.

RustDesk Menu > Network > ID Server / Relay Server / Key

RustDesk’s self-host documentation explains that clients can point to a self-hosted server by filling in these fields. That is especially useful if you want more control over privacy and traffic flow.

Why this step matters

Without these settings, the client uses the default connection path. That is fine for a quick test, but a sysadmin usually wants predictable access and stronger control.

Step 6: Configure Firewall Access

Open required ports

If you self-host RustDesk, open the default ports:

sudo ufw allow 21115/tcp
sudo ufw allow 21116/tcp
sudo ufw allow 21116/udp
sudo ufw allow 21117/tcp
sudo ufw allow 21118/tcp
sudo ufw allow 21119/tcp
sudo ufw reload

RustDesk’s self-host docs list these as the core ports used by the ID and relay services. The official docs also note that UDP 21116 is part of normal RustDesk connectivity.

Check firewall status

Confirm the rules are active:

sudo ufw status verbose

You should see the ports listed as allowed. This matters because a blocked port often looks like an app bug when it is really just a firewall problem.

Why firewall rules are important

A self-hosted remote desktop server without firewall rules is exposed and unreliable. Opening only the needed ports keeps your access path clear while limiting unnecessary network exposure.

Step 7: Set Up Self-Hosting

Install the server stack

RustDesk supports self-hosting through its server components. The official docs describe hbbs as the ID or rendezvous server and hbbr as the relay server.

Why sysadmins use self-hosting

Self-hosting gives you more privacy, better control, and a setup that fits internal policy. It also helps when you manage multiple Linux machines and want a stable remote access path.

What to do next

Use the RustDesk server documentation to deploy the server binaries or Docker stack, then point your Ubuntu client to that server. After that, verify the key and connection fields in the RustDesk client.

Step 8: Confirm the Connection

Test remote access

Try connecting from another machine with RustDesk installed. Enter the ID and password from your Ubuntu system.

What success looks like

A working connection should open the remote desktop view within a few seconds. If it fails, check the server key, firewall, and the active session type.

Why testing matters

You want to verify the full path, not just the install. A successful launch does not always mean remote access is working correctly.

Troubleshooting

1. RustDesk will not start

Check whether the package installed correctly:

rustdesk --version

If this fails, reinstall the package with apt install -fy. RustDesk’s Linux docs use that install method for Ubuntu-based systems.

2. Connection fails

Check your firewall and server ports:

sudo ufw status verbose

If you self-host, confirm that ports 21115 to 21119 are open as needed.

3. Black screen during remote access

This often comes from Wayland session limits on modern Ubuntu systems. RustDesk’s docs include Wayland notes and Linux-specific troubleshooting.

4. Wrong key or server mismatch

Recheck the ID server, relay server, and key fields in RustDesk. The server key must match the self-hosted server you are using.

5. Package download fails

Make sure your network works and that the GitHub release URL is valid. If needed, rerun the download command and confirm the file exists with ls -lh.