TheLanc3/rustdesk
1
0
Fork 0
mirror of https://github.com/rustdesk/rustdesk.git synced 2026-04-20 09:53:20 +03:00
Code Issues Packages Projects Releases Wiki Activity

Updated FAQ (markdown)

RustDesk
2025-09-22 10:14:08 +08:00
parent fe9b9a97e8
commit 4aa00d4c8c
1 changed files with 14 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
FAQ.md

@@ -1504,3 +1504,17 @@ https://github.com/rustdesk/rustdesk/issues/2018#issuecomment-3239374964
# "color must be int, or tuple of one or two elements error" when build custom client # "color must be int, or tuple of one or two elements error" when build custom client
You can adjust the color mode bit depth in https://www.photopea.com/ and save them again. You can adjust the color mode bit depth in https://www.photopea.com/ and save them again.
# Okta : error sending request for url (<OIDC auth URL>): error trying to connect: bad protocol version
> Any idea how we can get things working on 1.3 across the board (eventually)?
Sorry, no. `native-tls` might not support TLS 1.3, depending on the operating system.
On the rust side:
https://github.com/seanmonstar/reqwest/issues/2025#issuecomment-2010674997
https://github.com/seanmonstar/reqwest/issues/2025#issuecomment-2010698600
For windows, you may need to manually enable it.
https://learn.microsoft.com/en-us/answers/questions/1253847/how-to-enable-tls-1-3-on-windows-server-2022-havin
We use "native-tls" for better TLS support. We have to wait for a better solution at the lower level.
https://github.com/rustdesk/rustdesk-server-pro/issues/189