How the heck does this work? Over the past week roon has had trouble finding my smallgreencomputer sonicorbiter. after searching it reconnects until it fails again. now
it can’t find the sonic core at all. Have booted, rebooted, changed cables. yes, the internet is working fine. please help.
Hi there! To create a new topic, please click “Get Help” below and enter your details in the form.
Thanks for reaching out! Based on the diagnostic data enabled on your account, it looks like your Roon Server is up and running — the process started successfully and is currently bound to the local IP address 192.168.0.7.
Let’s run a few quick checks to better understand why your SonicOrbiter isn’t being detected:
Check web access
Open a browser on the same network and go to [url=http://192.168.0.7]http://192.168.0.7[/url]
Do you see the Roon Server (web UI) page load successfully?
Check file sharing (SMB)
Try accessing the server via \192.168.0.7 from your computer’s file explorer.
Can you connect or see the folders?
Network and connection
Confirm both your Roon Core (server) and SonicOrbiter are connected to the same subnet (e.g., 192.168.0.x).
Make sure there are no VPNs or guest networks enabled on your router.
Try temporarily disabling any firewalls or network security tools.
If you’re using Asus AiMesh or similar, check that both devices are connected to the same node (main router, not satellite).
Reboot sequence
Power off all related devices (router, SonicOrbiter, Roon Core).
Start your router first, wait 2 minutes.
Then power on the Roon Core, followed by the SonicOrbiter.
If you will have access at some point in time, please try to go to the Roon → Settings → General → Logout and log in again.
Please let us know the results of steps 1 and 2, and whether the SonicOrbiter reappears afterward. This will help us pinpoint where the connection is failing.
I don’t quite understand the steps in #1 but 192.168.0.7 does bring up the sonicorbiter.
I did all of the rebooting as described. multiple times.
roon is connected but there is a red dot above the three lines on the upper left of the home page and a circle keeps spinning.
last night when I went to bed roon kept asking the question “are you on the internet” or something to that effect. yes, I was, and everything else in the house was functioning.
I just now attempted to play something via roon and it began to play.
the latest error message is "metadata improver: paused. roon having trouble verifying connection, etc. connection is good. have rebooted numerous times. have checked with internet provider. all working on my end.
How did you get on with the last item in the list?
Below are the areas it advises to investigate … it will help Roon support to know what you have / have not attempted.
roon is current. I’ve rebooted multiple times. and I have no idea how to change DNS and disable ipv6. I’m an old man. there are no vpn, firewalls, or antivirus. roon has been working flawlessly for years. nothing has changed on my end. I need help. thank you.
We do not offer phone support, but we’ll be more than happy to assist you right here on the Community website.
When we troubleshoot through the Community, it ensures that our entire team has access to the discussion and can weigh in as needed — including our Support, QA, and Development teams.
From the diagnostic data enabled on your account, we can see multiple warnings related to metadata server access:
All of these errors are marked as Unauthorized, which means your authentication token may have expired.
Let’s refresh your credentials to reauthorize access:
Open Roon → Settings → General.
Click Log Out under your Roon account.
You’ll be redirected to the login page — please sign in again using your usual credentials.
This process is safe — your database and settings will remain intact. However, as a best practice, we always recommend creating a manual Roon backup before making any account changes (just in case).
Once you’ve logged back in, please check if the issue persists and let us know the results.
a very wise person suggested deleting my roon account and installing a fresh version. once logged in to the new version I was up and running. his was the correct solution.