mirror of
https://github.com/rustdesk/rustdesk.git
synced 2026-03-02 22:57:40 -05:00
Rustdesk is always using relayed connection #1900
Labels
No labels
bug
documentation
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
question
unreproducible
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/rustdesk#1900
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @stevenmccormack on GitHub (Jun 2, 2023).
Bug Description
I am facing an issue similar to https://github.com/rustdesk/rustdesk/issues/4348. After upgrading to version 1.2 I am always getting a relayed connection (also if hosts are on same site).
My setup has 2 sites with client PCs as well as a central datacenter with my self hosted server. All sites are connected via VPN.
After reading issue 4348 I checked RustDesk2.toml and found that on all machines I have the following in
/root/.config/rustdesk/RustDesk2.toml:In 1.19 nat_type was 1. If I manually set nat_type to 1 in the config, it will revert to 2 after restart / connection attempt.
I checked all firewalls involved but could not see any blocked traffic between the clients and the server.
How to Reproduce
I am unsure on how to reproduce
Expected Behavior
Direct connection as with 1.19
Operating system(s) on local side and remote side
local: Debian 12 remote: Debian 12 / Ubuntu 22.04
RustDesk Version(s) on local side and remote side
1.2.0 (2023-05-05 00:26)
Screenshots
Additional Context
No response
@rustdesk commented on GitHub (Jun 2, 2023):
https://github.com/rustdesk/rustdesk/issues/4348#issuecomment-1548176891
github.com/rustdesk/rustdesk@400aa61c6a