Roon bridge mac osx monterey not detected by core

Roon Core Machine

Core: Mac OSX Monterey 12.4, Mac mini (late 2014) 2.6GHz Dual-Core Intel Core i5, RAM 8GB

Bridge: Mac OSX Monterey 12,4, Mac mini (M1, 2020), Apple M1, RAM 8GB

Networking Gear & Setup Details

Connected to network via ethernet on same network:
Core address: 192.168.1.174, subnet: 255.255.255.0, Router 192.168.1.1

Bridge: 192.168.1.208, subnet: 255.255.255.0, router 192.168.1.1

Connected Audio Devices

Core detects mac mini over airplay
Also detects roon bridge installed on 2 different raspberry pi 4 setups.

Number of Tracks in Library

12572 tracks (on my mac mini core internal ssd drive)

Description of Issue

When I run roon bridge on my M1 Mac mini it says roon bridge is running but it does not show up on roon core. I have disabled firewalls on both core and bridge mac and still cannot see each other. Core sees airplay on the bridge mac mini but not the roon bridge. What seems to be the problem?

Hey @Houman_Javedan,

Thanks for taking the time to write in, and welcome to the community! We’re super excited to have you here, but also apologize that it was an issue that prompted your first post. No matter, let’s dig in and get your Mac mini with Roon Bridge sorted out.

First to check: make sure the Private Relay is turned off in your iCloud settings.

On your Mac, choose Apple menu  > System Preferences, then click Apple ID. Select iCloud > Private Relay.

On your iPhone, iPad, or iPod touch, go to Settings > [your name] > iCloud > Private Relay.

Your iCloud settings might take a while to load. In order to disable it, simply untick the box and click “Turn Off Private Relay” when the prompt appears.

If Private Relay isn’t being used please try uninstalling Roon Bridge, restart, then reinstall.

Let me know if your issue persists, I’ll be monitoring this thread for your reply :pray:

Hi Benjamin

Private Relay is off on my Mac Mini (ironically it is on, on my iphone and roon works just fine)

I uninstalled roon bridge (app to trash-then emptied, removed library-RAATSERVER and library-ROONBRIDGE folder to junk and emptied)- Reset computer- Reinstalled Roon Bridge. On Mac Mini roon bridge says roon bridge running but roon core does not see it in the audio settings.

Interestingly enough I installed the roon bridge on an intel imac and it sees that one without problems.

Any ideas?

This is my RAATSERVER Log on the M1 Mac Mini running roon bridge:

06/28 21:22:05 Info: Starting RAATServer v1.8 (build 943) stable on macosx
06/28 21:22:06 Trace: [bits] myinfo: {“os”:“Mac OS X 10.16.0”,“platform”:“macosx”,“machineversion”:100800943,“branch”:“stable”,“appmodifier”:"",“appname”:“RAATServer”}
06/28 21:22:06 Debug: [easyhttp] [1] POST to https://bits.roonlabs.net/1/q/roon.base.,roon.internet_discovery. returned after 671 ms, status code: 200
06/28 21:22:06 Trace: [bits] updated bits, in 759ms
06/28 21:22:06 Info: [RAATServer] creating RAAT__manager
06/28 21:22:06 Info: [RAATServer] appdata_dir = /Users/javedan/Library/RAATServer
06/28 21:22:06 Info: [RAATServer] unique_id = 4de09eec-bfec-4e1f-bd04-dcc678734513
06/28 21:22:06 Info: [RAATServer] machine_id = d4bfc581-547e-be6c-44c4-4f877322254c
06/28 21:22:06 Info: [RAATServer] machine_name = Macintosh-3
06/28 21:22:06 Info: [RAATServer] os_version = Mac OS X 10.16.0
06/28 21:22:06 Info: [RAATServer] vendor =
06/28 21:22:06 Info: [RAATServer] model =
06/28 21:22:06 Info: [RAATServer] service_id = d7634b85-8190-470f-aa51-6cb5538dc1b9
06/28 21:22:06 Info: [RAATServer] is_dev = False
06/28 21:22:06 Trace: [raatmanager] starting
06/28 21:22:06 Trace: [raatmanager/mac] FOUND id=10ACEAA0-0000-0000-1B1B-0103803D2378 usb_id=
06/28 21:22:06 Trace: [raatmanager/mac] vendor=DEL name=DELL U2718Q outname=
06/28 21:22:06 Trace: [raatmanager/mac] FOUND id=AppleUSBAudioEngine:AudioQuest:AudioQuest DragonFly Red v1.0:AQDFRD0100130912:1 usb_id=21b4:0082
06/28 21:22:06 Trace: [raatmanager/mac] vendor=AudioQuest name=AudioQuest DragonFly Red v1.0 outname=
06/28 21:22:06 Trace: [raatmanager/mac] FOUND id=BuiltInSpeakerDevice usb_id=
06/28 21:22:06 Trace: [raatmanager/mac] vendor=Apple Inc. name=Mac mini Speakers outname=Mac mini Speakers
06/28 21:22:06 Trace: [raatmanager] initialized
06/28 21:22:06 Info: [RAATServer] running RAAT__manager
06/28 21:22:06 Trace: [raatmanager] starting discovery
06/28 21:22:06 Trace: [discovery] starting
06/28 21:22:06 Info: [discovery] [iface:lo0:127.0.0.1] multicast recv socket is bound to 0.0.0.0:9003
06/28 21:22:06 Info: [discovery] [iface:lo0:127.0.0.1] multicast send socket is bound to 0.0.0.0:54333
06/28 21:22:06 Info: [discovery] [iface:en0:192.168.1.208] multicast recv socket is bound to 0.0.0.0:9003
06/28 21:22:06 Info: [discovery] [iface:en0:192.168.1.208] multicast send socket is bound to 0.0.0.0:50668
06/28 21:22:06 Info: [discovery] unicast socket is bound to 0.0.0.0:9003
06/28 21:22:06 Trace: [raatmanager] starting server
06/28 21:22:06 Info: [jsonserver] listening on port 9200
06/28 21:22:06 Trace: [raatmanager] announcing
06/28 21:22:06 Debug: [discovery] broadcast op is complete
06/28 21:22:07 Trace: [inetdiscovery] added device raatserver/4de09eec-bfec-4e1f-bd04-dcc678734513 in addr:ADDR
06/28 21:22:07 Trace: [inetdiscovery] added service com.roonlabs.raatserver.tcp for device raatserver/4de09eec-bfec-4e1f-bd04-dcc678734513
06/28 21:22:12 Trace: [ipaddresses] enumerating addresses
06/28 21:22:12 Trace: [ipaddresses] FOUND lo0 127.0.0.1
06/28 21:22:12 Trace: [ipaddresses] SKIPPED gif0: no ipv4
06/28 21:22:12 Trace: [ipaddresses] SKIPPED stf0: no ipv4
06/28 21:22:12 Trace: [ipaddresses] SKIPPED anpi1: no ipv4
06/28 21:22:12 Trace: [ipaddresses] SKIPPED anpi0: no ipv4
06/28 21:22:12 Trace: [ipaddresses] FOUND en0 192.168.1.208
06/28 21:22:12 Trace: [ipaddresses] SKIPPED en4: no ipv4
06/28 21:22:12 Trace: [ipaddresses] SKIPPED en5: no ipv4
06/28 21:22:12 Trace: [ipaddresses] SKIPPED en2: no ipv4
06/28 21:22:12 Trace: [ipaddresses] SKIPPED en3: no ipv4
06/28 21:22:12 Trace: [ipaddresses] SKIPPED ap1: no ipv4
06/28 21:22:12 Trace: [ipaddresses] SKIPPED en1: no ipv4
06/28 21:22:12 Trace: [ipaddresses] SKIPPED bridge0: no ipv4
06/28 21:22:12 Trace: [ipaddresses] SKIPPED awdl0: no ipv4
06/28 21:22:12 Trace: [ipaddresses] SKIPPED utun0: no ipv4
06/28 21:22:12 Trace: [ipaddresses] SKIPPED utun1: no ipv4
06/28 21:22:12 Trace: [ipaddresses] SKIPPED utun2: no ipv4
06/28 21:22:12 Trace: [ipaddresses] SKIPPED utun3: no ipv4
06/28 21:22:12 Trace: [ipaddresses] SKIPPED utun4: no ipv4
06/28 21:22:12 Trace: [ipaddresses] SKIPPED utun5: no ipv4
06/28 21:22:12 Trace: [ipaddresses] SKIPPED utun6: no ipv4
06/28 21:22:12 Debug: [easyhttp] [2] POST to https://discovery.roonlabs.net/1/register returned after 183 ms, status code: 200
06/28 21:22:12 Trace: [inetdiscovery] registered 1 devices, 1 services
06/28 21:22:17 Trace: [RAATServer] refreshing @ 10s
06/28 21:22:17 Trace: [raatmanager] announcing
06/28 21:22:17 Debug: [discovery] broadcast op is complete

One more interesting finding. Roon remote on my iphone when I go to settings->about sees the roon bridge at the correct ip address on my m1 mac mini but my roon core running on the intel mac mini does not.

Hey @Houman_Javedan,

Thanks for the updated information. A few follow-up things for you:

  1. Have you tested the M1 in question just as a roon remote? Were you able to connect using it as a remote?
  2. Did you use Time Machine with your Mac minis? If so, your Core machine may not be able to see the 2020 M1, as it will view it as the same machine as the core itself.

Let me know!

1 Like

Hi Ben

  1. Yes the m1 mini does work as a remote when I run the full Roon software

  2. I am not sure what you mean by Time Machine but the m1 mini is a new machine that I did restore from a Time Machine of the core mini and then renamed the old mini. This could be the problem? A clue also is that Roon as a remote does see itself as 127.0.0.1 in the about tab. How would I fix this?

Thx
Houman

Hi Ben

I did a clean install of osx on my mac mini core and renamed it. All is now working well.

Thx
Houman

2 Likes

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.