Updated FAQ (markdown)

FAQ.md

@@ -1434,20 +1434,8 @@ So we always upgrade custom client to newest version later, No ETA yet, but we w
 
 - 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.
-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.
 
-It is also possible that your WAF blocks certain requests, e.g. `GET`.
-
-> User: Can we arrange an appointment for tomorrow so you can log on to the server and check it?
->
-> RustDesk: We can do nothing even we log on to your server. It is your proxy strip the 'GET' request header. I have no way to modify your proxy. I think you do not have the permission either.
->
-> User: I figured it out. I added the proxy information to the YAML file for each image, so that it doesn't take it from the .env file. This works perfectly for us.
-- Case 4:
+- Case 2:
 > User: I see "Build timeout" error
 > 
 > RustDesk: Could you try again then when you see this?
@@ -1459,7 +1447,8 @@ It is also possible that your WAF blocks certain requests, e.g. `GET`.
 > User: It is now ok in another browser and device.
 >
 > Conclusion: it seems `React` does not work well on some browsers. Refresing browser might also skip "Build timeout" error for this case.
-- Case 5:
+
+- Case 3:
 > User: I proceeded as suggested (remove both requests and recreated one). But it stays as "queued" for almost one hour.
 > <img width="974" height="293" alt="1aebaa45-3aab-4d73-b6ed-febae121936b" src="https://github.com/user-attachments/assets/48c51ce6-1691-42d7-b667-4af7cf3ea9f7" />
 >