mirror of
https://github.com/rustdesk/rustdesk.git
synced 2026-04-19 19:23:20 +03:00
Updated FAQ (markdown)
11
FAQ.md
11
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
|
||||
|
||||
Reference in New Issue
Block a user