For Roon connectivity to work properly, both Roon Server and Roon Remote need to be turned on.
· I can't turn on Roon Server, I need help.
Describe the issue
Hello. I look after my Dad's Roon since he passed away, but I struggle with all the technical language. My Mum did an update last weekend, and since then it just gets stuck on "looking for roon server". Dad used QNAP, but I'm not entirely confident on what it is. I looked at the Roon Server through QNAP, and it says the status is "stopped". Version : 2.65 (build 1653) production QPKG-Version : 2023-03-07 ffmpeg : user supplied version. Is anyone able to help please? I'm really worried I will lose Dad's music.
Describe your network setup
I'm sorry - I don't understand a lot of this. I know Dad uses QNAP, and Mum's internet is with BT, but I don't know anything else.
yes , select Stop option from the the right-click menu
Stop option will stop RoonServer (which is actually failing to start after the upgrade to 2.65 anyway) and disable it from even trying to automatically start again in the future; it is up to you if you want to remove it instead, or not; personally I preferred to do that after Roon was running fine in docker-container (just in case I wanted / needed something from the old install)
You are on a good track, I believe this happened to others and is not so hard to overcome IF one knows what has to be done Unfortunately my missing experience with this topic gets in the way now and I have to leave it to others who surely will show up. (It’s the weekend now, so we will have to rely on volunteers until next week)
it should be as simple as click connect and follow the steps - authenticate & deauthorize your old RoonServer instance so that the new one will be active instance (and user of the Roon License)
It worked!! Thank you all so much, I really appreciate the help.
Question - is there any danger in not doing the Roon updates going forward? It often seems to go wrong, and I’m worried that it’ll get to a point beyond my tech knowledge.
Glad you got there, and you did much better than many others
This here was a special case as explained in the private message. Future updates are now isolated from the QNAP operating system, because of the container solution, so this shouldn’t happen again.
You could choose to not install updates, but:
Even if you configure updates to need manual confirmation on the QNAP and on Windows/Mac, it will keep nagging and it’s annoying.
If you use Roon apps on mobile devices (phone, tablet), they will keep updating through the App Store / Play Store. Therefore, over time they will become incompatible if the Roon Server becomes outdated due to missing updates. You would have to stop Roon updates for the mobile devices, and this depends:
On Android, you can deactivate updates for individual apps in the Play Store, so this is an option.
On iOS, there is no such option. You could only disable App Store updates for all apps, and this is probably not what you want.
I am absolutely thrilled to read that you got the system back up and running! It is wonderful that you are keeping your Dad’s music alive for your Mum, and I know stepping into a complex technical setup like this can feel incredibly daunting.
As Suedkiez mentioned, this specific update was a unique hurdle. Now that you have Roon safely isolated inside its new container, future updates should be significantly smoother and much less stressful!
Since everything is working beautifully now, I will go ahead and officially close this thread. Please never hesitate to reach out if you hit another technical roadblock in the future.
Unfortunately my missing experience with this topic gets in the way now and I have to leave it to others who surely will show up. (It’s the weekend now, so we will have to rely on volunteers until next week)