Roon Remote can't connect to server after update on Mac Ventura and OSX 26.3.1 (ref#YTS267)

[Digigina (Regina Weißkopf)]

Is Roon Server running?

· Yes, Roon Server is turned on and running.

What do you see on your screen?

· "Waiting for your Roon Server"

What happens if you press the "Select a different Roon Server" button?

· I see my Roon Server, but I still can't connect.

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

· None of the above

Describe the issue

After getting an update a few days ago, nor my Roon Remote on Mac Ventura neither on OSX 26.3.1 can connect to my roon server on QNAP NAS
After that I exchanged the nativ installation by the Docker version and got 2.65 (build 1653) production
But nothing changed, my roon server is displayed but a connection is not possible.

Describe your network setup

It's all ethernet, iPhone goes over a WiFi router

[benjamin]

Hey @Digigina,

Thanks for writing in and for sharing your report! As a first step, let’s see if completely clearing out your old Roon Remote database, followed by a reinstall, helps:

On the mac:

• Exit out of Roon
• Navigate to your Roon Database Location
• Find the folder that says “Roon”
• Rename the “Roon” folder to “Roon_old”
• Reinstall the Roon App from our Downloads Page to generate a new Roon folder
• Verify if the issue persists on a fresh database before restoring the backup

Thank you!

[Digigina (Regina Weißkopf)]

Hi Benjamin
I guess you mean roon server if you write roon.
I installed roon server in a docker container after the native app in QNAP doesn’t work after updating.
Here is the setting of the docker container:

services:
server:
image: Package roonserver · GitHub
container_name: roonserver
network_mode: host
environment:
- ROON_INSTALL_BRANCH=production
- TZ=Europe/Berlin
volumes:
- /share/RoonDB:/Roon:rw
- /share/Audio/Classic:/Audio/Classic:ro
- /share/Audio/POP:/Audio/POP:ro
- /share/Container/roon-backups:/RoonBackups:rw
restart: unless-stopped
logging:
driver: local

Does reinstall mean to remove the docker application and install it twice?

Or is it sufficient to restart the docker app after renaming the roon database folder?

BTW is there a way to stick on an old version of roon server?
I was fully satisfied with my roon environment before I started the update

Cheers
Regina

[Digigina (Regina Weißkopf)]

Hi Benjamin,
I followed your instructions now and renamed the RoonOnNAS Folder.
After that I could connect to my server, but the old database get lost.
Thats at first fine because I can listen to my music again.
Thanks a lot for your help

Is there a way to reactivate the old DB with all my playlists?

[vadim]

Hello @Digigina,

To answer your question: yes, you can absolutely get your playlists back! In fact, setting up your Docker container with a brand-new database folder—and deliberately not using the old native app’s path (like the RoonOnNAS folder)—is exactly what we recommend. Trying to connect Docker directly to the old native app folder often causes severe file permission errors.

To get your database and playlists loaded into your new Docker setup, we just need to restore from your backups. Here is the exact process:

1. Stop the Native App: Ensure the old native Roon application is completely stopped (or uninstalled) in the QNAP App Center so it doesn’t run in the background and interfere with your Docker container.
2. Connect to the New Server: Open the Roon Remote app on your device
3. Restore from Backup: On the “Choose your Roon Server” screen, you should see your new Docker server listed. Select it, and instead of logging in fresh, click the Restore a Backup link. (Note: If you prefer, you can also log in and go to Settings > Backups > Find Backups).
4. Select the Backup: Browse to the /RoonBackups folder. Because you successfully mapped - /share/Container/roon-backups:/RoonBackups:rw in your yaml configuration, Roon will be able to look inside that folder on your QNAP and find your previous backups. Select the most recent one.

Once the restore process finishes, your server will restart, and all your playlists, play history, and settings will be exactly as you left them.

Regarding your question about sticking to an older version: Roon requires the Server and all Remote devices (phones, tablets, PCs) to be running the exact same version to communicate properly. Because app stores automatically update mobile apps, keeping the server on an older version would break its ability to connect to your remotes. For this reason, downgrading is not supported.

Please let us know how the restore process goes!