@support After updating Roon Core and the Mac app to 1.3 (200), my Macbook no longer connects as a remote to my Roon Core (Ubuntu Linux, Roon 1.3 (200)). It sits there trying to connect indefinitely. I reinstalled the Mac app, Rebooted the Mac, and I also removed ~/Library/Application\ Support/Roon. No change. It worked fine in 1.3 (196). My Android phone (Roon 1.3 (196)) connects to the Core correctly.
Update: rebooted the Linux server to install the latest Linux updates, and now the Mac app sees the core. I guess I’ll take it, but I’m wondering if Core finding (through multicast?) is a bit less robust than it should be for the Mac app.
In build 200, we fixed a bug related to the discovery protocol. As you suspect, the bug was making discovery less robust compared to 1.2–but both the remote + the core needed updates to address the issue. That’s why updating the linux side made things snap into place.
I have a similar problem with the iPad app and my Debian sever. I do connect but when I return to the iPad after a screen lock it can take upwards of a minute to reconnect to the server.
Thanks, but I’m a bit confused. The problem came up after I updated the core to 200, and only went away after I rebooted the Linux server hosting the core. Does this mean core updates require a host OS reboot to take effect?
Back to the same problem, now with 203 everywhere. Android remote connects to Linux Ubuntu core without problems, Mac remote can’t find the core even though it’s on the same network as the Android device. No success after rm -rf ~/Library/Roon/ on the Mac, or rebooting the Mac. Whatever fixes were made for core discovery in 203, they’ve not succeeded, and in fact they seem to made it worse for Mac remotes. Unlike previous incidents, rebooting the Linux server with the core did not help: Android client finds the core, Mac client does not. Reinstalling the Mac app, rm -rf ~/Library/Roon/ don’t help.
I had the same problem. When I restarted the Roon Server I could connect again.
sudo systemctl stop roonserver
sudo systemctl start roonserver
Thanks, I have scheduled backups, one happened at 4am today (which stops and restarts the core as a side effect) and now the Mac sees the core. Mac > Linux core discovery, which was not great in 1.2, still pretty fragile, IMHO.
@support Every Roon upgrade sends my Mac remote to never-never land, this is driving me batty because I use the Mac remote to manage my library. My Android remote has no problem. The latest problem is with 204. All the tricks that worked before failed this time. Removing ~/Library/Roon, rebooting the Mac, rebooting the core server, reinstalling Mac app, nothing worked. The Mac remote is stuck looking for a remote library that is right now playing under my Android phone’s control.
Using tail -f on the Roon core log, here’s what I think is a sequence of events that documents the failure, from starting the Mac app:
02/20 09:09:26 Trace: [transport/raat] RAATServer discovered: RaatServer pereiras-MacBook-Air @ 192.168.2.25:61610
02/20 09:09:26 Info: [transport/raatserver] GOT SERVER f9bbd928-7b67-457d-c48b-1fa2349381b0::a98bf283-294a-450e-a67e-e224103d4b0f @ 192.168.2.25:61610 pereiras-MacBook-Air PROTOVER=1 RAATVER=1.1.13
02/20 09:09:26 Trace: [transport/raatserver] [RaatServer pereiras-MacBook-Air @ 192.168.2.25:61610] connecting (attempt 1)
02/20 09:09:26 Trace: [transport/raatserver] [RaatServer pereiras-MacBook-Air @ 192.168.2.25:61610] connected
02/20 09:09:26 Trace: [rnet/RnetJsonClient] SENT {"request":"enumerate_devices","subscription_id":"0"}
02/20 09:09:26 Trace: [rnet/RnetJsonClient] GOT NONFINAL {"status": "Success", "devices": [{"device_id": "AppleHDAEngineOutput:1B,0,1,1:0", "type": "coreaudio", "name": "Built-in Output", "vendor": "Apple Inc."}, {"device_id": "default", "type": "coreaudio", "name": "System Output", "is_system_output": true}]}
02/20 09:09:26 Info: [transport/raatserver] GOT DEVICE a98bf283-294a-450e-a67e-e224103d4b0f::AppleHDAEngineOutput:1B,0,1,1:0 Type=coreaudio Name=Built-in Output Vendor=Apple Inc.
02/20 09:09:26 Info: [transport/raatserver] GOT DEVICE a98bf283-294a-450e-a67e-e224103d4b0f::default Type=coreaudio Name=System Output
02/20 09:09:36 Warn: Error in web request https://push.roonlabs.com/push/1/connect: NetworkError (The remote server returned an error: (502) Bad Gateway.)
02/20 09:09:36 Trace: [push] request to manager failed
02/20 09:09:36 Trace: [push] retrying connection in 588344ms
Since the 1.3 update, I’ve wasted 10-20 hours debugging problems with the Linux and Mac Roon distributions. This is way too much for a supposedly consumer-grade product. I’m very disappointed.
Just tried another set of troubleshooting moves: use the find command to look for files in ~/Library connected with Roon, and delete them all. First time round it didn’t help, but I tried again and for good measure I watched the newly created log file with tail -f before clicking on the “I Agree” button in the initial setup screen. Guess what, I then selected using Mac as remote, and my core was found by the Mac app for the first time since the 203 update. No idea what changed.
Mac app crashed on its own when I was at work and Roon inactive. When I restarted it, it failed again to find the core. Managed to restart successfully after rm -rf ~/Library/Roon/ and rm -rf './Library/Saved Application State/com.roon.Roon.savedState', so it looks like some of the saved info is confusing the app.
@support Mac client hosed yet again, after the Macbook came back from sleep. Removing the directories noted above is not helping. I’ve not heard back with a request for more information even though this problem has been going on for 11 days.
Hi @Fernando_Pereira ----- Thank you for the report and my apologies for the slow response here. I will be contacting you momentarily via PM to grab some logs and some more information regarding this issue you are experiencing.
-Eric
Long story short, the root cause was that the Mac firewall had switched to reject incoming connections to Roon. Since I never touched it myself, either Roon itself or MacOS did the deed. Anyway, check your Mac firewall settings if this happens to you.
2 Likes
Closed due to inactivity. If you are still seeing this issue, please open a new support thread.