Roon not opening on mac despite fresh download (ref#K0IUH0)

[Rumpole]

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· Roon would not open on mac. I deleted roon and downloaded a new download from roon site. It won't open either. mac is wired to router via ethernet cable. network is functioning properly.

Tell us about your home network

· Asus router. no vpn, extenders or switch.

EDIT: After reinstalling roon from backup, it opens but can't hold a connection to my PS Audio Lens. It briefly shows up (greyed out) in audio setting but quickly dissapears.So far I've tried: *Toggling local network setting in mac local network settings *Reset router and modem and mac *Made sure airlens is up to date (it is) None of this helped.

[vadim]

Hello @Rumpole

Since you are running macOS, the missing audio devices behavior you are seeing is often tied to the strict Local Network permission controls in recent macOS releases, or a stale endpoint cache in your Roon database.

Please try the following two steps to get your audio devices to reappear.

Step 1: Refresh macOS Local Network Permissions

1. Open your macOS System Settings > Privacy & Security > Local Network.
2. Make sure both Roon and RoonServer are enabled.
3. Even if they are already enabled, please toggle them off and then back on to force a system refresh.
4. Fully quit Roon Server from the macOS menu bar (near the clock icon).
5. Reboot your Mac.
6. Launch Roon again and check if your devices are available.

Step 2: Clear the Roon Endpoint Cache

If refreshing the macOS permissions did not resolve the issue, resetting the internal audio device cache usually does the trick. Note: Deleting these files will clear your customized audio device settings.

1. Create a fresh manual backup of your Roon database via Settings > Backups.
2. Stop Roon and Quit Roon Server from the menu bar.
3. Find and open your RoonServer database folder.
4. Navigate through the folders to: RoonServer/Database/Registry/Core/.
5. Locate and delete all files that start with endpoint_ in this directory.
6. Restart Roon Server and open the Roon app.

(If Step 2 does not help, you can safely restore the backup you made in the first step to recover your previous audio settings.)

[Rumpole]

Vadim, neither of these suggestions worked. When I open Roon, it briefly shows my PS Audio Airlens (greyed out) and then Airlens quickly disappears from the audio screen.

Btw, when I go to “local network permissions” setting, it shows Roon twice. Before, it used to show “Roon” and “Roon server”. Now it just shows two “Roon”.

[benjamin]

Hey @Rumpole,

Sorry to hear the above didn’t help! From a fresh diagnostic report, we can see that Roon does properly identify the device, but as you’ve mentioned, quickly fails to connect:

Info: [devicedb] [autodetect] Match DeviceAutodetectData[Type=RoonReady Vendor=PS Audio Model=AirLens] => PS Audio AirLens
Trace: [raat] [PS Audio AirLens @ 192.168.50.86:36219] connecting (attempt 1)
Warn: [raat_ll/client] [PS Audio AirLens @ 192.168.50.86:36219] failed to connect(0) No route to host
Trace: [raat] Re-initializing endpoint: Sooloos.Audio.Raat.DiscoveryData
Trace: [raat] [PS Audio AirLens @ 192.168.50.86:36219] connecting (attempt 1)
Warn: [raat_ll/client] [PS Audio AirLens @ 192.168.50.86:36219] failed to connect(0) No route to host
Trace: [raat] [PS Audio AirLens @ 192.168.50.86:36219] => Connecting
Trace: [raat] [PS Audio AirLens @ 192.168.50.86:36219] => ConnectionFailed
Trace: [raat] [PS Audio AirLens @ 192.168.50.86:36219] => Connecting
Trace: [raat] [PS Audio AirLens @ 192.168.50.86:36219] => ConnectionFailed
Trace: [raat] [PS Audio AirLens @ 192.168.50.86:36219] client connection failed. Retrying in 500ms 

In networking terms, “No route to host” means Roon can see that the AirLens exists (it found its IP address: 192.168.50.86), but when it tries to actually send music data to it, the door is slammed shut.

Let’s see if cleaning up the Mac “Local Network” Permissions may help. The double entry could be causing the “No route to host” error.

• Go to System Settings > Privacy & Security > Local Network.
• Toggle both "Roon" entries to OFF.
• Restart your Mac.
• Go back to the same setting and toggle both back to ON.
• Better yet: If you can, select one and use the minus (-) button to remove it entirely, then let Roon ask for permission again when you launch it.

If that doesn’t helo, try refreshing the AirLens IP (Address Reservation)

The log shows the AirLens at 192.168.50.86.

• Power cycle the AirLens by flipping the back switch (don't just standby).
• If your router has "Address Reservation" (Static IP), assign a specific IP to the AirLens. Sometimes Roon loses the "route" because the device shifted IPs during the reinstall/reboot cycle.

If that still doesn’t make a difference, let’s fully refresh your RAATServer database.

You can generate a new RAATServer instance on your device by following these instructions, but please be aware that this will reset your Roon Settings -> Audio Tab to factory settings and I would advise making a backup of any custom DSP settings you have:

• Create a Backup of your current Roon database
• Exit out of Roon
• Navigate to your Roon’s Database Location
• Find the folder that says “RAATServer”
• Rename the “RAATServer” folder to “RAATServer_old”
• Restart the Roon App to generate a new RAATServer folder

We’ll be monitoring for your reply, thank you!

[Rumpole]

*toggling Local Network permissions and restarting did not help. Further I still see two “roons”. I can’t toggle one off because when I toggle one of them the other toggles along with it. I still don’t see “roon server” in permissions. Before this all happened there was “roon” and “roon server” showing in permissions. Now it is two “roons” that for some reason can’t toggle off without toggling the other. This seems like strange behavior. There is no way to minus toggle to remove them. I can only turn them off.

*power cycleing the Airlens only results in briefly seeing it in roon devices but quickly disappearing.

*Generating a new RAATServer didn’t help.

*I did not assign a specific IP to Airlens because:

1. I have no idea how to do that.
2. I wouldn’t know what to change it to and I’m afraid of screwing up something in the router admin settings.
3. I’m old and a tech dunce .

I don’t know if this matters but Qobuz Connect app has no trouble finding the Airlens and is fully functional.

I’m puzzled by the appearance of the two “roons” in network permissions.

[alex_h (Alex)]

@Rumpole ,

It is certainly unexpected for your system to show “Roon” twice.

Could you please run the following command in Terminal and share the output with us? This will scan your Mac for any duplicate Roon applications.

find /Applications ~/Applications ~/Downloads ~/Desktop \
 \( -iname "Roon.app" -o -iname "RoonServer.app" -o -iname "RAATServer.app" -o -iname "RoonAppliance.app" \) \
 2>/dev/null

After providing the output, please perform a clean reinstall of Roon alongside with deleting the following folders:

• ~/Library/Roon
• ~/Library/RoonServer
• ~/Library/RAATServer

Let us know please if that helps.

Thanks.

[Rumpole]

*deleted all files you ask

*downloaded and installed new Roon and restored from older backup before all trouble started.

*All worked fine and it saw the airlens until I shut down computer and reopend Roon and then it all went to ■■■■ again and I get the following:

*

*

*

*

And we are back to this with no Airlens showing. It’s maddening!

*

And Local Network Permissions still shows two “Roon” but no “Roon Server” like it used to.

[alex_h (Alex)]

Hey @Rumpole,

Thanks for sharing those screenshots. After reviewing the new installation logs, it appears your Roon installation on Mac is being assigned two IP addresses.

Please close both Roon and Roon Server, then disable one of your IP interfaces on your Mac (either 192.168.50.160 or 192.168.50) before running it again.

Let us know please if it resolves the problem.

Thanks!