Skip to content

Installation

Start here to choose the best RustDesk Server Pro installation method for your environment, with Docker as the recommended option.

What is the best way to install RustDesk Server Pro?

For most teams, Docker is the best way to install RustDesk Server Pro because updates are simpler and the deployment is easier to reproduce. The install.sh path is useful when you want native systemd services on Linux. Converting from OSS is the right path when you already run RustDesk Server and want to keep moving to Pro.

What do you need before you start?

  • A RustDesk Server Pro license
  • A Linux server or VM, or a host where Docker is already available
  • Required RustDesk ports open in your firewall, plus 21114 or 443 if you need the web console and API
  • An optional DNS name if you want HTTPS on a domain

Which installation method should you choose?

MethodBest forWhy you would use it
DockerMost new Pro deploymentsEasiest upgrades, simpler rollback, and consistent setup
install.shLinux admins who want native servicesCreates systemd services and can optionally set up Nginx and Certbot
Convert from open sourceExisting OSS deploymentsMoves an existing RustDesk Server install to Pro without starting from zero

Method 1: Docker (Recommended)

bash <(wget -qO- https://get.docker.com)
wget rustdesk.com/pro.yml -O compose.yml
sudo docker compose up -d

For more details, please check Docker.

Method 2: install.sh

If you are proficient in Linux, please use the script below. Otherwise, you may encounter significant issues if it fails, and it could be difficult to determine why it isn’t working.

bash <(wget -qO- https://raw.githubusercontent.com/rustdesk/rustdesk-server-pro/main/install.sh)

For more details, please check install.sh.

Convert from open source

Docker

If you install the open-source version using Docker, there is no direct way to convert it. Instead, you’ll need to run a new container with the Pro image. Before doing this, please back up your private key (the id_ed25519 file, not id_ed25519.pub). Once the new container is set up, copy the old id_ed25519 private key file to the working directory of the new container, then restart the container.

install.sh

If you install the open-source version using install.sh, please follow this.