rustdesk / rustdesk/rustdesk-server

UDP failure: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (OS error 10014), client cannot connect remotely.

Open
#539 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Rust
Stars
10.4k
Forks
2.6k
PR merge metrics
No merged PRs in 30d

Description

The server-side system is win server 2012, the software is 1.14 (it was 1.12), the id_ed25519 is configured, and rustdesk-utils.toml is configured (the content is [options] relay-server = "192.168.0.111:21116"), and there are two months in the period set to ([options] relay-server = " xxx.com:21116"), under such a configuration, it has been used normally for two months, and now after the domain name expires, when the domain name is changed and reconfigured, it is found that the client cannot connect to the server, at this time, the server can be pinged, and SMB access can be normal, but the client prompts, "the remote computer is offline", and the client is now 1.3.9, which was originally 1.3.7. The server now always prompts "ERROR [src\rendezvous_server.rs:255] udp failure: The system has detected an invalid pointer address when trying to use a pointer parameter in a call. (os error 10014)", but I'm using netstat -ano| The findstr "21116" test is normal, how can I solve it?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the UDP error reported at src\rendezvous_server.rs:255 and review how the rendezvous server handles UDP on Windows Server 2012. Reproduce the failure using the reported relay-server configuration and port 21116, comparing the changed domain setup with the working state. Done means identifying the cause of OS error 10014 and confirming that remote clients can connect again.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
backend, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.