My Roon Server is ROCK. ROCK and all remote devices are up to date as are the remote apps. I can connect to ROCK from my Windows 11 PC, a MacBook Pro, three iPads, and two iPhones. But, recently, another iPad and iPhone can’t connect. When trying to connect, the details of the ROCK are all there (version, IP address), but the Connect button is grayed out and there’s a red dot instead of a green one.
All devices are on the same subnet with the same netmasks, gateway, and DNS server. The settings on the IOS devices that aren’t working are identical to those that are, and they’re all on the same wifi network.
After several hours looking for the problem, I reinstalled ROCK from scratch and the IOS apps on the devices that aren’t working. The problem remains the same. Ditto with new Roon servers installed on my Windows 11 PC and MacBook Pro. So this is a client-side issue.
Everything is inside my firewall, no VLAN issues, just a big mystery.
“Something” is preventing these IOS apps from connecting to the server. It’s likely a client-side issue. I’m grateful for any ideas.
Ah, that may be a factor. One new iPad was cloned from an older one and was activated with a new Apple account. The new iPhone was cloned from an older one but with the same Apple account. I deleted and reinstalled the Roon app a couple of times on each of the new devices, to no avail.
I cloned another new iPad using the “side by side” transfer and changed the Apple account and that one works just fine with Roon.
I hope that there’s a fix that doesn’t involve a total clean rebuild of the iPhone and iPad that aren’t working with Roon.
Many thanks for the link. I think that I’ve found a solution to the cloned IOS device issue.
Yesterday, Roon’s server infrastructure seemed to be very challenged: it took a few hours to download the Windows Roon installer (less than 200MB), and search wasn’t working. This may have contributed to the connection issue.
Today, I deleted the Roon app from the IOS devices that weren’t working, immediately shut down the devices, restarted them, and reinstalled the Roon app. Everything worked. It may have been that deleting the app and restarting a device cleared any lurking token/identifier in memory, or it may have been that Roon’s servers were back at full strength. In any case, it’s great that a full from-scratch install of the affected devices wasn’t necessary.