· No, Roon Server is not running.
· I can't turn on Roon Server, I need help.
roon on my linux (synology NAS) can not get it on anymore...
roon on my Linux (Synology NAS) can not be turned on again...? so server is not foundable...
Then your server’s OS (DSM) is already older. You can try and update it or, also if you want support because the old apps no longer are (supported), you have to switch to a Docker installation. See also:
AFAIK, you need DSM7.3 or higher in order to run roonOnNAS on Synology natively.
it has always worked fine on DSM 6.x but suddenly i can not execute Roon server … it starts up and then the button goes back to ‘‘execute’’…
That’s exactly the point. You very likely updated the roon Server on your NAS to its latest version. And this version needs DSM 7.3+. It doesn’t work with DSM 6.x anymore.
In case you’re 100% sure that your roon Server has never been updated since then, it’d be something else.
And yes, a roon Server update on a NAS would also be performed in case this update does not support the underlying DSM version, unfortunately.
So, from what you said so far it looks like a recent roon Server update on your NAS bricked your roon environment silently.
Either you are able to update your DSM to 7.3+ or you use a Docker image on your NAS to run roon Server from there. roon does provide such an image. Search for “Docker image”.
is there a simple step by step guide somewhere? i am no it specialist…
I already linked the guide(s) for you. If this is too complicated for you, search in your environment for someone with more skills in NAS administration and Docker app installation to help you out on this.
This is just my advice as a fellow Roon (on NAS) user, you are free to ignore it.
Assuming your NAS model does not support DSM 7.3. Have you already checked?
think i got it turning now…but not fully understand it hahahah
Indeed, then you’d try the Docker image.
Hello @Hans_Buurstede ,
That’s correct, you’ll need to use the Docker install for your setup. Did you manage to get the Docker container working correctly, or are there any issues remaining? If there are any remaining issues, please let us know any details you can and we’ll assist, thanks!
i think i have almost everything set now. Roon is importing my library (75.000 tracks) now. i only have no audio…but that will be a setting…
Hey @Hans_Buurstede,
Great progress, Hans, nice work getting the container up and running! 
The “no audio” part is almost always down to Docker networking. For Roon to see your network audio devices (and for remotes/endpoints to find the server), the container needs to run in host network mode rather than bridge mode. If you followed the guide with network_mode: host, you should be most of the way there. Once the container is on the host network, your zones will show up under Settings → Audio in the Roon app, just enable the ones you want and give them a name.
A couple of things worth checking:
Hey @Hans_Buurstede,
Just checking in on this. Were you able to switch the container over to host networking and then open Settings → Audio to see whether any zones appear? If Settings → Audio is still empty, that usually points back to bridge mode or another Docker networking issue, and networked endpoints are the reliable option here rather than a USB DAC passed through the NAS. Let us know what you see there and how things are behaving once the library import has had more time to finish.
Please note, if we don’t hear back from you this thread may close automatically soon. If the thread auto-closes and you need further assistance, please submit a reopen support request via the technical support help form below and specify that the issue should be reopened. Thank you.
