Duplicate Device Issue
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- backend
Research direction
Start by reproducing the device rebuild flow on RustDesk Server Pro 1.7.7 with allow-hostname-as-id=Y, comparing the offline hostname entry with the online default-ID entry. Trace the device registration and list-handling entry points; done means rebuilding a device does not create a duplicate or inflate the 2500-device limit.
Written by the indexing model from the issue text.
Description
We are maxing out our device limit (2500) due to device being duplicated when they are rebuilt.
Our custom client uses the allow-hostname-as-id=Y setting.
When the device is initially built, an entry is created in the device list with an ID that is a preset/fixed hostname (HOSTNAME1234).
When the device is rebuilt, it goes back into the device list with the default RustDesk ID (1680798129) instead of the hostname.
The hostname remains in the list, but that device entry is offline. The online device is the new entry with the default DustDesk ID (1680798129).
The allow-hostname-as-id=Y setting seems to fail due to the device ID (hostname) already existing.
The hostname is still visible under the device column (username@device_name) but the issue is the duplicated/maxing out the device limit.
We are currently running on RustDesk Server Pro 1.7.7 at the moment.
- Dominant language
- Shell
- Stars
- 322
- Forks
- 120
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from rustdesk/rustdesk-server-pro
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
rustdesk/rustdesk-server-pro#1026 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
rustdesk/rustdesk-server-pro#1023 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
rustdesk/rustdesk-server-pro#1019 · 4 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
rustdesk/rustdesk-server-pro#1017 · 1 comment · 3 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 57/100
rustdesk/rustdesk-server-pro#1015 · 2 comments ·
All issues in rustdesk/rustdesk-server-pro
Similar issues
-
data only (no code) good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
kind/bug needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 88/100
projectbluefin/common#1521 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
upstream-release
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
pypa/advisory-database#401 · 3 comments ·
Maintainers usually reply within 1 day