I'm having a number of problems. I get the message that "Roon has quit unexpectedly" 2 or 3 times a week. Then Roon has trouble finding the core and then Roon can't see my audio devices. There is some thing wrong with my setup but I've gone through nearly everything in "Network Best Practices" and I still can't solve the problem. My system consists of: Mac Mimi M2 core (ethernet connected), a Hegel 190 IA (ethernet connected), a Bluesound Node 2i (ethernet connected), a Gustard R26 (ethernet connected), a Synology DS118 NAS (ethernet connected), a TP-Link AX300 (WiFi 6) Netgear Cm700 Modem, and a Netgear GS305 switch. My remotes are MacBooks, iPads, and iPhone. There is another issue that occurs- my core updates Roon automatically, as selected, but my remotes will not update automatically to the latest Roon software. I try to update the remotes manually, but I often get the notice: "There was an error checking for an update." The result is that my remotes are often out of software sync with the core. I don't know if these issues are related. Searching the community forum has led me to believe that the problem is in how I set up my network. Recently I've noticed that on the settings audio page that my Mac Mini IP address is flickering between two numbers: 192.168.0.252 and .153. Can this be the reason that Roon quits unexpectedly? I've also considered the static and dynamic IP choices as well as the possibility of an IPv6 conflict, all to no avail. (Roon quits while playing live radio as well as NAS files. My library is only about 6000 flac files.) Usually the way I get things working again is by quitting Roon, rebooting my core and then restarting Roon. It has become a chore. There are lots of things I love about Roon and I know many people run it without any problems. What have I screwed up? Thanks Bill
We’ve pulled diagnostic logs from your RoonServer instance and see the server re-trying live radio queries in a continuous loop. In the context of the update failures you’ve mentioned across multiple Roon clients, there’s a possibility the assigned DNS server for this network is failing to resolve addresses properly for Roon’s upstream servers.
I’d enter the settings administration page for the the TP-Link router and make sure that a reliable DNS server is assigned in place of the internet provider defaults. We usually recommend QuadNine (9.9.9.9) or Cloudflare (1.1.1.1).
From there, navigate to the System Settings on your Mac Mini hosting RoonServer. In Privacy & Settings, toggle on Local Network access for Roon; if you’ve already toggled it on, then toggle it off/on again to refresh Roon’s access to the network interface through MacOS. Take this step on any MacOS Roon Remotes as well (MacBooks). On your iOS devices, navigate to WiFi Details and make sure Private WiFi is set to “Fixed.”
Finally, ensure that the Mac Mini is plugged in via ethernet. Disable the WiFi in the network settings - this will prevent the Mac from switching between the two IP addresses it has allocated (one for WiFi, one for ethernet).
Restart RoonServer from the menu bar after taking these steps.
If you continue to have issues, let us know here and we’ll pull updated diagnostics. We’ll watch for your response. Thanks!
Connor:
Thank you for the response. I’ve changed the DNS on the admin. page. My administration page is a bit different than your example. Does this look right?
(see screenshot)
I’ve made the other changes you suggested and ran Roon Live Radio and NAS files for approx. 20 hours without “Roon Quitting Unexpectedly.” However, I still can’t get my remotes to update to the latest Roon software automatically or manually. What can be causing this? Thanks for your time. Bill
Add images
Thanks for the updates and screenshots! I’m glad to hear there’s been progress as well - smooth listening is so crucial!
Regarding your remotes having issues with updates, if you reboot the devices themselves, does that help at all?
If you delete the Roon app from your remotes and reinstall it, does that help? I realize that isn’t a long-term solution here, but I’d be curious to see if that still allows for the latest version of Roon to be installed properly.
It looks like your iPad is running the latest version of Roon, with your Macbook Pro running the previous version of Roon - build 1538. The only severely out-of-date device appears to be your Macbook Air 2018 running build 1368. Redownloading and installing Roon will likely be the best step for your Macbook Air.
Benjamin: After running normally for a few days Roon has begun “To Quit Unexpectedly” again. Yesterday a 6 hr. playlist stopped after about 20 minutes and I could not get it to start again. Hitting the play button did nothing. (Live Radio would not play either.) Finally I had to reboot my M2 core and quit Roon then restart Roon. Back to normal until this morning when Roon quit again. I noticed that when Roon quits it shows my Hegel amp as playing on the settings audio page but there is no sound. Don’t know what that means. (I can’t find anything set to mute.) I also noticed while on the settings page that the IP address (192.168.0.153) for my M2 core flickers every once in a while. No other IPs on the page do that. Seems odd to me. Occasionally when I open Roon I get the message: “Error Loading Saved Page.” Can these problems have to do with more network setup problems? Thank you for your time. Bill
Thanks for the update! We’re seeing similar radio-related errors from a recent diagnostic report.
While your physical network setup sounds totally fine, it may be worth testing out a different Ethernet cable, and get a direct connection from your server machine directly to your router - bypassing your unmanaged switch.
It may also be worth testing things on a completely fresh Roon Server database, but let’s first see if the above changes any behavior. We’ll be on standby for your reply!
Benjamin: It has to be something else. I have a direct (cat 6) ethernet connection between my router and the Mac mini core. Only my Hegel IA and Gustard 26 dac use the switch. This morning when I opened Roon to play a NAS playlist the list appeared as it should but when I hit “Play” nothing happens. The same thing with “Live Radio.” I have to quit Roon, restart the mac mini, reopen Roon and then (sometimes) things begin to work normally. Thank you for the help. Bill
We have just checked the analytics report provided from your Mac M2 Roon server and can see that there were no reboots or crashes of the Roon server actually.
That makes us assume that you likely to have problem with remotes or network rather than with server.
You have also mentioned that you have a problem with reinstallation of the roon Remote manually. Could you please tell us at which step did the problem happen ? In order to reinstall roon manually you have just to drag the existing app from the Finder Apps folder to the Trash bin and just install the fresh app again.
Since we have your logs and you told us that this morning it stopped working could you please share with us exact time when did you experience the issue last time? Or can you reproduce the issue and let us know what exactly happened and when ?
Alex: I have no idea what time it was when I rebooted the system. I seem to have to do a reboot nearly every day to get Roon to work. This morning the core (mac mini) says that I need a software update but it also says that I “have the latest version installed.” One of my remotes can’t connect to Roon server and has been “initializing” for the last 30 minutes. Three other remotes want me to “Select an audio zone” but the only zone I ever need (my Hegel amp) is not listed among the choices. I will have to reboot everything (including my router) once again and hope for the best. An awful lot of work to listen to a playlist. I am willing to try anything reasonable to get the system to work properly. Help! Thanks Bill
From your admin, it looks like all your devices are fully up to date running the latest version of Roon, so you’re all set there.
For the issue around your local audio devices not showing up - macOS Sequoia (version 15), has tighter (and more obfuscated) network security settings than preceding MacOS versions.
Can you please navigate to macOS System Settings > Privacy & Security > Local Network, and make sure Roon and Roon Server are allowed.
If it is already enabled, toggle it off and on again. Then reboot your Mac, and see if the same issue persists.
Lastly, which remote has been stuck initializing for 30 minutes? If it’s one of your macs, can you double-check the firewall settings on that machine? If you temporarily disable your firewall and reboot Roon, are you able to connect?
Benjamin: The toggle off/on technique seems to work. Is it possible that every time I do a reboot on one of my remotes (which is often) running Sequoia, I need to toggle on/off the local network allowance option for Roon to see my audio devices? The MacBook that was initializing found the core after I rebooted it and manually updated to the latest version of Roon. The firewall on/off toggle did not seem to help. I still occasionally get the message that “Roon has quit unexpectedly” and when I click the option to “Reopen” it does. But I wonder: are things switched off in Sequoia such as local network communication when Roon quits. I still think that Roon “quitting unexpectedly” might be the cause of these problems. What do you think might cause these persistent interruptions of Roon software on my system? Thanks for your time. Bill
Thank you for the update and for all the testing you’ve done so far — it really helps us narrow this down.
We want to let you know that we’re aware of this issue on macOS Sequoia. Our R&D team is actively investigating it, but progress is slower than we’d like because Apple has significantly tightened and obscured local network permissions in their latest OS. This means we’re sometimes running into system-level restrictions outside of Roon’s direct control.
In the meantime, the toggle workaround you discovered (refreshing the Local Network allowance) is the most effective way to restore connectivity when the issue appears. We realize that’s not a perfect solution, but it does confirm that permissions are at the heart of the problem.
Take note of the specific name of the track playing when this occurs next - as well as the date and time, and we’ll take a closer look again.
Another setting that may be worth testing: System Settings > Privacy & Security > Full Disk Access → Add both Roon and Roon Server. This can prevent crashes caused by restricted access to core files.
