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-06-23 22:52:54 +08:00
parent 2f3ae70f8e
commit 38c86fea75
1 changed files with 1 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
FAQ.md

@@ -962,10 +962,10 @@ You can delete a device only when it is offline and disabled. If the device is a
Fails with error 403 https://github.com/rustdesk/rustdesk-server-pro/discussions/572
- Case 2:
The rustdesk server Pro runs behind the proxy, the proxy remove the `Authorization` header which our build server requires.
The custom client is not built on your server—it’s compiled on our build server. Your server communicates with ours via HTTP to request these builds. However, some users’ servers lack direct internet access and rely on a proxy. Unfortunately, this proxy strips critical HTTP header fields, which disrupts communication between the servers. As a result, the custom client fails to function correctly, leaving tasks perpetually queued and preventing the download link from being created.
- Case 3:
The build job remains in a `waiting` status. I verified that all background build tasks have completed successfully, but the web console does not reflect this. The issue appears to be related to the proxy configuration once again. While the build job is triggered via a `POST` request, the status is polled using a `GET` request that includes an `Authorization` header. However, the proxy is stripping the `Authorization` header from `GET` requests, preventing the status from being retrieved correctly.
# Unknown custom clients downloads and executions
https://github.com/rustdesk/rustdesk-server-pro/issues/312
@@ -986,12 +986,6 @@ or turn off below
![image](https://github.com/user-attachments/assets/243637fa-7008-440b-91af-ed16f21687eb)
# Building custom client on web console not work
Some users have reported issues where custom client tasks remain stuck in a queued or pending state, and the download link is never generated. Here’s why:
The custom client is not built on your server—it’s compiled on our build server. Your server communicates with ours via HTTP to request these builds. However, some users’ servers lack direct internet access and rely on a proxy. Unfortunately, this proxy strips critical HTTP header fields, which disrupts communication between the servers. As a result, the custom client fails to function correctly, leaving tasks perpetually queued and preventing the download link from being created.
# Desktop crash after a few minutes
Try turn off hardware codec please. https://www.reddit.com/r/rustdesk/comments/1h3z7fj/desktop_crash_after_a_few_minutes/