mirror of
https://github.com/rustdesk/doc.rustdesk.com.git
synced 2025-01-24 15:08:36 +01:00
commit
2fa5a030e7
@ -33,7 +33,7 @@ sudo zypper install --allow-unsigned-rpm ./rustdesk-<version>-suse.rpm
|
||||
### ~~X11 Required~~
|
||||
~~RustDesk does not support Wayland yet; you need switch to X11 manually.~~
|
||||
|
||||
RustDesk now has experimental Wayland support since v1.2.0.
|
||||
RustDesk now has experimental Wayland support since version 1.2.0.
|
||||
|
||||
#### Display Server
|
||||
|
||||
@ -69,4 +69,3 @@ The number in parentheses after `audit` is timestamp.
|
||||
{{% /notice %}}
|
||||
|
||||
If the output contains `avc: denied`, you need to add SELinux policies, please refer to [SELinux](https://rustdesk.com/docs/en/client/linux/selinux/).
|
||||
|
||||
|
@ -27,7 +27,7 @@ more. You have to enable "Input Monitoring" permission on local Mac side.
|
||||
Please follow this
|
||||
[https://github.com/rustdesk/rustdesk/issues/974#issuecomment-1185644923](https://github.com/rustdesk/rustdesk/issues/974#issuecomment-1185644923).
|
||||
|
||||
In 1.2.4, you can try out `Input source 2` which can be seen by clicking on keyboard icon on the toolbar.
|
||||
In version 1.2.4, you can try out `Input source 2` which can be seen by clicking on keyboard icon on the toolbar.
|
||||
{{% /notice %}}
|
||||
|
||||
To capture screen, you need to grant RustDesk **Accessibility** permission and **Screen Recording** permission. RustDesk will guide you to the settings window.
|
||||
@ -36,17 +36,13 @@ To capture screen, you need to grant RustDesk **Accessibility** permission and *
|
||||
| --- | --- |
|
||||
| ![](/docs/en/client/mac/images/acc.png) | ![](/docs/en/client/mac/images/acc3.png?v2) |
|
||||
|
||||
If you have enabled it in the settings window, but RustDesk still warns. Please remove RustDesk from the settings windows by the `-` button, and click on `+` button, select RustDesk in `/Applications`.
|
||||
If you have enabled it in the settings window, but RustDesk still warns. Please remove `RustDesk` from the settings windows by the `-` button, and click on `+` button, select `RustDesk` in `Applications`.
|
||||
|
||||
{{% notice note %}}
|
||||
[https://github.com/rustdesk/rustdesk/issues/3261](https://github.com/rustdesk/rustdesk/issues/3261)
|
||||
|
||||
Other helpless attempts:
|
||||
|
||||
```
|
||||
tccutil reset ScreenCapture com.carriez.RustDesk
|
||||
tccutil reset Accessibility com.carriez.RustDesk
|
||||
```
|
||||
[https://github.com/rustdesk/rustdesk/issues/3261](https://github.com/rustdesk/rustdesk/issues/3261) <br>
|
||||
Other helpless attempts: <br>
|
||||
`tccutil reset ScreenCapture com.carriez.RustDesk` <br>
|
||||
`tccutil reset Accessibility com.carriez.RustDesk` <br>
|
||||
Reboot is still required.
|
||||
{{% /notice %}}
|
||||
|
||||
|
@ -16,7 +16,8 @@ Go to https://github.com/rustdesk/rustdesk/fork and click "Create fork".
|
||||
{{% notice note %}}
|
||||
You only need to do this if you want to change the default server and public key.
|
||||
|
||||
The server URL and key you are using is hidden from other users on GitHub however they can download your client and connect to your server. If you require a fully private repo you can import the RustDesk Client repo using https://github.com/new/import. **If you use a private repo you have limited amounts of builds you can create per month, if you need more you will need to have a paid GitHub account.**
|
||||
The server URL and key you are using is hidden from other users on GitHub however they can download your client and connect to your server. If you require a fully private repo you can import the RustDesk Client repo using https://github.com/new/import. <br>
|
||||
**If you use a private repo you have limited amounts of builds you can create per month, if you need more you will need to have a paid GitHub account.**
|
||||
{{% /notice %}}
|
||||
|
||||
On your fork you just created go to "Settings → Secrets and variables → Actions".
|
||||
|
@ -138,7 +138,7 @@ You'll might need to disable building Flutter Rust Bridge from `build.rs` file,
|
||||
sed -i "s/gen_flutter_rust_bridge();/\/\//g" build.rs
|
||||
```
|
||||
|
||||
#### Building rustdesk lib
|
||||
#### Building RustDesk library
|
||||
At this step you'll build `librustdesk.so` file.
|
||||
|
||||
First, add triplet to rust:
|
||||
@ -215,4 +215,3 @@ If you want you might move builded app somewhere else, feel free to run:
|
||||
```
|
||||
mv build/app/outputs/flutter-apk/app-arm64-v8a-release.apk ../rustdesk-release.apk
|
||||
```
|
||||
|
||||
|
@ -45,7 +45,7 @@ Desktop versions use [Sciter](https://sciter.com/) for GUI, please download [sci
|
||||
|
||||
`rust-bindgen` depends on `clang`, download [LLVM](https://github.com/llvm/llvm-project/releases) and install, add System environment variable `LIBCLANG_PATH`=`<llvm_install_dir>/bin`.
|
||||
|
||||
You can download version 15.02 of the LLVM binaries here: [64 bit](https://github.com/llvm/llvm-project/releases/download/llvmorg-15.0.2/LLVM-15.0.2-win64.exe) / [32 bit](https://github.com/llvm/llvm-project/releases/download/llvmorg-15.0.2/LLVM-15.0.2-win32.exe).
|
||||
You can download version 15.0.2 of the LLVM binaries here: [64 bit](https://github.com/llvm/llvm-project/releases/download/llvmorg-15.0.2/LLVM-15.0.2-win64.exe) / [32 bit](https://github.com/llvm/llvm-project/releases/download/llvmorg-15.0.2/LLVM-15.0.2-win32.exe).
|
||||
|
||||
### Build
|
||||
|
||||
@ -59,4 +59,3 @@ wget https://raw.githubusercontent.com/c-smile/sciter-sdk/master/bin.win/x64/sci
|
||||
mv sciter.dll target/debug
|
||||
cargo run
|
||||
```
|
||||
|
||||
|
@ -10,7 +10,7 @@ Support is available via our [Discord](https://discord.com/invite/nDceKgxnkV) fo
|
||||
|
||||
### Basic Setup
|
||||
|
||||
https://rustdesk.com/docs/en/self-host/rustdesk-server-oss/install/#set-up-your-own-server-instance-manually
|
||||
[Set up your own server instance manually.](https://rustdesk.com/docs/en/self-host/rustdesk-server-oss/install/#set-up-your-own-server-instance-manually)
|
||||
|
||||
### Ports Required
|
||||
|
||||
|
@ -8,7 +8,7 @@ pre: "<b>2.3. </b>"
|
||||
|
||||
There are a number of ways to configure RustDesk Clients to use your own self-hosted server, we will cover some below.
|
||||
|
||||
### 1, Manual Config
|
||||
### 1. Manual Config
|
||||
|
||||
In the main RustDesk Client home click on the Menu button [ ⋮ ] next to your ID then click on Network, you can now unlock the settings using elevated privileges and set your ID, Relay, API and Keys.
|
||||
|
||||
@ -43,7 +43,7 @@ e.g. your API Server runs on default https port, please specify `API Server` wit
|
||||
|
||||
If you still can not confirm the value of `API Server`, please go to the welcome page of web console, the `API Server` is shown in above picture (The input box with `API:` label).
|
||||
|
||||
### 2, Setup Using Import or Export
|
||||
### 2. Setup Using Import or Export
|
||||
|
||||
1. Use the steps [above](https://rustdesk.com/docs/en/self-host/client-configuration/#manual-config) to configure RustDesk Client on a Device.
|
||||
2. Using the above machine go to Settings then Network and unlock.
|
||||
@ -54,7 +54,7 @@ If you still can not confirm the value of `API Server`, please go to the welcome
|
||||
7. It will automatically paste the settings in.
|
||||
8. Click `Apply`.
|
||||
|
||||
### 3, Automatic Config
|
||||
### 3. Automatic Config
|
||||
|
||||
The easiest way to setup automatically is using deployment scripts found [here](https://rustdesk.com/docs/en/self-host/client-deployment/).
|
||||
|
||||
@ -62,7 +62,7 @@ You can fix the Password is required and use a reverse Base64 string in the form
|
||||
|
||||
You can also use the steps from [above](https://rustdesk.com/docs/en/self-host/client-configuration/#setup-using-import-or-export) to export the string, remove any `=` at the start or end of the string. Restart RustDesk Client if settings don't show.
|
||||
|
||||
### 4, Put config in rustdesk.exe file name (Windows only)
|
||||
### 4. Put config in rustdesk.exe file name (Windows only)
|
||||
|
||||
Change `rustdesk.exe` to rustdesk-`host=<host-ip-or-name>,key=<public-key-string>`.exe, e.g. rustdesk-`host=192.168.1.137,key=xfdsfsd32=32`.exe. You can see the config result in the About Window below.
|
||||
|
||||
@ -81,23 +81,18 @@ If there are invalid characters in the key which can not be used in a Windows fi
|
||||
repeat this process until you get valid characters.
|
||||
{{% /notice %}}
|
||||
|
||||
#### add `--` to the name
|
||||
#### Add `--` to the name
|
||||
At the end, add `--`.
|
||||
|
||||
Example: `rustdesk-licensed--{encrypted string}--.exe`
|
||||
|
||||
We have noticed that in some cases, when double downloaded, something like `copy (1)` is added to the end of the file name, and this ruins the config.
|
||||
|
||||
By adding `-- `at the end right after our config string, even if something is added to the file name, it won't corrupt the config string, and RustDesk will correctly retrieve it.
|
||||
By adding `--` at the end right after our config string, even if something is added to the file name, it won't corrupt the config string, and RustDesk will correctly retrieve it.
|
||||
|
||||
{{% notice note %}}
|
||||
{{% /notice %}}
|
||||
### 5. [Hardcoding Custom Settings](https://rustdesk.com/docs/en/self-host/client-configuration/hardcode-settings/)
|
||||
|
||||
### 5, [Hardcoding](https://rustdesk.com/docs/en/self-host/client-configuration/hardcode-settings/)
|
||||
|
||||
### 6, use command line "--config"
|
||||
### 6. Use command line `--config`
|
||||
`rustdesk.exe --config <config-string>`
|
||||
|
||||
You can get the config string from web console (you can see it on above picture) or from RustDesk client `Settings` -> `Network` (here is a dicussion about this, https://github.com/rustdesk/rustdesk/discussions/7118).
|
||||
|
||||
|
||||
You can get the config string from web console (you can see it on above picture) or from RustDesk client "Settings → Network" ([here](https://github.com/rustdesk/rustdesk/discussions/7118) is a discussion about this).
|
||||
|
@ -5,8 +5,8 @@ weight: 49
|
||||
|
||||
### Custom Server
|
||||
{{% notice note %}}
|
||||
To hardcode custom server settings into your executables you must [build](https://rustdesk.com/docs/en/dev/build/) the client yourself on your machine or [with GitHub Actions](https://rustdesk.com/docs/en/dev/build/all/).<br>
|
||||
**Noted**: [self-hosted runners](https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners) for Arm are used in our GitHub actions, please set it up yourself.
|
||||
To hardcode custom server settings into your executables you must [build](https://rustdesk.com/docs/en/dev/build/) the client yourself on your machine or [with GitHub Actions](https://rustdesk.com/docs/en/dev/build/all/). <br>
|
||||
**Note**: [self-hosted runners](https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners) for Arm are used in our GitHub actions, please set it up yourself.
|
||||
{{% /notice %}}
|
||||
{{% notice note %}}
|
||||
**If you set either of these values without setting the other, your executable will not work!**
|
||||
@ -32,11 +32,10 @@ This should be a string such as
|
||||
OeVuKk5nlHiXp+APNn0Y3pC1Iwpwn44JGqrQCsWqmBw=
|
||||
```
|
||||
|
||||
### API_SERVER
|
||||
By default the API_SERVER runs on `http://rustdesk.my-domain.com:21114`, you'd better run it behind nginx for security with https.
|
||||
#### API_SERVER
|
||||
By default the API_SERVER runs on `http://rustdesk.my-domain.com:21114`, you'd better run it behind Nginx for security with HTTPS.
|
||||
|
||||
This should be a string such as
|
||||
```
|
||||
https://rustdesk.my-domain.com
|
||||
```
|
||||
|
||||
|
@ -47,13 +47,13 @@ function getLatest()
|
||||
$src = [System.Text.Encoding]::Unicode.GetBytes($Page.Content)
|
||||
$HTML.write($src)
|
||||
}
|
||||
|
||||
|
||||
# Current example link: https://github.com/rustdesk/rustdesk/releases/download/1.2.3/rustdesk-1.2.3-x86_64.exe
|
||||
$Downloadlink = ($HTML.Links | Where {$_.href -match '(.)+\/rustdesk\/rustdesk\/releases\/download\/\d{1}.\d{1,2}.\d{1,2}(.{0,3})\/rustdesk(.)+x86_64.exe'} | select -first 1).href
|
||||
|
||||
|
||||
# bugfix - sometimes you need to replace "about:"
|
||||
$Downloadlink = $Downloadlink.Replace('about:', 'https://github.com')
|
||||
|
||||
|
||||
$Version = "unknown"
|
||||
if ($Downloadlink -match './rustdesk/rustdesk/releases/download/(?<content>.*)/rustdesk-(.)+x86_64.exe')
|
||||
{
|
||||
@ -67,7 +67,7 @@ function getLatest()
|
||||
}
|
||||
|
||||
# Create object to return
|
||||
$Result = New-Object PSObject -Property
|
||||
$Result = New-Object PSObject -Property
|
||||
@{
|
||||
Version = $Version
|
||||
Downloadlink = $Downloadlink
|
||||
@ -83,7 +83,7 @@ $rdver = ((Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Un
|
||||
|
||||
if ($rdver -eq $RustDeskOnGitHub.Version)
|
||||
{
|
||||
Write-Output "RustDesk $rdver is the newest version"
|
||||
Write-Output "RustDesk $rdver is the newest version."
|
||||
Exit
|
||||
}
|
||||
|
||||
@ -358,4 +358,3 @@ fi
|
||||
echo "Password: $rustdesk_pw"
|
||||
echo "..............................................."
|
||||
```
|
||||
|
||||
|
@ -4,7 +4,7 @@ weight: 20
|
||||
---
|
||||
|
||||
{{% notice note %}}
|
||||
Windows security policy is tricky, if this tutorial does not work for you, or you encounter unstable connection, please migrate to `Linux` server.
|
||||
Windows security policy is tricky, if this tutorial does not work for you, or you encounter unstable connection, please migrate to a Linux server.
|
||||
{{% /notice %}}
|
||||
|
||||
### A crossroads
|
||||
@ -55,7 +55,7 @@ nssm install "RustDesk hbbr service" "C:\Program Files\RustDesk Server\hbbr.exe"
|
||||
- You can change `RustDesk hbbr service` to whatever you desire to name hbbr the service
|
||||
- You can change `C:\Program Files\RustDesk Server\hbbs.exe` to wherever you placed the RustDesk binaries
|
||||
- You can change `C:\Program Files\RustDesk Server\hbbr.exe` to wherever you placed the RustDesk binaries
|
||||
- You do not need the `-k _` option which is optional, it's just for better security. In `Pro` version, please ignore `-k _` which is applied implicitly.
|
||||
- You do not need the `-k _` option which is optional, it's just for better security. In the `Pro` version, please ignore `-k _` which is applied implicitly.
|
||||
|
||||
**Command templates:**
|
||||
|
||||
@ -103,7 +103,7 @@ Download the Windows version of [RustDesk Server](https://github.com/rustdesk/ru
|
||||
|
||||
```cmd
|
||||
cd C:\rustdesk-server-windows-x64
|
||||
pm2 start hbbs.exe
|
||||
pm2 start hbbs.exe
|
||||
pm2 start hbbr.exe
|
||||
pm2 save
|
||||
```
|
||||
@ -114,4 +114,3 @@ pm2 save
|
||||
pm2 log hbbr
|
||||
pm2 log hbbs
|
||||
```
|
||||
|
||||
|
@ -7,8 +7,8 @@ When logging in to your account, turning on Two-Factor Authentication (2FA) veri
|
||||
|
||||
Our web console currently supports two kinds of 2FA:
|
||||
|
||||
1. Email verification.
|
||||
2. TOTP. A third-party authentication app is required to generate the verification code, such as [Authy](https://authy.com/), [Microsoft](https://www.microsoft.com/en-us/security/mobile-authenticator-app/ ), [Google](https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2/) authentication app.
|
||||
1. Email verification
|
||||
2. TOTP. A third-party authentication app is required to generate the verification code, such as [Authy](https://authy.com), [Microsoft Authenticator](https://www.microsoft.com/en-us/security/mobile-authenticator-app/) and [Google Authenticator](https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2) authentication app.
|
||||
|
||||
You first need to go to the account settings page.
|
||||
|
||||
@ -19,7 +19,8 @@ You first need to go to the account settings page.
|
||||
To enable email verification for login, you need:
|
||||
|
||||
1. Set email.
|
||||
2. Enable the "Enable email login verification" option.
|
||||
2. Enable the `Enable email login verification` option.
|
||||
3. Click on `Submit`.
|
||||
|
||||
![](/docs/en/self-host/rustdesk-server-pro/2FA/images/2-2fa-email-1.png)
|
||||
|
||||
@ -27,7 +28,6 @@ When we log in next time, RustDesk will send us a verification code email, and t
|
||||
|
||||
![](/docs/en/self-host/rustdesk-server-pro/2FA/images/2-2fa-email-2.png)
|
||||
|
||||
|
||||
### TOTP
|
||||
|
||||
TOTP is a widely used 2FA method, so in the web console of RustDesk Server Pro, 2FA refers to TOTP verification.
|
||||
@ -35,20 +35,18 @@ TOTP is a widely used 2FA method, so in the web console of RustDesk Server Pro,
|
||||
#### Prepare authentication app
|
||||
|
||||
First, you need to prepare an authentication app.
|
||||
You can choose from these types [Authy](https://authy.com/), [Microsoft](https://www.microsoft.com/en-us/security/mobile-authenticator-app/), [Google](https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2/) authentication app.
|
||||
You can choose from these types [Authy](https://authy.com), [Microsoft Authenticator](https://www.microsoft.com/en-us/security/mobile-authenticator-app/) and [Google Authenticator](https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2) authentication app.
|
||||
|
||||
#### Enable 2FA
|
||||
|
||||
When the "Enable 2FA" button is displayed on the settings page, it means that 2FA is not currently enabled.
|
||||
When the `Enable 2FA` button is displayed on the settings page, it means that 2FA is not currently enabled.
|
||||
|
||||
![](/docs/en/self-host/rustdesk-server-pro/2FA/images/3-2fa-enable-1.png)
|
||||
|
||||
|
||||
Click the button and a form will pop up to enable 2FA.
|
||||
|
||||
![](/docs/en/self-host/rustdesk-server-pro/2FA/images/3-2fa-enable-2.png)
|
||||
|
||||
|
||||
Open the authenticator app, add an account by scanning the QR code.
|
||||
|
||||
If you are inconvenient to scan the QR code, you can also enter the code here directly.
|
||||
@ -57,15 +55,15 @@ If you are inconvenient to scan the QR code, you can also enter the code here di
|
||||
|
||||
After adding the account in the authenticator app, enter the verification code in the authenticator app to turn on 2FA.
|
||||
|
||||
After 2FA is successfully turned on, RustDesk Server Pro will also be bound to 6 **backup codes**. So that you can use these **bacoup codes** to pass the verification even if you are unable to use the authenticator app.
|
||||
After 2FA is successfully turned on, RustDesk Server Pro will also be bound to 6 **backup codes**. So that you can use these **backup codes** to pass the verification even if you are unable to use the authenticator app.
|
||||
|
||||
![](/docs/en/self-host/rustdesk-server-pro/2FA/images/3-2fa-enable-4.png)
|
||||
|
||||
|
||||
**Note**:
|
||||
|
||||
{{% notice note %}}
|
||||
1. These backup codes can only be used once.
|
||||
|
||||
2. Please keep the backup codes in a safe place.
|
||||
{{% /notice %}}
|
||||
|
||||
#### Login verification
|
||||
|
||||
@ -73,22 +71,18 @@ When 2FA is enabled, email login verification is no longer used. We will be usin
|
||||
|
||||
![](/docs/en/self-host/rustdesk-server-pro/2FA/images/3-2fa-enable-login-5.png)
|
||||
|
||||
|
||||
When logging in, you will be redirected to the verification page.
|
||||
|
||||
![](/docs/en/self-host/rustdesk-server-pro/2FA/images/3-2fa-enable-login-6.png)
|
||||
|
||||
|
||||
#### Modify settings
|
||||
|
||||
When 2FA is enabled, modifying account settings requires additional 2FA verification.
|
||||
|
||||
![](/docs/en/self-host/rustdesk-server-pro/2FA/images/3-2fa-settings-1.png)
|
||||
|
||||
|
||||
![](/docs/en/self-host/rustdesk-server-pro/2FA/images/3-2fa-settings-2.png)
|
||||
|
||||
|
||||
#### 2FA state
|
||||
|
||||
2FA has a total of 3 states: not enabled, enabled and expired.
|
||||
@ -99,4 +93,6 @@ When 2FA is enabled, modifying account settings requires additional 2FA verifica
|
||||
|
||||
![](/docs/en/self-host/rustdesk-server-pro/2FA/images/3-2fa-state-expired.png)
|
||||
|
||||
**Note**: 2FA can still be used normally after it expires. It just means that the 2FA settings haven't been changed for a long time (default 180 days). For security reasons, we recommend re-enabling 2FA, so the secret data can been updated.
|
||||
{{% notice note %}}
|
||||
2FA can still be used normally after it expires. It just means that the 2FA settings haven't been changed for a long time (default 180 days). For security reasons, we recommend re-enabling 2FA, so the secret data can been updated.
|
||||
{{% /notice %}}
|
||||
|
@ -6,20 +6,20 @@ pre: "<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](/docs/en/self-host/rustdesk-server-pro/console/)
|
||||
- No concurrent connection limit, aka no limit of simultaneous connections (OSS version has no limit either, but TeamViewer etc. have this limit)
|
||||
- [Web console](https://rustdesk.com/docs/en/self-host/rustdesk-server-pro/console/)
|
||||
- API
|
||||
- [OIDC](/docs/en/self-host/rustdesk-server-pro/oidc/), LDAP, [2FA](/docs/en/self-host/rustdesk-server-pro/2fa/)
|
||||
- [OIDC](https://rustdesk.com/docs/en/self-host/rustdesk-server-pro/oidc/), LDAP, [2FA](https://rustdesk.com/docs/en/self-host/rustdesk-server-pro/2fa/)
|
||||
- Address book
|
||||
- Rename
|
||||
- Log management (Connection, file transfer, alarm, etc.)
|
||||
- Device management
|
||||
- [Security Settings sync](/docs/en/self-host/rustdesk-server-pro/strategy/)
|
||||
- [Access control](/docs/en/self-host/rustdesk-server-pro/permissions/)
|
||||
- [Multiple relay servers](/docs/en/self-host/rustdesk-server-pro/relay/) (automatically selects your closest relay)
|
||||
- [Security Settings sync](https://rustdesk.com/docs/en/self-host/rustdesk-server-pro/strategy/)
|
||||
- [Access control](https://rustdesk.com/docs/en/self-host/rustdesk-server-pro/permissions/)
|
||||
- [Multiple relay servers](https://rustdesk.com/docs/en/self-host/rustdesk-server-pro/relay/) (automatically selects your closest relay)
|
||||
|
||||
{{% notice note %}}
|
||||
RustDesk Client >= 1.2.0 required
|
||||
RustDesk Client ≥ 1.2.0 required
|
||||
{{% /notice %}}
|
||||
|
||||
### Hardware requirement
|
||||
@ -54,4 +54,3 @@ You need port 21114-21119 TCP and 21116 UDP open, please ensure these ports are
|
||||
{{% notice note %}}
|
||||
You should use a proxy like Nginx to deliver this over HTTPS requiring port 443 to be opened.
|
||||
{{% /notice %}}
|
||||
|
||||
|
@ -29,23 +29,23 @@ Non-administrator users can also login to browse their device and logs, change t
|
||||
### Automatic Configs
|
||||
By Clicking on `Windows EXE` you will be able to get the configs for your own RustDesk Server Pro, this will help configure your clients.
|
||||
|
||||
For Windows clients, you can leave out the custom server configuration and put the configuration information in the `rustdesk.exe` filename instead. As shown above, please go to the console welcome page and click on `Windows EXE`. **Client >=1.1.9 Required.**
|
||||
For Windows clients, you can leave out the custom server configuration and put the configuration information in the `rustdesk.exe` filename instead. As shown above, please go to the console welcome page and click on `Windows EXE`. **Client ≥ 1.1.9 required.**
|
||||
|
||||
You can use this in conjunction with [client config](https://rustdesk.com/docs/en/self-host/client-configuration/) and [deployment scripts](https://rustdesk.com/docs/en/self-host/client-deployment/) to setup your clients.
|
||||
|
||||
### Creating a new user other than the default `admin` user
|
||||
1. Click On `Users` on the left hand menu.
|
||||
1. Click on `Users` on the left hand menu.
|
||||
2. Create another account with `administrator` enabled.
|
||||
3. Log in with the new administrative account.
|
||||
4. Delete the `admin` on `Users` page.
|
||||
|
||||
### Creating a new user
|
||||
1. Click On `Users` on the left hand menu.
|
||||
1. Click on `Users` on the left hand menu.
|
||||
2. Create a new user.
|
||||
3. Select what group they should be in (if you need to add new groups please keep reading).
|
||||
|
||||
### Add a new Group
|
||||
1. Click On `Groups` on the left hand menu.
|
||||
1. Click on `Groups` on the left hand menu.
|
||||
2. Create a new group.
|
||||
3. Once created you can allow groups access each other, Click `Edit`.
|
||||
4. Select the relevant groups you want access (it automatically adds them in the corresponding group).
|
||||
|
@ -61,4 +61,4 @@ services:
|
||||
|
||||
The run `docker compose up -d`.
|
||||
|
||||
> If you have problem with seLinux on Fedora, please check this https://github.com/rustdesk/rustdesk-server/issues/230
|
||||
> If you have problem with seLinux on Fedora, please check this [issue](https://github.com/rustdesk/rustdesk-server/issues/230).
|
||||
|
@ -6,7 +6,7 @@ weight: 10
|
||||
{{% notice note %}}
|
||||
Don't forget to get your license from [https://rustdesk.com/pricing.html](https://rustdesk.com/pricing.html), check [license](https://rustdesk.com/docs/en/self-host/rustdesk-server-pro/license/) page for more details.
|
||||
|
||||
Please read [OSS installation](/docs/en/self-host/rustdesk-server-oss/install/) first before doing this simple install. You can know more underlying details there.
|
||||
Please read [OSS installation](https://rustdesk.com/docs/en/self-host/rustdesk-server-oss/install/) first before doing this simple install. You can know more underlying details there.
|
||||
{{% /notice %}}
|
||||
|
||||
### Install
|
||||
@ -76,5 +76,3 @@ chmod +x restore.sh
|
||||
Copy the backup file into the same folder as the restore.sh file and then run `./restore.sh`.
|
||||
|
||||
This will restore your server to how it was prior, you will need to revoke your [license](https://rustdesk.com/docs/en/self-host/rustdesk-server-pro/license/) to move it to the restored server.
|
||||
|
||||
|
||||
|
@ -4,7 +4,7 @@ weight: 2
|
||||
---
|
||||
|
||||
{{% notice note %}}
|
||||
Windows security policy is tricky, if this tutorial does not work for you, or you encounter unstable connection, please migrate to `Linux` server.
|
||||
Windows security policy is tricky, if this tutorial does not work for you, or you encounter unstable connection, please migrate to a Linux server.
|
||||
{{% /notice %}}
|
||||
|
||||
### Install
|
||||
@ -12,7 +12,7 @@ Windows security policy is tricky, if this tutorial does not work for you, or yo
|
||||
1. Get your license from [https://rustdesk.com/pricing.html](https://rustdesk.com/pricing.html), check [license](https://rustdesk.com/docs/en/self-host/rustdesk-server-pro/license/) page for more details.
|
||||
2. Download the the Windows installer from [GitHub](https://github.com/rustdesk/rustdesk-server-pro/releases/latest).
|
||||
3. Unzip the Windows installer.
|
||||
4. Run the Installer and follow the steps on screen. (or manually install with [PM2 OR NSSM](/docs/en/self-host/rustdesk-server-oss/windows/))
|
||||
4. Run the Installer and follow the steps on screen. Or manually install with [PM2 or NSSM](https://rustdesk.com/docs/en/self-host/rustdesk-server-oss/windows/).
|
||||
5. Once its completed open RustDesk Server.
|
||||
6. Follow the prompts as they guide you through the install.
|
||||
7. Click `Services` and then `Start`.
|
||||
|
@ -6,12 +6,11 @@ weight: 17
|
||||
### RustDesk Pro - Install Additional Relay Servers with Geo Location using docker
|
||||
|
||||
{{% notice note %}}
|
||||
[The simple install](/docs/en/self-host/rustdesk-server-pro/installscript/) creates a relay server (the `hbbr` process) implicitly on the same machine, you do not need to specify relay server explicitly.
|
||||
[The simple install](https://rustdesk.com/docs/en/self-host/rustdesk-server-pro/installscript/) creates a relay server (the `hbbr` process) implicitly on the same machine, you do not need to specify relay server explicitly.
|
||||
|
||||
If you wanna create additional relay server explicitly on another machine, please run `hbbr` by following [OSS installation](/docs/en/self-host/rustdesk-server-oss/install/). You can find `hbbr` in `rustdesk-server-linux-amd64.tar.gz`, `rustdesk-server-hbbr_<version>-<arch>.deb`, `rustdesk-server-windows-x86_64.tar.gz` or in `docker` (`sudo docker run ... rustdesk/rustdesk-server-pro hbbr`)
|
||||
If you wanna create additional relay server explicitly on another machine, please run `hbbr` by following [OSS installation](https://rustdesk.com/docs/en/self-host/rustdesk-server-oss/install/). You can find `hbbr` in `rustdesk-server-linux-amd64.tar.gz`, `rustdesk-server-hbbr_<version>-<arch>.deb`, `rustdesk-server-windows-x86_64.tar.gz` or in `docker` (`sudo docker run ... rustdesk/rustdesk-server-pro hbbr`).
|
||||
|
||||
`hbbr` does not require a license and is the same as the open source version.
|
||||
|
||||
{{% /notice %}}
|
||||
|
||||
You can have several relay servers running across the globe and leverage GeoLocation to use the closest relay server, giving you a faster experience when connecting to remote computers.
|
||||
@ -110,7 +109,7 @@ You can automate the [download process](https://dev.maxmind.com/geoip/updating-d
|
||||
|
||||
#### Change settings in RustDesk Pro Web Console
|
||||
|
||||
Add your relay server IP addresses or DNS names (DNS is supported in version `1.1.11`) to the the `Relay Servers`. **Port is not required, `21117` port is used explictly.** <br>
|
||||
Add your relay server IP addresses or DNS names (DNS is supported as of version 1.1.11) to the `Relay Servers`. **Port is not required, `21117` port is used explicitly.** <br>
|
||||
<img width="500" alt="image" src="https://github.com/rustdesk/doc.rustdesk.com/assets/642149/c4452ba4-5e1d-437a-ae1d-fc0070bfa26c">
|
||||
|
||||
Add a Geo Override but adding the server IP address and the coordinates where the server is located. <br>
|
||||
@ -143,4 +142,3 @@ You can also confirm the relay requests directly on your hbbr instances, simply
|
||||
INFO [src/relay_server.rs:436] Relayrequest 0593e64e-4fe8-4a59-a94f-b3420ab043eb from [::ffff:100.100.123.233]:52038 got paired
|
||||
INFO [src/relay_server.rs:442] Both are raw
|
||||
```
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user