Please try to restart your network setup by unplugging, waiting 30 seconds and then replugging in your networking gear.
· No, the issue remains the same
Please select how you've connected your Roon Server to the internet
· Roon Server is connected by *Ethernet*
Have you checked your firewall settings to ensure that Roon is allowed through?
· Roon still won't connect even after checking this aspect
Have you verified that Roon Server is on the same subnet as your Remotes?
· My Remotes and Server are on the same subnet and I still can't connect
Sometimes the issues can be resolved with a reinstall of your Roon Remote app. Let's try to perform a reinstall and see if it helps.
· I've reinstalled the Roon Remote but it did not help
What is the operating system of your Roon Server host machine?
· *MacOS*
Select any of the following components that are present in your local network setup
· None of the above
Describe the issue
My ipad can't find my toon server on my Mac mini. I delete the app on the ipad and reinstall it and it finds it right away. I turn off the ipad or stop the app, and when I try again it won't connect. So I delete and reload the app and it connects no problem. so as long as I don't stop it, it stays connected. Same with my iphone, If I stop the app or turn off my phone, I have to delete and reload the app, then it works. For my PC, it can't connect as a remote. It sees the Mac Mini server and wants me to deauthorize it. It gives the option "oops I meant to connect as a remote" but when I select that it does not show the Mac Mini.
Describe your network setup
I think this is irrelevant since it does connect, I just have to keep reloading the apps
Thanks for writing in and for sharing your report! It sounds like your devices are losing the “handshake” with the server once the initial session is broken. Since a fresh install fixes it temporarily, the server is definitely running, but the discovery protocol (how the apps “find” the server on your network) is failing to reconnect.
Here are the most effective steps to troubleshoot this:
Assign a Static IP to the Mac Mini - If your router assigns a new IP address to your Mac Mini, the iPad and iPhone apps will “look” for the old address and fail. Reinstalling the app forces a fresh scan, which is why it works temporarily.
Go to System Settings > Network > Wi-Fi (or Ethernet) > Details > TCP/IP.
Change "Configure IPv4" to Using DHCP with manual address.
Pick an IP address (like 192.168.1.50) that is outside the range of your other devices, or set a DHCP Reservation in your router settings.
2. Enter the IP Address Manually
On the iPad or iPhone, when it says "Looking for Roon Server" or "Searching," look for an option that says "Configure IP" or "Help".
Enter the specific IP address of your Mac Mini (e.g., 192.168.1.XX).
This creates a direct "hard-coded" path that survives app restarts.
3. macOS Firewall & Privacy Settings - Even if it works once, macOS might be blocking the specific ports needed for background discovery.
On the Mac Mini, go to System Settings > Network > Firewall.
If it’s ON, go to Options and ensure the server application is set to "Allow incoming connections."
Additionally, go to Privacy & Security > Local Network and make sure the server app is toggled ON.
It may also help to temporarily disable your macOS firewall, and check if the same issue occurs.
We’ll be monitoring for your reply, thank you, Bruce!
step 1 make no sense. I am restarting my iPad, not the Mac Mini server. The mac IP doesn’t change when I reboot my iPad
Step 2 I have tried on all devices entering the IP of my server, that doesn’t work either
step 3 I do not have any firewall or filevault enabled
The other issue is that every time I restart roon on the server. It disconnects from Tidal and it takes many , many attempts to get it to work. It goes to Tidal, I log in, it accepts that, Tidal says I have connected my account, , but Roon keeps saying that there is an error authorizing Tidal
then again, I do the exact sme things and everything logs in no problem, then randomly it doesn’t
I think the next step here is to enable some diagnostics on your account so our technical staff can get some more insight into what’s going on here.
However, before I enable this feature, I’d like to ask for your help ensuring we gather the right information.
First, can you please reproduce the issue once more and note the time at which the error occurs. Then respond here with that time, and I’ll make sure we review the diagnostics related to that timestamp.
Wanted to follow up on this. Were you able to reproduce the issue again and note the exact time it happened? If you can send that timestamp over, we can review the diagnostics around that point and take a closer look. Thanks!
