0a79a19fa0
1. Move `nat-loopback-issues` from self-host/rustdesk-server-oss/ to self-host/ 2. Add notice and article link to `self-host/rustdesk-server-oss/_index.en.md`` and `self-host/rustdesk-server-pro/_index.en.md`
2.8 KiB
| title | weight | pre |
|---|---|---|
| RustDesk Server Pro | 200 | <b>2.2. </b> |
RustDesk Server Pro has more features compared to the open source version.
- No concurrent connection limit, aka no limit of simultaneous connections (OSS version has no limit either, but TeamViewer etc. have this limit)
- Web console
- API
- OIDC, LDAP, 2FA
- Address book
- Rename
- Log management (Connection, file transfer, alarm, etc.)
- Device management
- Security Settings sync
- Access control
- Multiple relay servers (automatically selects your closest relay)
{{% notice note %}} RustDesk Client ≥ 1.2.0 required {{% /notice %}} {{% notice note %}} If you build you own server on your home/office, and can't connect it though public IP/domain, please check this article. {{% /notice %}}
Hardware requirement
Lowest level VPS is enough for your use case. The server software is not CPU and memory intensive. Our public ID server hosted on a 2 CPU/4 GB Vultr server serves 1.5+ million endpoints.
Download
https://github.com/rustdesk/rustdesk-server-pro/releases/latest
Installation
Simple Install
To make life easy, we have developed scripts which take care of everything (install/upgrade/convert from open source) Simple Install Script.
{{% notice note %}} Don't forget to get your license from https://rustdesk.com/pricing.html, check license page for more details. {{% /notice %}}
Manual Installation
Almost the same as the open source version, but you do not need to run hbbs/hbbr with any arguments. These can be set later in web console.
-k _is set by default-r <server:host>is not needed any more if the relay server runs on the same machine with hbbs, and you can set multiple relay servers in the web console
Ports Required
You need port 21114-21119 TCP and 21116 UDP open, please ensure these ports are setup when you set firewall rules and Docker port mapping.
{{% notice note %}} You should use a proxy like Nginx to deliver this over HTTPS requiring port 443 to be opened. {{% /notice %}}