Unable to connect to Roon Server on QNAP NAS after moving to Container (ref#306JOT)

[Roger_Morrow]

Is Roon Server running?

· Yes, Roon Server is turned on and running.

What do you see on your screen?

· I see something else

When you try to connect, what screen do you see?

· Just the Roon logo

Please try to restart your network setup by unplugging, waiting 30 seconds and then replugging in your networking gear.

· No, the issue remains the same

Please select how you've connected your Roon Server to the internet

· Roon Server is connected by *Ethernet*

Have you checked your firewall settings to ensure that Roon is allowed through?

· Roon still won't connect even after checking this aspect

Have you verified that Roon Server is on the same subnet as your Remotes?

· My Remotes and Server are on the same subnet and I still can't connect

Sometimes the issues can be resolved with a reinstall of your Roon Remote app. Let's try to perform a reinstall and see if it helps.

· I've reinstalled the Roon Remote but it did not help

What is the operating system of your Roon Server host machine?

· Roon on a *NAS* (Synology, QNAP, ASUSTOR)

Select any of the following components that are present in your local network setup

· *Mesh networks*

You mentioned a mesh network in your setup. Certain common mesh networks might require slight reconfiguration to support Roon.

· None of the above

Describe the issue

Can't connect to Roon Server after upgrading to host via containers on QNAP NAS

Was surprised to find Roon not working after returning from a trip and found that the server on my QNAP NAS wasn’t running. Some Googling quickly identified that the native Roon app was no more and that I needed to move it to a Container. Amazed that the first I heard about this was after my system had stopped working.

So I followed the instructions to move the Server to a Container and now have Roon Server 2.65 (build 1653) running on my TS-251+ through Container Station. I found the instructions really easy to follow and the web page to generate the yaml was great.

When I try to connect any of my Roon clients, they see the Roon Server instance (which is on the same network), but then never successfully connect. All I get is the Roon animated icon, suggesting something is stuck.

I haven’t yet got to the point of restoring the old database yet and thinking that the upgraded server might have been busy re-indexing my music library left it running overnight. However, behavioural today is unchanged and I am still unable to connect.

Server logs aren’t very informative. Welcome any ideas on what to try next?

Describe your network setup

NAS connected via LAN to MESH WiFi network. Nothing has changed other than the recent upgrade of Roon Server

[Roger_Morrow]

This ticket can be closed. After restarting the container running the ServerI was able to chose to deactivate the existing instance (which I now assume must have been the replaced native version) and log in successfully. It would be useful to note that this step is required in the otherwise useful instructions on migrating to Container Station.

[vadim]

Hello @Roger_Morrow

It is good to hear your system is back online. Dealing with an unexpected server migration right after returning from a trip is certainly an unwelcome surprise, and we understand the frustration that caused.

Your feedback about the deauthorization step is spot on. Because the Docker container generates a new Machine ID, the Roon system treats it as a completely new Core, which requires releasing the license from the legacy installation. I will pass your suggestion directly to our documentation team to ensure this step is explicitly added to the migration guide.

Before we officially close this ticket, could you clarify two quick details for our records?

• Did you map the Docker container to use the exact same database folders as your previous native installation?
• What is the current status of the native Roon Server app in your QNAP App Center (e.g., is it still installed but stopped, or have you completely uninstalled it)?

Thank you again for your time and feedback!

[Roger_Morrow]

Vadim, thanks for the reply. In response to your questions, I have removed the native installation and configured the new installation with a new set of database folders, restoring the most recent backup once I got the system working again.