TheLanc3/rustdesk
1
0
Fork 0
mirror of https://github.com/rustdesk/rustdesk.git synced 2026-04-19 19:23:20 +03:00
Code Issues Packages Projects Releases Wiki Activity

Updated FAQ (markdown)

RustDesk
2025-07-10 00:48:07 +08:00
parent 06d3d47ea8
commit 7d1890b2e4
1 changed files with 48 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

62
FAQ.md

@@ -215,6 +215,19 @@ However, this layout mode may cause problems with certain programs such as video
This mode is for compatibility with RustDesk <= 1.1.9.
# `deadline has elapsed`
Try out [force relay](https://github.com/rustdesk/rustdesk/wiki/FAQ#force-relay) first. If it does not work, please check the possible reasons below:
- You do not install [`hbbr`](https://github.com/rustdesk/rustdesk-server-pro/discussions/372#discussioncomment-10475836) yet
- https://github.com/rustdesk/rustdesk-server-pro/discussions/386#discussioncomment-10631971
- The controlled side is configured with wrong key
Please check [access logs](https://github.com/rustdesk/rustdesk/wiki/FAQ#access-logs) on the controlled side, along with the `hbbs` and `hbbr` logs; you can find more clues.
- One user had below error in their access log sometimes. There seems complex networking problem between the pc and the `hbbr` server. Later he resolved this by migrating `hbbs/hbbr` to another machine.
> [2025-02-28 09:43:37.354355 -06:00] ERROR [src\server.rs:246] Failed to create relay connection for *.*.*.*:63731 with uuid 2dcd80ff-0169-4cfa-ab02-a72154e0ac65: deadline has elapsed
# Force relay
@@ -258,6 +271,41 @@ When you run RustDesk on Windows without installation, you will find the window
![image](https://github.com/rustdesk/rustdesk/assets/71636191/c26acbf5-6b2d-440a-8e24-0266fc8520c4)
![image](https://github.com/rustdesk/rustdesk/assets/71636191/5a8ed96e-3d2d-4ef0-a4db-023869aa66cf)
# Detailed UAC process
1, Even if the controller enters the administrator username and password in the RustDesk elevation prompt, someone on the remote side still needs to confirm it. However, the remote user does not need to enter the password—just click to approve.
2, During software installation, if a UAC prompt appears before the RustDesk elevation prompt, and this initial UAC requires a password, then simply click Cancel on the first UAC prompt, and then approve the RustDesk UAC prompt instead. After that, retry the installation. This time, the controller will be able to see the UAC prompt directly in RustDesk and can enter the administrator password.
So when a UAC prompt appears during installation, the correct steps are:
a. A UAC prompt pops up during installation. The controller requests elevation and enters the administrator username and password in the RustDesk prompt.
b. The user on the remote side rejects the first UAC prompt (which requires a password) and then approves the second RustDesk prompt (which doesn't require a password). At this point, RustDesk is successfully elevated.
c. Re-attempt the installation. Now the UAC prompt will be visible directly inside RustDesk, and the controller can enter the admin password.
Alternatively, you can preemptively elevate by selecting ["Elevate" from the RustDesk menu](https://github.com/rustdesk/rustdesk/wiki/FAQ#windows-uac). This will trigger the RustDesk UAC prompt directly on the remote side, which the user only needs to approve. Once elevated, the controller can perform installations and input UAC credentials as needed.
I have recorded and combined videos of both methods on the controller side into one screen for comparison. Please check the attachments:
elevate_when_needed.mp4 shows the case where a password is entered after a UAC appears (I used running CMD as administrator to simulate the installation).
elevate_from_menu.mp4 shows the case where elevation is initiated directly from the menu, allowing direct password entry.
Please review the videos and the description above to check if there are any differences in behavior depending on the situation.
- elevate_when_needed.mp4
https://github.com/user-attachments/assets/ed875a35-8a91-4932-915c-d94556dd6c34
- elevate_from_menu.mp4
https://github.com/user-attachments/assets/7648e8a7-3775-4d92-8cce-8ca69156c81f
# Access devices on another self-hosted or public server.
https://github.com/rustdesk/rustdesk/issues/6198#issuecomment-1794694273
![image](https://github.com/rustdesk/rustdesk/assets/71636191/9f61f06d-5b28-4787-b783-b7f1eb5d6430)
@@ -321,20 +369,6 @@ Edit:
>
> Value data: RunAsInvoker
# `deadline has elapsed`
Try out [force relay](https://github.com/rustdesk/rustdesk/wiki/FAQ#force-relay) first. If it does not work, please check the possible reasons below:
- You do not install [`hbbr`](https://github.com/rustdesk/rustdesk-server-pro/discussions/372#discussioncomment-10475836) yet
- https://github.com/rustdesk/rustdesk-server-pro/discussions/386#discussioncomment-10631971
- The controlled side is configured with wrong key
Please check [access logs](https://github.com/rustdesk/rustdesk/wiki/FAQ#access-logs) on the controlled side, along with the `hbbs` and `hbbr` logs; you can find more clues.
- One user had below error in their access log sometimes. There seems complex networking problem between the pc and the `hbbr` server. Later he resolved this by migrating `hbbs/hbbr` to another machine.
> [2025-02-28 09:43:37.354355 -06:00] ERROR [src\server.rs:246] Failed to create relay connection for *.*.*.*:63731 with uuid 2dcd80ff-0169-4cfa-ab02-a72154e0ac65: deadline has elapsed
# Connection reset by the peer
- Try out using force relay https://github.com/rustdesk/rustdesk/wiki/FAQ#force-relay.