Please try to restart your Roon Server by closing the Roon app in the taskbar or rebooting your Roon Server machine.
· No, the issue remains the same
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 *WiFi*
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?
· *Nucleus*
Select any of the following components that are present in your local network setup
· *Mesh networks*
You mentioned a mesh network in your setup. Certain common mesh networks might require slight reconfiguration to support Roon.
· None of the above
Describe the issue
I lost contact with my Nucleus. The iOS app sees it occasionally, tells me to sign in and tells me I’m already signed in! Then it goes to the loading icon, after which I sometimes get a message saying something’s not right or it tells me the server cannot be found. This goes on in a continuous cycle.
Describe your network setup
I have wireless broadband connected to a TP-Link mesh node directly. In turn, the node is hard-wired to the Nucleus.
Thanks for reaching out to ask us about this issue.
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.
This was in the course of two minutes, taken, well, two minutes ago.
I have a feeling that part of the problem possibly lies in that it saw two Roon cores, the other being my MacBook. Having said that, I unauthorised the MacBook (which has never been designated as a core) and the problem continues.
Thanks so much for your patience, and our sincere apologies for the delay in getting back to you. We’re a small team, and while we aim to respond within 24 hours, it can sometimes take a bit longer for a thread to reach the top of our queue. We truly appreciate your understanding and cooperation!
You mention you have a mesh network - we’re seeing some network-related errors from a recent Nucleus diagnostic report. Could you temporarily set up your Nucleus via ethernet to your primary router?
We’re also seeing a potential for your remote devices connected to different subnets within your local network, can you review your router settings > devices list and confirm you don’t have two active subnets?
I’d give your router a reboot as well, if you haven’t already. We’ll be monitoring for your results and reply!
I have found the problem. Is this a glitch in the software? When I try to upload to the server files stored on my MacBook, Roon seems to think that the MacBook is the core and gets confused. I found that I had to unauthorise the MacBook and then everything goes according to plan.
So, how do I stop Roon from thinking my MacBook is the core?
If you quit RoonServer from the taskbar, there should only be the Nucleus server visible. Have you been able to locate it as per @benjamin ‘s instructions?
After several hours of uninterrupted play, today, I uploaded more ripped tracks from my MacBook and now am back to square one.
Both the MacBook and the Nucleus were showing up as servers (again). I de-authorised the MacBook and it fixed the problem, though it had never been set as a core. Before the Nucleus, (I don’t think you read these posts properly) I used a MacMini as the core.
So, confidently, I uploaded more ripped CDs through the Roon app on the computer.
Now, it seems to think the MacBook is the core and everything has crashed again.
This must be a software issue.
Your previous response seems to have been based on the assumption that I have used the MacBook as the core, which has never been the case.
It would be good to get this sorted out. I don’t have a television and listen to music when not working.
The silent void is, at this moment, filled only with the sound of the dog farting.
Thanks for the update! An odd issue indeed, let’s see what we can do about getting you back up and running properly. It sounds like the process of adding more tracks to your Roon library is triggering the issues.
Can you break down your process of how you’re adding tracks? I’m interested to figure out how Roon Server is restarting on your Mac after you’ve quit it.
Are you transferring tracks over the network to your Nucleus internal storage?
I was initially dragging and dropping the files into the Roon app on my MacBook, but subsequently added them directly through Finder. I thought this might make a more stable transfer but to no avail.
As I have said, I have never used my MacBook as the server, though it seems to think I have. When I connect to the MacBook through the iPhone app, it shows stuff I had added from Tidal. I haven’t used Tidal in about four years. Even then, the core was a MacMini.
