Roon stopped on QNAP; unable to connect streamer (ref#T8UKED)

[John_Berry]

Is Roon Server running?

· No, Roon Server is not running.

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

Qnap shows Roon as "stopped". I tried to complete the Docker Container Station fix but still no go. I have all the other threads and performed as much as I could. Now my streamer won't connect either.

Describe your network setup

Qnap Nas, Linn DSM streamer Dac

[John_Berry]

[John_Berry]

[BlackJack]

I don’t see how your streamer suddenly fits into the picture. Can you please elaborate some more about your current issue.

[John_Berry]

Well, before the “Container Station” fix attempt. I was at least able to connect my streamer to the internet and play music using the Tunein app via Linn server. Now it won’t even connect and find my streamer.

[BlackJack]

Maybe try and restart all involved components, including your network components and your streamer. Roon does not have anything to do with your Linn software so maybe click on “Contact Linn” there if you still can’t use it afterwards.

[John_Berry]

I tried that. Turned Off and Unplugged for 5 minutes the restarted. No go.

Do my screen shots look like I completed the Container Station fix correctly?

[BlackJack]

The Docker Application roon1 is status green, running. So we have to assume that a Roon Server instance is running inside. Roon Support may be able to provide further troubleshooting help if needed, their office days are Monday to Friday and there is currently a lot on their plate.

[John_Berry]

OK, thank you.

[vadim]

Hello @John_Berry

Thank you for reaching Roon support.

To resolve the connection issue between your QNAP and your streamer, please follow these steps:

• Confirm Remote Connectivity: Are you able to see and connect to the new Roon Server instance from your phone or another Roon Remote device?
• Disable the Deprecated App: Go to the QNAP App Center and manually Stop or Disable the old, native Roon Server application. Leaving both running simultaneously can cause network conflicts and prevent your streamer from identifying the correct core.
• Manual Server Selection: If your Roon Remote app is hanging, click the Select a different Roon Server button. Choose the new Docker instance (status “running” in your screenshots) and log in.
• Streamer Conflict: If your Linn streamer still cannot be found, it is likely still “cached” or looking for the old native application’s unique ID. Restarting your networking gear and the Linn DSM again after disabling the old app should force it to see the new Docker instance.

Provide an update on whether your phone can connect to the new server once the old app is fully disabled.

[John_Berry]

1. No, I get same screen from iPad and iPhone. “Looking for Rood server” and are you new to Roon.

2. I deleted the old Roon application on the Qnap in the app section.

3. I tried the “ned help finding the Roon server” then input the up address for my NAS 192.168.40.110 but then it just goes back to the “ looking for your Roon server and Are you new to Roon?” screen.

4. I unplugged the Linn steamer for 5 minutes then back in and powered up. Still can’t connect to the server.

   Ugh, sorry to be a problem. So frustrated.

   Thanks for helping.

[John_Berry]

Ok, one more unplug and replug and the Linn in now connected to the internet.

However still can’t find the Roon server.

[vadim]

Hello @John_Berry,

Thank you for the updates. If your devices are still unable to see the new server, let’s try a few deeper troubleshooting steps to clear out any lingering network or cache conflicts.

Please try the following:

1. Restart the Container (Refresh Network Stack) Sometimes the Docker network stack needs a bit of a nudge to start broadcasting correctly on your local network. Open QNAP Container Station, manually stop the Roon container, wait about 10 seconds, and start it again. Doing this a couple of times can often force the network discovery to trigger properly.

2. Clean Reinstall of the Roon Remote App To completely rule out your iPhone or iPad trying to cling to the old, cached server ID, please completely delete the Roon app from your iOS device. Once deleted, download a fresh copy from the App Store and see if it can discover the new Docker core.

3. Verify your YAML Configuration Network discovery heavily relies on the container being configured correctly. Could you please confirm if the YAML code you used during the setup exactly matches the structure shown in the screenshot above?

It is absolutely critical that the line network_mode: host is included and formatted correctly. Without this specific setting, the Docker container remains isolated, and neither your Linn streamer nor your mobile devices will be able to find Roon.

Let us know how the fresh app install and container restarts go!

[John_Berry]

1. Done. Stopped and started twice.

2. Done. New download of Roon App still says “stopped Status”

3. I deleted the original Roon container and made a fresh one. Still not finding server. Below is my new YAML and what I continue to see when trying to connect to the server.

   
   

[benjamin]

Hey @John_Berry,

Thanks for the update! Looking at your screenshot, the YAML config looks correct — network_mode: host is there, volumes are mapped properly. The container is running but Roon clients still can’t discover it. Here are the next logical troubleshooting steps to try:

1. Check if the container is actually running Roon Server (not just the container)

In QNAP Container Station, click on the running Roon container → go to the Console/Terminal tab and run:

ps aux | grep roon

This confirms whether the Roon Server process is actually alive inside the container, vs. the container shell just being up.

2. Verify the /share/Container/roon folder has correct permissions

   The most common silent failure on QNAP is the /Roon data directory being owned by root (from a previous install), which prevents the container from writing to it. In QNAP’s File Station or via SSH:

   ls -la /share/Container/roon

   If it’s owned by root and not writable, the server silently fails to start. Fix with:

   chmod -R 777 /share/Container/roon

   Then restart the container.

3. Confirm the QNAP firewall isn't blocking discovery

   Go to QNAP Control Panel → Security → Firewall and temporarily disable it, then try connecting. Roon uses MDNS/mDNS for discovery which can be blocked by QNAP’s built-in firewall.

Let me know if any of the above help!

[John_Berry]

1. 1. I cannot find this tab, “go to the Console/Terminal tab”
2. I cannot find “/share/container/roon” folder in file station.
3. 3. I went to Control Panel - Security - There is nothing in all the tabs referring to “Firewall”.

I’m striking out here big time.

Is it possible to screen share and take over my computer and have a look see?

[John_Berry]

Where do I find the tabs you are referencing?

[John_Berry]

Is this issue only affecting Qnap NAS units?

[John_Berry]

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

· https://community.roonlabs.com/t/roon-stopped-on-qnap-unable-to-connect-streamer-ref-t8uked/319587

I have an issue with my qnap NAS not finding the server. I haven’t had any posted the above trouble ticket and have not had replies/help from anyone for several days. Still trying to get this fixed. Thanks.

Tell us about your home network

· DZS 1764WZ

[John_Berry]

@support,
Please help. I haven’t had any responses for 7 days.