rustdesk / rustdesk/rustdesk-server-pro
"allow-hostname-as-id" is not persistent
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 317
- Forks
- 119
- PR merge metrics
- No merged PRs in 30d
Description
We use
allow-hostname-as-id=Y
for our Kubuntu clients, but unfortunately as soon as the employee works from home, we have two entries in our RustDesk Pro Console, the old hostname entry and a new default numeric entries:
This shouldn't be the case. The ID should always be the hostname, regardless of the connection.
Server Version: 1.6.3
Custom Client Version: 1.4.1
Custom Client Configuration:
show-remote-cursor=Y
preset-address-book-name=Kubuntu
theme=dark
enable-lan-discovery=N
approve-mode=password-click
hide-tray=Y
direct-server=Y
allow-hostname-as-id=Y
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the duplicate-entry behavior with allow-hostname-as-id=Y while switching between the stated Kubuntu connection contexts, using Server Version 1.6.3 and Custom Client Version 1.4.1. Compare the RustDesk Pro Console entries before and after the connection changes; done means the hostname remains the sole ID instead of creating a numeric entry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, shell
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100