Roon app on macOS can't connect to Unraid server (ref#DE6GJY)

Is Roon Server running?

· Yes, Roon Server is turned on and running.

What do you see on your screen?

· "Looking for your Roon Server"

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

macOS Tahoe running Roon app. Latest version of both.
Unraid server using docker to run RoonServer
All worked fine, but now it won't connect to the server even when I type the full ip address in using the "help" button under "looking for your Roon Server"

Describe your network setup

All wired 2.5gb

So, simple fix apparently. The Docker container I was using was goosed. I used a different repository and all is working again.

Is there a way to reload my library from a backup, because I just know a lot of my classical collection probably got messed up.

Thanks.

If you created one

Hi @Casa_Paska,

Thanks for the update — glad to hear you were able to get things working again.

Just to set expectations going forward: Docker-based and other containerized Roon Server setups (including unRAID) are not officially supported. While they can work, we’re unfortunately not able to provide troubleshooting assistance if issues arise in that environment.

If you decide to continue using Docker, you’re welcome to do so at your own discretion, but for full support we recommend running Roon Server on a native, supported platform.

Regarding your library: if you have a Roon backup available, you can restore it from Settings → Backups → Restore. This will bring back your library data, edits, and classical metadata as it existed at the time of the backup.

Thanks for your understanding, and feel free to reach out if you move to a supported setup.

No worries. I completely understand why you need to have official products / licences, you need to keep this great company and its product commercially viable.

Personally, I can’t abide by people who open a support thread, figure out the issue and then don’t bother to return to give the solution that might help others in a similar position.
It’s lazy and selfish.

FYI, I never mentioned the docker container I used was

steefdebruijn/docker-roonserver

Thanks again.

1 Like

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.