· Can no longer open my home (library) using Roon Remote on MacStudio (Tahoe26.3) since updating Roon Server to v2.6 build on NAS (Synology DSM1522+); Upon launching the Remote, it goes into the panel--shown in the uploaded image--stays on indefinitely.
In contrast, the Remote on MBP14 (Tahoe26.2) works fine with the same server; Comparison between Remote's Log-files (details available if needed) on the two Macs shows some differences after each makes initial connection with the Roon Server;
Remotes on iPhone and iPad devices continue to work fine; FYI, OS for both mobile devices slightly lag behind the most up-to-date iOS & iPADOS.
Tell us about your home network
· Internet Router is Verizon Fios unit (Make: VZPD Model: CR1000A, 5GHZ Band = channel 6, 2.4GHZ Band = channel 11); Using multiple eero 7 and 6 devices (not in the bridge mode) to create the mesh subnet for the house, its main unit connected to the Verizon unit via 10Gb ethernet. Problematic MacStudio is connected both wireless and ethernet, while MBP14 laptop is connected wireless. Both computers work fine in all aspects network-wise. Not using VPN at the moment. Problem persists when the Firewall is deactivated, also when the Mac is run in the Safe Mode. Private Wifi address, Switching on and off of Limit IP address tracking, and other security measures don't seem to affect the issue.
Since you’re running macOS, the behavior you’re seeing is consistent with the newer, stricter Local Network permission controls in the recent macOS releases.
Please try the following steps:
Open macOS System Settings → Privacy & Security → Local Network
Make sure Roon and Roon Server are both enabled
Even if they are already enabled, please toggle them off and back on
Fully quit Roon Server from the macOS menu bar / task bar
Reboot your Mac
After reboot, launch Roon again and check if the devices is avaliable again.
Once these permissions are refreshed and the system restarted, your audio devices should reappear.
Please let us know if the issue persists after these steps, and we’ll continue from there.
I tried the steps as you suggested, but the same problem. (I am not running the server on macOS at the moment, so the steps applied only to the Roon Remote that used to work fine fetching data from the Roon serving running on my Synology NAS.) After rebooting, the Remote gets stuck in the same state as shown in the screenshot originally submitted with the ticket. I left it for a couple hours, and nothing changed.
To provide a bit more information, I have looked into the log-files from Remotes on my two Macs in interacting with the latest version of the Roon server on the Synology NAS. The Roon Remote on my MacBook, MBP14, successfully connects to the server on the NAS and displays my Roon library off the database also hosted on the NAS. The Remote on my MacStudio, however, fails, even though it seems to communicate with the server at least partially. I have documented these detailed observations here. Hopefully, this may help locate where the Remote fails to close the Connect panel and move on to display the library on Mac Studio.
I will wait for your suggestion for the next step.
This morning, it occurred to me that I have one more Mac - an iMac - that I can use to test the issue. It was running Tahoe 26.2 as of this morning, and is on the same eero network as my other Macs are. I have never used Roon Remote on this particular machine, so I downloaded and installed the latest Remote and ran it. Its “Connect to…” panel immediately listed the Roon server on my NAS with the “green” round button attached and when I chose it, proceeded to open my Library almost instantaneously!
Then I further wanted to see if it still works fine under the latest Mac OS (Tahoe 26.3). So, I updated its Mac OS, and again, it worked just fine. So I now have two Macs running Tahoe 26.2 (MBP14) and 26.3 (iMac) with the latest Roon Remote working just fine with the latest server on the Synology NAS.
This test suggests that the issue seems to be localized to my MacStudio (Tahoe 26.3, but this OS may not be the cause contrary to my earlier suspicions), for an unknown reason at this point. As MacStudio is my main work machine, it has both wireless and ethernet connections (though earlier I tested to disable one to focus each of them separately without any positive outcome), and many external volumes attached. As for system extensions that might possibly interfere with Roon, I also had tried to test in the Safe Mode, with the same result. So, I would appreciate if you can point to a way to systemically eliminate potential culprits on MacStudio.
I tried fiddling with the network configuration on my MacStudio now that I have verified that another Mac running the same latest MacOS (Tahoe 26.3) allows the latest Roon Remote (2.60 build 1629) to work fine with the latest Server (2.60 build 1629) running on my Synology NAS. The most obvious difference between the two Macs became some details in their respective network configuration.
The culprit was that on MacStudio, I was using the “DHCP with Manual IP Address”. The other Mac - MBP14 ran the Remote successfully and it was using “DHCP”, all other setting options being equal.
So, now I have everything running OK on all Macs, using “DHCP”, using public DNS by google and openDNS, Private Wi-Fi address = Fixed, Wi-Fi 6E mode = Automatic, Limit IP address Tracking = ON, Firewall = Active, not using VPN)!
For a reason that I don’t quite remember, but likely for setting up the Roon Arc, I had set the Manual IP Address mode for MacStudio.(The manually set ip address was then reserved via eero settings.) I eventually gave up on the Roon Arc, but kept the manual ip setting. With earlier Mac OS versions, this apparently wasn’t a problem. But with Tahoe 26.3, it seems to have become an issue.
But it would be great if you can explain to me why choosing the Manual IP address mode for my Mac wifi has become an issue under the latest MacOS. To be more specific, why the Roon servers log file never reached the “Authenticating…” step in its Connecting to Server stage (step 5 in the comparison of the log files from two Macs) when the MacStudio was in that manual ip address mode?
