Updated FAQ (markdown)

RustDesk
2026-03-18 23:12:48 +08:00
parent 7d1df33c77
commit 6754fb8e70

2
FAQ.md

@@ -1428,7 +1428,7 @@ It is also possible that your WAF blocks certain requests, e.g. `GET`.
> Conclusion: it seems `React` does not work well on some browsers. Refresing browser might also skip "Build timeout" error for this case. > 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 5:
> User: I proceeded as suggested (remove both requests and recreated one). But it stays as "queued" for almost one hour. > 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" /> > <img width="974" height="293" alt="1aebaa45-3aab-4d73-b6ed-febae121936b" src="https://github.com/user-attachments/assets/48c51ce6-1691-42d7-b667-4af7cf3ea9f7" />
> User: We found the issue and solved it. You can close this case. > User: We found the issue and solved it. You can close this case.
> RustDesk: Could you let me know the reason? > RustDesk: Could you let me know the reason?
> User: The VM is configured behind a proxy but the container was not configured to use the proxy. > User: The VM is configured behind a proxy but the container was not configured to use the proxy.