Roon Server fails to start after update on NAS (ref#EJUW7H)

Support
1

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· Hi, after being asked to update my Roon software I clicked "update all". Roon was updated but Roon never came back. Roon server runs on a NAS server and Roon clients on my notebooks. Having Roon updated more than 100 times in the past years never had a problem.

Only this time something is wrong. When I start Roon server on my NAS it stops again right after start. No chance to keep it running. I have restarted the NAS, have updated the NAS system software but no change.

Now I wanted to uninstall it and install it new from scratch. But I cannot find the Roon download on Roon website. Maybe because I have life long subscription. How to get access to Roon installer?

Or is there anything else I can do?

Tim
*Removed personall information*

Tell us about your home network

· doesn't matter, Roon is not starting at all on my NAS

2

The Roon Server package no longer works, please switch to the official Docker image to run Roon Server on your NAS. See also:

3

Hello @timboeger

Thank you for reaching out. We understand that your Roon Server on Synology is failing to start following the recent update.

This is happening because the latest update introduced new minimum system requirements. The native Synology operating system (DSM) relies on older software libraries that Roon can no longer support, which causes the standard Roon Server package to stop or crash shortly after launching.

To get your Roon Server back up and running smoothly, you will need to transition to our new, official Docker-based installation. Docker allows Roon to run in an isolated environment with all the up-to-date libraries it needs, ensuring better stability and performance on your NAS.

Here is our comprehensive, step-by-step guide to help you migrate: Installing RoonServer on Synology with Docker

A critical tip for migrating your existing library: You do not have to start from scratch! You can safely restore your previous database. However, to prevent your listening history and edits from being lost or duplicated, you must disable your watched storage folders in your current Roon setup before you create your final backup.

Please carefully read the “Migrating from an Existing Installation” section at the bottom of the guide before you begin.

Take a look at the guide, and let us know if you have any questions or run into any trouble during the Docker setup! We are here to help.

4

Thanks for the instruction. Looks a little tricky, or looks that it could go wrong if not following the instructions carefully. But I will do my best.

5

My dear friends this installation process is a nightmare. I am NOT a IT system’s specialist. I have never heard of Docker before. In your instruction you recommend names for files, paths. For example you write “create docker/RoonOnDocker/Roon”. In your docker.yaml the default for the volumes is “/share/Container/roon”. As said, I am not a specialist in IT systems. Please write in your YAML the same path names you use in your instruction! So: “/share/docker/RoonOnDocker/Roon”. Hard enough to find out that “share” means root (in my case it was volume1).

But when I now start my Roon client (2 hours later, what a great experience…) it said “waiting for roon”. Then the Roon server is found, Ready-Light is green. Clicking “Connect” starts a new search which never ends.

What’s the problem?

6

Then I closed my computer and 2 hours later, after having a brake I changed to another computer, started roon and I could press the connect button. Unfortunately I failed to click the unauthorize button (After 4 hours I forgot this item in your instructions) and was told that I am allowed to have only one Roon server. Ok, I agree,

But from now on the screen behind the connection button stays blank and the option to unauthorize was just not coming back. Then I stopped and restarted the Roon server. This time it worked, I could restore my backup. But after the required relaunch I only saw “Waiting for your Roon Server”

Restart the client again. Ok, then I could sign in and could select my old music folder: I have only one physical folder on my NAS containing the music (3,600 files). I have chosen this folder in Roon. Roon imported 4,400 files (!?). All tracks were found and can be played. But in my playlists (~115 files or so) cannot find a single song from the NAS. All songs are “unavailable”. Only my Tidal tracks are found and can be played. To clarify: I exactly followed your back-up instructions. That part worked as described. But how to fill my playlists with music? The covers are there, the titles are there, just the music is not playing.

But there is another music folder in the Storage area of Roon. It says that this folder has moved. I opened this folder too and chose again my physical music folder from the NAS. Roon again imported 4,400 files and now shows in the Tracks screen: 5,500 tracks.:slight_smile:

But now all my playlists are having their music back again. No, not all, now all the Tidal tracks are unavailable. What is wrong with my Tidal connection? Roon says in the Service area my Tidal account is “signed in”. Why cannot I use Tidal? I am sorry, this is extremely poor. It might be that I have done a lot of mistakes. But to set up a process which is so easy to fail with is poor. Or am I the only one who is using a NAS server? Maybe I am just not using the things as they are designed.

Anyway, if you are going to ask “how was your experience with our update process?”, the answer is, 4 hours hazzle, not finished yet, zero of five stars!!

The Tidal issue I couldn’t resolve up to now. What to do?

7

Ok, one night later, Tidal too can be played.

Ticket is solved. But that was not easy… Thanks anyway

8

Hello @timboeger,

Thank you for the follow-up. I understand that migrating to Docker took more time than a standard update, especially when it is a completely new environment for you. While the process mostly involves carefully reading the steps and copy-pasting the configuration, we definitely hear your feedback regarding the folder naming in the instructions.

I also want to explain exactly why this transition was necessary. As Roon continues to evolve with new features, better security, and overall performance improvements, the software requires modern, up-to-date underlying libraries. Older native NAS operating systems simply do not have these required components anymore. Moving to a Docker-based setup was a forced but necessary measure—it is the only way we can keep Roon running reliably on your NAS hardware without holding back the development of the product itself.

I am glad your local library, playlists, and Tidal are all fully up and playing now. I will go ahead and close this ticket as requested. Enjoy the music!

9

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.