Roon server instability after update (ref#INFIYD)

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 don't see Roon Server.

Please try to restart your Roon Server by closing the Roon app in the taskbar or rebooting your Roon Server machine.

· No, the issue remains the same

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 *WiFi*

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?

· *MacOS*

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

· None of the above

Describe the issue

Roon server is not stable following update

Describe your network setup

Mac OS 15.4.1 running roon server, remote is iOS

Hello @Reese_Gautschi ,

Thank you for reaching out, and sorry to hear about the trouble after the update.

Could you kindly clarify what you mean by “not stable”?

  • Are you experiencing frequent crashes or restarts of the Roon Server?
  • Does the Remote app fail to connect or disconnect intermittently?
  • Are there issues with playback or device discovery?

Any additional details you can provide would help us isolate the issue more efficiently.

Unstable - The server can’t be reached by Roon remote. No devices are available. Song stops in the middle.

Hello @Reese_Gautschi,

Thank you for the update.

We’ve gone ahead and enabled diagnostics for your account. Based on the logs, everything was running smoothly after the update until your Roon Server—hosted on the iMac—received a new IP address. Initially, the server was operating under 192.168.0.39, but later it changed to 192.168.0.218.

This IP change could be causing discovery or connectivity issues.

Could you please try the following:

  1. Fully close the Roon Server:
  • Right-click the Roon icon in the macOS taskbar (top-right corner) and select Quit.
  • Then relaunch Roon and see if the issue persists.
  1. Check Local Network Access:
  • Navigate to System Settings > Privacy & Security > Local Network.
  • Make sure Roon is listed and has access.
  • If it is already enabled, toggle it off and then back on.
  • Reboot your Mac afterwards and test again.

Let us know how it goes or if the problem continues—we’re here to help.

Did as you suggested, and it now seems to be stable. I missed the toggle on / off suggestion in my first guesses, so I believe that’s what solved it.

Hello @Reese_Gautschi,

Thank you for the update. We are glad to hear that everything is running smoothly. Enjoy your music!

Still unstable. Can you check the logs?

Hello @Reese_Gautschi,

Thank you for the update.

I noticed that your Roon Server is currently connected via Wi-Fi. As outlined in our networking best practices, we strongly recommend using a wired Ethernet connection for the Roon Server to ensure optimal performance and stability.

Your Roon Server should always have a wired connection.

Would you kindly connect your Roon Server directly to the router using an Ethernet cable and let us know if the issue persists afterward?

Hi @Reese_Gautschi,

This thread will shortly auto-close due to a lack of response. The most recent diagnostics to reach our servers suggest that you might have signed into RoonServer in the interim. We hope this indicates the above suggestions were helpful or you’ve otherwise resolved your issue.

If we’re incorrect in this assumption and you find this thread has closed when you attempt to respond, please simply reach out in a new support request and we’ll continue the conversation there.

Thanks!