QNAP Roon Server "Stopped" Status - Unable to Connect (ref#47H96Y)

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

· My Roon server is on a QNAP drive. It was working until yesterday when I could not connect. The iphone/Macbook Roon app message was "Waiting for your server...." On the QNAP Roon server window, it showed status: "Stopped" in red. The adapter status showed "connected". I stopped, restarted, removed, re-installed, updated the QNAP Roon app (still 2023-03-07)without success. I rebooted the NAS. I refreshed the browser. I tried a new data location/folder with no success. I can send pics. I await your guidance. Thanks

Tell us about your home network

· Verizon Fios Router with Ethernet cable to TP-Link TL-SG105S 2.5G switch with cable to QNAP. This setup working for weeks. I didn't anything. The QNAP front panel lights show appropriate colors and and lights so connected.

Hello @MARK_SWIDLER and welcome to the forum.-

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

Hello Blackjack, Thank you and much appreciated. Looks daunting. I’ll give it a college try. Mark

Hello @MARK_SWIDLER , and welcome to the Roon community!

Thank you for reaching out, and a big thanks to BlackJack for pointing you in the right direction. We completely understand that moving from a simple app package to a Docker installation can look a bit daunting at first glance!

To give you a little context on why this happened: the recent Roon update introduced new minimum system requirements. Because the native QNAP operating system relies on older software libraries, it can no longer run the standard Roon Server package (which is why it suddenly shows as “Stopped”). Transitioning to Docker allows Roon to run in an isolated environment with all the modern tools it needs, which actually results in much better stability and performance for your NAS moving forward.

Take it one step at a time using our official guide here: Installing RoonServer on QNAP with Docker

Here is a crucial tip for your migration: You do not have to start from scratch! Before you begin, just make sure you know where your previous Roon backups are located on your QNAP. Once you get the new Docker container up and running, simply look for the “Restore from backup” link on the initial Roon login screen. This will bring back all your playlists, history, and settings exactly as they were before the server stopped.

If you get stuck on any step—especially the folder mapping part in Container Station—please don’t hesitate to reply here with a screenshot or a question. We are more than happy to help walk you through it!

Thank you. At first try, it too complicated for a non-software savvy person. I tried to go back to a Macbook Roon server setup used in the past without success. I removed the QNAP Roon app and updated the Mac Roon app but the Roon speaker icon keeps spinning. How to I get everything to start from scratch and just use my Mac. Thanks

I tried as best I could and the above is what I was able to put together. How does it look? Will it work? I then opened iphone Roon and clicked on QNAP NAS Roon server. Unable to connect. The Roon icon is still spinning. What should I do? Is the fact that NAS Roon system has stopped have anything to do with being unable to connect? Thanks

Running a server software as Roon (or similar) does require some tinkering and messing about every now and then.

Setting up docker is not as complicated as it looks at first. The guides are quite good and there are many people on the forum that can help, in addition to Roon support.

For a 100% tinker free solution I would suggest a streamer and a streaming subscription like Tidal/Qobuz.

Hey @MARK_SWIDLER,

Thanks for your patience so far! Based on your account admin information, it looks like you’re currently running both Roon Server and Roon on your MacBook Pro - are you still having any issues getting that setup?

We’re here to assist in any way we can. Let us know how things are going and where you may need help. :folded_hands:

For @barrybutler / @John_Berry, please create your own support ticket if you haven’t yet, you can access our Technical Support typeform below:

Here is the container setup on QNAP TS 264T. Do it look OK? If not what should I do? Still no luck getting QNAP Roon Server to work. When I try, I do switch off from MacBook server to QNAP so only using one Roon server at a time. In the QNAP Roon app, I click on upload new Roon program, a check mark appears but Roon continues to be stopped. Is there someone I can talk with who can guide me in real time? Please advise. Thanks

Hello @MARK_SWIDLER

Thank you for the screenshots. This shows that your Docker container (app-1) is successfully Running. This is now your actual Roon Server!

  1. Completely Stop the Native App: Go to your QNAP App Center (not the Roon window), find the Roon Server icon, and ensure it is Stopped. It is vital that the old app is fully deactivated so it doesn’t conflict with the new Docker version. Please confirm here once you have stopped it in the App Center.
  2. Connect via Roon Remote: Open the Roon app on your iPhone or PC. Click Disconnect and “Select a different Roon Server.” You should see the new Docker instance of your NAS ready to connect.

A note on real-time support: While we don’t offer real-time voice guidance, we are monitoring this thread closely to guide you through every step.

Standing by for your confirmation that the native app is stopped in the App Center!

Hi @MARK_SWIDLER,

We see two Roon Server instances are now associated with your account and recently active (a Mac and the QNAP container).

Have you decided to migrate to another server, or are you currently in the process of switching between machines? We want to make sure you didn’t abandon the QNAP; we’re here to support.

I am still trying to use my Qnap NAS as my server

I started another ticket, Ref#T8UKED because I didn’t get any responses for 7 days and I’m getting very frustrated.

Disregard. I thought that response was for me. Sorry.

However, I am still waiting for a response for my issue that’s been going on now for 15 days.

Hi Vadim, Thank you for your reply. I am still trying to make the QNAP work as before. I followed your instructions. I stopped the Roon App on QNAP. I went to Roon app on my MAC and clicked disconnect.What came up was image below. I clicked on the NAS choice. The Roon pinwheel appeared and is still spinning. Please advise. Thanks

Hi Connor, Thank you for your reply. I am still trying to get my QNAP working again with Roon. I followed Vadim’s instruction. Not there yet. See my reply. Unable to connect to QNAP after stopping QNAP Roon app and logging out of remote Roon.Any advice on what to do next is greatly appreciated. Thx.

Hello @MARK_SWIDLER,

Thank you for sticking with this process and providing those updates!

Seeing the QNAP-RoonServer listed in that window is actually a good sign—it means your Roon Remote (your Mac) can “see” the new Docker container broadcasting on the network. The spinning pinwheel, however, indicates it is hanging when trying to establish the actual connection.

This usually happens due to one of two things: either the database path inside the container is misconfigured, or the container is struggling to adopt a restored database backup.

Let’s troubleshoot this by checking a few specific details:

  1. Did you restore a backup? When you first set up the container, did you attempt to restore your old Roon database backup, or is this a completely fresh, empty database?
  2. Restart the Container: Sometimes a new container needs a “kick” to fully initialize its networking. Please go into your QNAP Container Station, find the app-1 container, stop it, wait 30 seconds, and start it again. Then, try connecting from your Mac once more.
  3. Share your YAML configuration: If the pinwheel continues spinning after a restart, we need to look at exactly how the container was built. Please share a screenshot or copy/paste the text of the YAML configuration code you used to deploy the container (specifically looking at how your volumes are mapped).

Let us know what happens after the restart and we will go from there!

Thank you for your reply, Vadim. Please forgive my very limited skills in this domain

  1. Did you restore a backup? I dont remember doing it from scratch. Somehow, app-1 happened by chance. I was working on navidrome-1 as per prior instructions. The image below is what shows when I click on the app-1 in the container station. Does that help tell you anything?The image below is from my File 5 Station:

When I click on container-store data, I get:

When I click on roon, it takes me to roon server and following folders. below. ( at end of message. The roon-backup folder is empty.

For # 2, I stopped the app-1 for 30 sec as directed. I was able to connect to Roon on my Iphone. I tried to connect using QNAP and the following window came up. Please advise on what I should do next.

For #3 I do not know what YAML is and where I am supposed to find it. I await your instructions. Thanks

Hey @MARK_SWIDLER,

Thanks for the follow-up and screenshots! Great progress, the fact that you were able to connect on your iPhone after restarting app-1 means your Docker container is working correctly. That’s the key milestone!

What you’re seeing now (the Roon setup screen on your iPhone) is Roon asking whether you want to set up fresh or restore from a backup. Since your roon-backups folder is empty, you’ll need to start fresh (unless you have a saved backup available elsewhere). Your library will need to be re-scanned but your music files are safe.

For the YAML question: To find it, open Container Station on your QNAP, click on app-1, and look for a tab called “YAML” or “Edit” or “Configuration.” Take a screenshot of whatever you see there and post it.

You’re very close, the hard part is done! :folded_hands:

Hi @MARK_SWIDLER,

Diagnostics show that the docker might have pinged our servers a few times since you lasted posted. Were you able to locate and restore the proper Backup, or set up a new library? Please share a screenshot if you’re stuck.