iOS devices cannot connect to Roon Core

Core Machine (Operating system/System info/Roon build number)

2017 iMac, Big Sur 11.1, 24GB RAM, firewall turned off, on both Ethernet and local WiFi network
Roon Version 1.7 (build 710)

Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)

Eero WiFi mesh, all Roon communication is over WiFi

Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)

iPhone 11 Pro, iOS 14.3, WiFi
HiFiBerry Raspberry Pi 4, WiFi

Description Of Issue

I listen to Qobuz via Roon with a number of iOS devices and a HiFiBerry Raspberry Pi 4. This morning the Roon app on my iOS devices cannot find my Roon Core. After starting the app, I see “Choose your Roon Core” and “Looking for your Roon Core…” with no success.

Also, selecting “Configure Roon OS devices on your network” gives me a “Searching for devices…” window but nothing is found.

I restarted my Roon Core iMac and confirmed Roon is running. Also restarted iOS devices, with no luck.

I also restarted the Eero network.

The problem began this morning. There have been no changes to the network configuration or OS of the Roon Core or my WiFi network. This all worked with no issues yesterday.

I also notice that go.roonlabs.com is down, FWIW. Maybe it’s related.

Thanks in advance for your assistance.

Hi, make sure you have enabled Local Network from iOS Roon settings. This is new setting for iOS 14, so if you just updated from earlier version that need to be changed.

Thanks for the suggestion, but that setting was already turned on.

It’s all working now, however. It took another restart of Roon on the Core machine. The Roon application on the Core has hung twice and required a forced quit. I’ll run some disk maintenance to remove any possibilities there.

1 Like

Well, I spoke too soon. It went down again. I had to force quit Roon on the Core machine and restart it to get it work again.

Any ideas why this is happening?

Hello @Gene_Hopstetter, my apologies for the issue here. Have you rebooted your router since this issue started?

Closed due to inactivity. If you are still seeing this issue, please open a new support thread.