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

Updated FAQ (markdown)

RustDesk
2025-06-06 16:32:10 +08:00
parent 369233c352
commit e4f6ab1408
1 changed files with 12 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
FAQ.md

@@ -366,7 +366,7 @@ https://github.com/rustdesk/rustdesk/discussions/6398#discussioncomment-9065991
![image](https://github.com/rustdesk/rustdesk/assets/71636191/5e16205d-c509-497a-bada-195291337f5e)
- Check your relay server (`hbbr`/21117) is using the same key as `hbbs`. You can see some errors related to connection to relay server in https://github.com/rustdesk/rustdesk/wiki/FAQ#access-logs on controlled side.
- Check if your relay server (`hbbr`/21117) is using the same key as `hbbs`. You can see some errors related to connection to relay server in https://github.com/rustdesk/rustdesk/wiki/FAQ#access-logs on controlled side.
```
[2025-06-06 14:02:38.370839 +08:00] INFO [src\rendezvous_mediator.rs:421] create_relay requested from 12.23.45.67:23108, relay_server: 150.109.58.178:21117, uuid: 2f9ec2fc-2f0e-4002-8e81-eb0eb1241d0b, secure: true
@@ -379,6 +379,17 @@ https://github.com/rustdesk/rustdesk/discussions/6398#discussioncomment-9065991
It may be caused by using wrong volumns mapping in docker compose file, please strictly follow https://rustdesk.com/docs/en/self-host/rustdesk-server-pro/installscript/docker/#docker-compose, or you changed `hbbs` key but forgot to sync to `hbbr` (and restart), or some other reasons.
> We have seen two cases having this `hbbr` key issue while upgading RustDesk server.
- If your cloud has problem with `21117` connection.
An user reported this, the `hbbr` logs below show the relay succeeded but close (It is FIN close, not RST) quickly. This indicated the connection closure likely occurred mid-stream between the server and client, leading us to suspect a cloud provider issue. The problem was indeed resolved after the user migrated to a different cloud service.
```
[2025-06-06 05:59:42.978845 +00:00] INFO [src/relay_server.rs:475] New relay request 6b07fbd4-4f29-4721-807b-7c8bd1f6fb02 from [::ffff:114.5.43.33:49925
[2025-06-06 05:59:43.138847 +00:00] INFO [src/relay_server.rs:459] Relay request 6b07fbd4-4f29-4721-807b-7c8bd1f6fb02 from [::ffff:11.12.29.91]:22903 got paired
[2025-06-06 05:59:43.138871 +00:00] INFO [src/relay_server.rs:465] Both are raw
[2025-06-06 05:59:43.138910 +00:00] INFO [src/relay_server.rs:471] Relay of [::ffff:11.12.29.91]:22903 closed
```
# CTRL-ALT-DEL does not work
- Make sure you install RustDesk on Windows, a system service is required for this so you have to install
- Check if `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\SoftwareSASGeneration`registry have correct value, 1 or 3. https://knowledge.broadcom.com/external/article/21517/ctrlaltdel-does-not-work-on-remote-contr.html