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.
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.