· Other
· None of the above
· Other
Roon on OSX loses connection to USB DACs though OSX still sees them in Sound Control Panel
1Gbps Ethernet to EERO WIFI7
Hey @Dan_Clark,
Thanks for writing in! Sorry to hear about your connection issues to local devices on your Mac. As a first step, can you please navigate to macOS System Settings > Privacy & Security > Local Network , and make sure Roon is allowed. If it is already enabled, toggle it off and on again. Then reboot your Mac, and see if the same issue persists?
It may be worth confirming that both the DAC and Mac are running on the same local subnet as well.
We’ll be on standby for your reply! 
There is no “Local Network” on that path.
OSX 14.6.1
There is no “Local Network” on that path.
OSX 14.6.1
Hi @Dan_Clark,
Is the OSX 14.6.1 computer the only one experiencing this issue? Our records show another Roon Server running on OSX 15.3.0, which is why we provided the advice we did.
From what you’ve described, it sounds like a firewall may be blocking RAATServer. Could you try whitelisting Roon, RoonServer, and RAATServer in your firewall settings and see if that resolves the issue?
Let us know how it goes!
Hi Daniel, thanks. I decided ot update the Mac Mini on 14.6 to v 15, let’s see if that resolves it. It may take a day or two to know.
Hi @Dan_Clark,
Thanks for letting us know. We’ll be on the look out for the results of updating your Mac!
FWIW updating 14.6 to 15.3.2 broke Roon, it wouldn’t start as the server and would loop back to the server not found page, even though the Mac Mini IS the server.
Uninstalling and reinstalling resolved.
I should know within a day or two if the USB issue is resolved. It’s certainly running faster now.
Hi @Dan_Clark ,
Glad to hear that reinstalling resolved the issue! Please keep us posted on how things are working on the USB side after further testing, thanks!
Problem is not resolved, it recurred today when the machine woke up after 2 days. It not only couldn’t find USB devices it couldn’t find itself, still. LOL. All listed services are enabled in firewall.
Edit: I did briefly see a pop up that Roon was still running when I rebooted, even though I had exited Roon when it couldn’t find “the server.”
I have this issue still with RME UCXII interface.
Hey @Dan_Clark,
Sorry to hear your issues persist!
Can you reproduce and share a more specific date and time? That way, we’ll be able to review a fresh diagnostic report and analyze it further.
@Amino7996 if you could fill out a fresh support thread, you’ll be able to get proper and dedicated support - please use this link:
https://account.roonlabs.com/en/contact/new-ts-request
Thank you!
It was 2 days ago, right before I posted that the problem persisted, so that should be in the logs… I will post again tomorrow if it recurs.
Hi @Dan_Clark,
Sorry for the confusion here - we see multiple Mac’s running both Roon as well as Roon Server, on top of a Linux machine also running Roon Server.
Are you referring to the Mac Mini, when you were using Roon? You mention earlier that your Mac Mini is what you’ve been using for your Roon Server, so we’ll just need a bit more clarity on what your current set up is, and which machine is experiencing the lack of connection to your system outputs and DACs.
There’s also a Macbook Pro in the mix, are you seeing any issues there?
Thank you for the additional clarity and details here! This should help us pinpoint additional information via fresh diagnostic reports from the issue machines.
The Mac mini is the unit having problems.
The Linux server has its own issue of Qobuz loading slowly but that’s OT, and the MacBook has no problems but isn’t used much.
The Mac mini is the unit having problems.
The Linux server has its own issue of Qobuz loading slowly but that’s OT, and the MacBook has no problems but isn’t used much.
Thanks for the additional informaiton @Dan_Clark!
We were able to review a fresh diagnostic report from the Mac Mini, and saw a few potential network related hiccups that could be interfering with your endpoint connections (even your system output on the Mac)
We see RAATServer lose and regain connection in a pattern until it ultimately fails, to which you then restart Roon and are able to refresh the connection:
Trace: [Broker:Transport] [raatserver] [RaatServer Mac-mini @ 127.0.0.1:9200] lost client connection. Retrying(0)
Now you should be able to test the following if you haven’t:
Another area to check : navigating to your Network settings (WiFi → Details) and checking whether the Mac in question is relying on a Fixed , not a rotating, Private WiFi Address.
Let me know the results of the above, thank you! 
Roon and RAAT definitely allowed through firewall.
I had wifi and LAN connected but LAN is what is in use right now. The problem exists whether I’m on Wifi or LAN. For now I am the only device on the LAN. We use both IPV4 and 6.
That said not sure why this is an issue, as the server is the Mac mini and the the USB devices are all local. The Mac mini sometimes can’t identify itself as the server and can’t see the local USB devices.
Hey @Dan_Clark,
While this would certainly give you two IPs, they usually still fall within the same subnet. In your case, we’re still seeing two different subnets altogether. Are you able to test out my above mentions of accessing your router settings and disabling one of them temporarily?
While they may be local to the same machine, Roon still relies on network protocols to detect and communicate with devices. If the Mac mini sometimes “can’t identify itself as the server,” it could indicate that network settings (such as multiple subnets, VLANs, or isolation settings) are interfering with its ability to recognize its role.
I can’t really do that as the other subnet is a Tennant, but we’re not on that network.
I have turned off WiFi on the Mac mini and am just using LAN. So far the machine has gone through two sleep cycles without borking.