mirror of
https://github.com/rustdesk/doc.rustdesk.com.git
synced 2026-07-19 05:03:59 +00:00
blogs
This commit is contained in:
rustdesk
@@ -10,7 +10,7 @@ pre: "<b>1. </b>"
|
||||
The RustDesk Client is the application you install on devices to start or receive remote desktop sessions through RustDesk public servers or your own self-hosted RustDesk Server. Use this guide to download the correct build, install it on each platform, connect to another device, and point the client to RustDesk Server OSS or RustDesk Server Pro.
|
||||
|
||||
{{% notice note %}}
|
||||
Platform guides: [RustDesk for Linux](https://rustdesk.com/blog/rustdesk-for-linux), [RustDesk for Mac](https://rustdesk.com/blog/rustdesk-for-mac), and [remote control from Android and iOS](https://rustdesk.com/blog/rustdesk-remote-control-android-ios). See also [the best free remote desktop software](https://rustdesk.com/blog/best-free-remote-desktop-software).
|
||||
Platform guides: [RustDesk for Linux](https://rustdesk.com/blog/rustdesk-for-linux) and [remote control from Android and iOS](https://rustdesk.com/blog/rustdesk-remote-control-android-ios). See also [the best free remote desktop software](https://rustdesk.com/blog/best-free-remote-desktop-software).
|
||||
{{% /notice %}}
|
||||
|
||||
## Supported Platforms
|
||||
|
||||
@@ -7,10 +7,6 @@ weight: 3
|
||||
|
||||
Use this macOS guide to install RustDesk, allow the app to run, and grant the permissions needed for screen capture and input control.
|
||||
|
||||
{{% notice note %}}
|
||||
See also the overview guide: [RustDesk for Mac](https://rustdesk.com/blog/rustdesk-for-mac).
|
||||
{{% /notice %}}
|
||||
|
||||
## What does RustDesk need on macOS?
|
||||
|
||||
RustDesk on macOS needs more than the app installation itself. To control another Mac correctly, you typically need to move the app into `Applications`, allow it to run, then grant `Accessibility`, `Screen Recording`, and in some cases `Input Monitoring` permissions.
|
||||
|
||||
@@ -11,7 +11,7 @@ Self-hosting RustDesk lets you control your own ID and relay infrastructure, kee
|
||||
Support is available via our [Discord](https://discord.com/invite/nDceKgxnkV) for OSS and [email](mailto:support@rustdesk.com) for Pro.
|
||||
|
||||
{{% notice note %}}
|
||||
Background reading: [why self-host remote desktop software](https://rustdesk.com/blog/why-self-host-remote-desktop-software), [self-hosted vs. cloud SaaS](https://rustdesk.com/blog/rustdesk-self-hosted-vs-cloud-saas-option), and [what open-source remote desktop software gives you](https://rustdesk.com/blog/open-source-remote-desktop-software).
|
||||
Background reading: [why self-host remote desktop software](https://rustdesk.com/blog/why-self-host-remote-desktop-software).
|
||||
{{% /notice %}}
|
||||
|
||||
## Which RustDesk server should you choose?
|
||||
|
||||
@@ -33,8 +33,6 @@ Most self-hosted RustDesk clients only need a few values:
|
||||
|
||||
You can have your own name, logo, icon, configuration, be signed and more.
|
||||
|
||||
For a guided overview, see the [web console and custom client generator walkthrough](https://rustdesk.com/blog/rustdesk-web-console-custom-client-generator-port-21114).
|
||||
|
||||
Currently, Windows X64, Mac Arm64 / X64, [Linux](https://twitter.com/rustdesk/status/1788905463678951787), Android Arm 64 are supported.
|
||||
|
||||
[Video](https://twitter.com/rustdesk/status/1769171628426944539)
|
||||
|
||||
@@ -11,7 +11,7 @@ RustDesk Server OSS is the free and open-source self-hosted backend for RustDesk
|
||||
Use RustDesk Server OSS when you want core self-hosting capabilities and are comfortable managing deployment, networking, and upgrades yourself. If you need a web console, API access, OIDC, LDAP, 2FA, device management, or other centralized admin features, compare it with [RustDesk Server Pro](/docs/en/self-host/rustdesk-server-pro/).
|
||||
|
||||
{{% notice note %}}
|
||||
Related reading: [what open-source remote desktop software gives you](https://rustdesk.com/blog/open-source-remote-desktop-software) and [why self-host remote desktop software](https://rustdesk.com/blog/why-self-host-remote-desktop-software).
|
||||
Related reading: [why self-host remote desktop software](https://rustdesk.com/blog/why-self-host-remote-desktop-software).
|
||||
{{% /notice %}}
|
||||
|
||||
## What is included in RustDesk Server OSS?
|
||||
|
||||
@@ -20,7 +20,7 @@ RustDesk Server Pro is the commercial self-hosted deployment option for teams th
|
||||
- Plan for HTTPS, licensing, and client configuration immediately after the server starts.
|
||||
|
||||
{{% notice note %}}
|
||||
Deciding whether Pro fits you? See [self-hosted vs. cloud SaaS](https://rustdesk.com/blog/rustdesk-self-hosted-vs-cloud-saas-option), [how to evaluate Server Pro](https://rustdesk.com/blog/rustdesk-server-pro-free-trial), and [RustDesk for enterprise](https://rustdesk.com/blog/rustdesk-for-enterprise).
|
||||
Deciding whether Pro fits you? See [RustDesk for enterprise](https://rustdesk.com/blog/rustdesk-for-enterprise).
|
||||
{{% /notice %}}
|
||||
|
||||
## When to choose RustDesk Server Pro
|
||||
@@ -51,7 +51,7 @@ We recommend reading this first before proceeding, [How does self-hosted server
|
||||
|
||||
## Hardware requirement
|
||||
|
||||
Lowest level VPS is enough for your use cases. The server software is not CPU and memory intensive. Our public ID server hosted on a 2 CPU/4 GB Vultr server serves 1.0+ million endpoints. Each relay connection consumes avg 180kb per second. 1 cpu core and 1G ram is enough to support 1000 relay concurrent connections. For sizing at large scale, see [self-hosting server hardware at scale](https://rustdesk.com/blog/self-host-rustdesk-server-hardware-at-scale) and [scaling to 50,000–200,000 devices](https://rustdesk.com/blog/rustdesk-scale-50000-200000-devices).
|
||||
Lowest level VPS is enough for your use cases. The server software is not CPU and memory intensive. Our public ID server hosted on a 2 CPU/4 GB Vultr server serves 1.0+ million endpoints. Each relay connection consumes avg 180kb per second. 1 cpu core and 1G ram is enough to support 1000 relay concurrent connections. For sizing at large scale, see [scaling to 50,000–200,000 devices](https://rustdesk.com/blog/rustdesk-scale-50000-200000-devices).
|
||||
|
||||
## Article tutorials
|
||||
[Step-by-Step Guide: Self-Host RustDesk Server Pro on Cloud via Docker for Secure Remote Access](https://www.linkedin.com/pulse/step-by-step-guide-self-host-rustdesk-server-pro-cloud-montinaro-fwnmf/)
|
||||
|
||||
@@ -9,10 +9,6 @@ The RustDesk Server Pro web console is the main administrative interface for man
|
||||
|
||||
The web console is integrated in the RustDesk server Pro, serviced by the `21114` port.
|
||||
|
||||
{{% notice note %}}
|
||||
See also the [web console and custom client generator walkthrough](https://rustdesk.com/blog/rustdesk-web-console-custom-client-generator-port-21114).
|
||||
{{% /notice %}}
|
||||
|
||||
## What is the RustDesk Server Pro web console?
|
||||
|
||||
The web console is the main control plane for a self-hosted RustDesk Server Pro deployment. It is where administrators manage users, devices, groups, permissions, strategies, relay settings, SMTP, tokens, and custom clients.
|
||||
|
||||
@@ -10,7 +10,7 @@ weight: 600
|
||||
This FAQ covers the most common RustDesk Server Pro tasks: installation, conversion from OSS, upgrades, license migration, logging, SMTP issues, and device-management problems. If you are starting from scratch, begin with the [installation guide](/docs/en/self-host/rustdesk-server-pro/installscript/). If you already have a running server, the most common follow-up pages are [License](/docs/en/self-host/rustdesk-server-pro/license/), [SMTP](/docs/en/self-host/rustdesk-server-pro/smtp/), and [Client Deployment](/docs/en/self-host/client-deployment/).
|
||||
|
||||
{{% notice note %}}
|
||||
Troubleshooting help: [RustDesk not connecting](https://rustdesk.com/blog/rustdesk-not-connecting-troubleshooting), ["connected, waiting for image"](https://rustdesk.com/blog/rustdesk-connected-waiting-for-image), and [running Server Pro without Docker](https://rustdesk.com/blog/rustdesk-server-pro-without-docker).
|
||||
Troubleshooting help: ["connected, waiting for image"](https://rustdesk.com/blog/rustdesk-connected-waiting-for-image).
|
||||
{{% /notice %}}
|
||||
|
||||
## Which page should you use for each common task?
|
||||
|
||||
@@ -7,10 +7,6 @@ keywords: ["rustdesk ldap", "rustdesk server pro ldap", "rustdesk ldap authentic
|
||||
|
||||
Use this guide to connect RustDesk Server Pro to your LDAP directory for centralized authentication and user lookup.
|
||||
|
||||
{{% notice note %}}
|
||||
For a broader walkthrough of directory integration, see [RustDesk Active Directory, LDAP, and SSO](https://rustdesk.com/blog/rustdesk-active-directory-ldap-sso).
|
||||
{{% /notice %}}
|
||||
|
||||
## What does LDAP do in RustDesk Server Pro?
|
||||
|
||||
LDAP lets RustDesk Server Pro authenticate users against your directory service instead of managing separate local credentials for every account. On first successful login, RustDesk creates the user automatically based on the LDAP identity.
|
||||
|
||||
@@ -20,7 +20,7 @@ RustDesk Server Pro licensing is tied to the `hbbs` server, not to every relay n
|
||||
- If the server cannot reach the internet directly, you can configure a proxy for license verification
|
||||
|
||||
{{% notice note %}}
|
||||
Related reading: [how RustDesk Pro license cost and payment work](https://rustdesk.com/blog/rustdesk-pro-license-cost-how-to-pay), [lifetime vs. subscription licensing](https://rustdesk.com/blog/rustdesk-lifetime-perpetual-license), [what counts as a managed device](https://rustdesk.com/blog/what-counts-as-a-managed-device), and [upgrading a license mid-subscription](https://rustdesk.com/blog/upgrade-rustdesk-license-mid-subscription).
|
||||
Related reading: [what counts as a managed device](https://rustdesk.com/blog/what-counts-as-a-managed-device), and [upgrading a license mid-subscription](https://rustdesk.com/blog/upgrade-rustdesk-license-mid-subscription).
|
||||
{{% /notice %}}
|
||||
|
||||
## Buy license
|
||||
|
||||
@@ -7,10 +7,6 @@ keywords: ["rustdesk access control", "rustdesk device permissions", "rustdesk u
|
||||
|
||||
Use Access Control to decide which users or groups can connect to which devices in RustDesk Server Pro.
|
||||
|
||||
{{% notice note %}}
|
||||
For a practical overview, see [per-user access control, device groups, and the shared address book](https://rustdesk.com/blog/rustdesk-per-user-access-control-device-groups-shared-address-book).
|
||||
{{% /notice %}}
|
||||
|
||||
## What is Access Control in RustDesk Server Pro?
|
||||
|
||||
Access Control determines whether a user or group is allowed to reach a device. It is about connection eligibility, not about what the operator can do after the connection starts. For in-session permissions, use [Control Role](/docs/en/self-host/rustdesk-server-pro/control-role/).
|
||||
|
||||
Reference in New Issue
Block a user