Unable to access Roon server on NAS after update (ref#S5IS5I)

Support
1

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

Since the last Roon update I cannot access my roon server on my Nas. I tried everything I can do but no success. So I want to create a new server on an SSD but roon is blocked on the symbol searching...

Describe your network setup

I want to create a new server on an SSD (and no more on the NAS)

2

Hi @JF_Basin,

Thanks for writing in, and sorry for the disruption.

What you’re experiencing is directly related to a change in Roon’s minimum system requirements that took effect with the latest release (build 1653). Roon now requires glibc 2.27 or later and OpenSSL 1.1.1 on Linux. From what we see in diagnostic servers, your operating system runs an older Linux kernel that falls below that threshold. This is why both the existing NAS server stopped working after the update, and why a fresh install on the SSD is getting stuck.

Roon has released an official Docker image specifically to address this situation. Your Synology very likely meets the hardware requirements. Docker runs a containerized environment on top of your existing DSM, bypassing the kernel/glibc limitation entirely.

Roon has a dedicated guide for migrating from your existing native installation to Docker here:

Installing RoonServer on Synology with Docker – Migrating from a Native Installation

One critical step before you begin: before creating your final backup, you must disable all watched storage folders in Settings → Storage. If you skip this, Roon will treat all your files as new after the migration and you’ll lose your listening history and edits. The guide covers this in detail.

For further context on why this change happened and what systems are affected, see the announcement: [UPDATED] Roon Minimum System Requirements Are Changing

Let us know if you hit any snags during the migration and we’ll help you through it.

3

Hi Connor,

1/ As I see in the announcement: [UPDATED] Roon Minimum System Requirements Are Changing, how an I stay on an older Roon version ?

2/ Or if I want to change my Roon server (no more on NAS) but on a SSD, how can I do it ? because It try to connect and remains stuck on the Roon symbol (see yesterday print screen)

Thanks for your reply

4

Hey @JF_Basin,

For Mac users who are not yet able to update to macOS 12 or later, we’re also making a pre-update installer available as a temporary option. This version will not receive future updates or security fixes, and may become incompatible with current Roon Remote or ARC versions over time. You can find and download the installer here.

This is a bit more of a process, but I’ll share the steps with you below:

  1. Create a Fresh Backup

Before touching anything else, you need a snapshot of your current database (playlists, history, edits).

  • Open the Roon app on your phone or computer.
  • Go to Settings > Backups.
  • Click Backup Now. Save this to a location accessible by both devices, such as a USB thumb drive or a shared folder on your network.
2. Prepare the New SSD Server

Depending on what your “SSD device” is, you need to install the Roon Server software:

  • If using a NUC (DIY): I highly recommend installing ROCK (Roon Optimized Core Kit). It is a custom, lightweight operating system designed solely for Roon.
  • If using a Mac/PC: Download and install Roon Server (not just the Roon app) from the Roon website.
3. Migration (The "Switch")

Once the new software is installed on your SSD-based machine:

  1. Shut down the Roon server on your NAS to avoid any database conflicts.
  2. Open the Roon app on your remote (phone/tablet) and it should ask you to "Choose your Roon Server."
  3. Select the new server (the one on the SSD).
  4. Crucial Step: When it asks you to log in, do not log in yet. Instead, look for a small link at the bottom that says "Restore a Backup."
  5. Navigate to the backup you created in Step 1 and let it restore.

4. Re-mapping Music Files

Since your music was on the NAS, you need to tell the new server where to find it:
  • Go to Settings > Storage.
  • If your music files are still on the NAS, you will need to "Add Folder" and enter the network path (e.g., \\NAS-NAME\Music).
  • If you moved the music files onto the SSD itself, simply point Roon to that local folder.

Some important tips for this:

Authorizing: During the setup, Roon will tell you that your license is already in use by the NAS. Simply click “Unauthorize” for the old NAS; your license will immediately transfer to the new SSD server.

Database vs. Music: You don’t have to put your actual music files on the SSD. As long as the Roon Database (the app’s brain) is on the SSD, you will get the performance boost even if the music files stay on the NAS’s mechanical hard drives.

Networking: Ensure your new SSD server is connected via Ethernet rather than Wi-Fi for the most stable experience.

I hope this helps! :folded_hands:

5

We’re going to close this thread due to inactivity, but you can reach out here to reactivate it if you require additional assistance. Thank you!