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

Updated FAQ (markdown)

RustDesk
2025-06-06 19:59:59 +08:00
parent e4f6ab1408
commit fd34ddc413
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
FAQ.md

@@ -379,9 +379,9 @@ https://github.com/rustdesk/rustdesk/discussions/6398#discussioncomment-9065991
It may be caused by using wrong volumns mapping in docker compose file, please strictly follow https://rustdesk.com/docs/en/self-host/rustdesk-server-pro/installscript/docker/#docker-compose, or you changed `hbbs` key but forgot to sync to `hbbr` (and restart), or some other reasons.
> We have seen two cases having this `hbbr` key issue while upgading RustDesk server.
- If your cloud has problem with `21117` connection.
- If your cloud instance has problem with `21117` connection.
An user reported this, the `hbbr` logs below show the relay succeeded but close (It is FIN close, not RST) quickly. This indicated the connection closure likely occurred mid-stream between the server and client, leading us to suspect a cloud provider issue. The problem was indeed resolved after the user migrated to a different cloud service.
An user reported this, the `hbbr` logs below show the relay succeeded but close (It is FIN close, not RST) quickly. This indicated the connection closure likely occurred mid-stream between the server and client, leading us to suspect a cloud provider issue. The problem was indeed resolved after the user migrated to a new cloud instance.
```
[2025-06-06 05:59:42.978845 +00:00] INFO [src/relay_server.rs:475] New relay request 6b07fbd4-4f29-4721-807b-7c8bd1f6fb02 from [::ffff:114.5.43.33:49925