rustdesk / rustdesk/rustdesk-server-pro
Upgrade from OSS to Pro and adding non-priveleged user causes HBBR service to not start due to HBBS & HBBR still running on previous account
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 317
- Forks
- 119
- PR merge metrics
- No merged PRs in 30d
Description
Bug Description
When first installing OSS I wasn't prompted with the "this can run as a non priveleged user".
When upgrading to pro by running the script provided, the HBBR service didnt start.
When first installing OS version I ran it as admin1.
I ran the upgrade script as root due to an error with using "sudo bash" as admin1.
I used svc_user1 as the non-priveleged user.
After trying to uninstall, reinstall and so on I found out that a HBBR service still ran on the active ports 21115:21119 - i killed the HBBR process and it started instantly.
How to Reproduce
- Install OS version as admin1
- Upgrade from OS as root
- Try starting HBBR service
Expected Behavior
systemctl status rustdesk-hbbr.service
This will exit with error code.
Operating system(s) on local side and remote side
Ubuntu 24.04.1 LTS (non-docker)
RustDesk Version(s) on local side and remote side
1.4.5 - only serverside
Screenshots
Additional Context
A restart of the server could've possibly solved it, however I didnt try it as a regular update should run without restarts.
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 with convertfromos.sh and inspect how the upgrade handles the existing HBBS and HBBR services and the selected non-privileged user. Reproduce the Ubuntu 24.04.1 LTS upgrade, check systemctl status rustdesk-hbbr.service, and inspect ports 21115:21119. Done means the upgraded HBBR service starts without an older HBBR process still running on those ports.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100