mirror of
https://github.com/rustdesk/rustdesk.git
synced 2026-03-02 19:26:56 -05:00
Could not connect to my server - problems with ethernet drivers or what? #1653
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-rustdesk#1653
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 @albgen on GitHub (Apr 13, 2023).
Bug Description
Simply could not connect to my server deployed with docker compose.
How to Reproduce
Windows Server running on Proxmox.
Rustdesk server running on another virtual infrastructure elsewhere. Docker compose file as follows
docker compose.txt
On Proxmox, set the network card of Windows Server as e1000 model, result is everything working correct.
On Proxmox, Set the network card of Windows Server as VirtIO model, result is "Could not connect".
Please note that, internet connectivity is working normally and also other services are working normally in both cases. Only Rustdesk has the issue.
See screenshot for the logs of the hbbs server which shows several attempts with tcp closed.
It shows also a successfull attempt when the network card was set to e1000
Expected Behavior
Connect on server as usual.
Operating system(s) on local side and remote side
Windows Server 2019, Windows Server 2012
RustDesk Version(s) on local side and remote side
1.1.9 but also 1.2.0 the same issue
Screenshots
What you see on the following, are different attempts to connect on the server and the one that worked

Settings of proxmox on network card

Additional Context
No response
@rustdesk commented on GitHub (Apr 13, 2023):
#763