From 2f3ae70f8e2b3229f912b35e3479b905101fb5ad Mon Sep 17 00:00:00 2001
From: RustDesk <71636191+rustdesk@users.noreply.github.com>
Date: Mon, 23 Jun 2025 22:48:02 +0800
Subject: [PATCH] Updated FAQ (markdown)

---
 FAQ.md | 11 +++++++++--
 1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/FAQ.md b/FAQ.md
index 8003970..23155b0 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -956,8 +956,15 @@ https://github.com/rustdesk/rustdesk/discussions/11006
 # Can not delete devices on web console
 You can delete a device only when it is offline and disabled. If the device is always online, you cannot delete it because it will reconnect and appear online again after deletion. In such cases, you can only disable it. A disabled device has the same effect as a deleted one—it becomes inaccessible and does not continues to occupy a slot in your license's device limit.
 
-# Custom Client creation fails with error 403
-https://github.com/rustdesk/rustdesk-server-pro/discussions/572
+# Custom Client build / creation failures
+
+- Case 1: 
+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.
+- 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