Constantly ‘Looking for Roon Server’ followed by 'UhOh Somethings Not Right". Sometimes rebooting everything helps it connect for a short period, then I have to constantly go through the same cycle. Orbi mesh network, Nucleus One plugged directly into main router. Started with Nucleus One, when my server ran from a NUC, I had no issues.
You say the operating system of the server is Windows but you also say that you have a Nucleus One. Are you sure you are trying connecting to the Nucleus One and not a server on your Windows machine?
Is the device you are trying to control Roon from wired or wireless? What device(s) have you tried to connect to Roon from?
Thank you for the report and we’re sorry to hear you’re experiencing intermittent connection loss to the Nucleus One. If the server and client had already established a handshake and you’re actively browsing when you encounter the connection loss, then the Nucleus One has temporarily lost line-of-sight to the client device. Diagnostics from the Nucleus One don’t show the network stack struggling with a connection to the internet.
Are your Windows, Android, and iOS remotes served by mesh node(s) in this setup?
If so, I’d check the following:
Verify the backhaul between the main router and the node is reliable; if using WiFi, hardwire the node via ethernet.
Disable any band steering settings, or temporarily switch to a single band (2.4 or 5.0) only on the router.
Most importantly, ensure that Disable IGMP Proxying is toggled off in the Orbi mesh node settings. This setting can interfere with device announcements.
Roon Server on Nucleus One is hardwired directly to the ORBI router. All remotes are on the same network, either wired (PC) or wireless (phone, iPad, laptop). ALL REMOTES display the same behavior, all the time, regardless of condition or location. Backhaul is fine. The network works fine otherwise, no problem with over 100 devices. If I restart everything from the modem and all remotes, it usually works for a bit, then the same stuff starts to happen.
I’ve been through all the tips and troubleshooting guides, all the settings are set like they are supposed to be.
Can you please let us know the exact local time + date when you next get into this state? We will enable logging for your Nucleus and check to see if logs have any clues. Additionally, it would be helpful if you could try to set reserved IP address in your router for your Nucleus and Roon remotes to ensure that the IP address remains the same.
I spent the day overhauling my network - connected both of my ORBI satellites via ethernet to get the highest backhaul (both solid/Good), gave a static IP to the Roon Server, rebooted everything. For several hours after I started things back up, I had awesome, snappy performance. Then … again with this problem. July 4th at (and around) 1347 EDT, I’m right back where I started.
Thanks for the update! Sorry to hear your issues persist.
From a recent Roon Server diagnostic report, we see some network-related failures around the timestamp you’ve shared, including a status code: 999
(none) user.notice roonconfig/run: 07/04 14:43:17 Warn: [push2] request to push manager failed (https://push-manager.roonlabs.net/1/connect) with status code: 999
(none) user.notice roonconfig/run: 07/04 14:43:17 Trace: [push2] retrying connection in 68499ms
(none) user.notice ntpd/run: sendto: Network is unreachable
Your Server is not getting a valid IP address or DNS configuration, which is breaking cloud service communication. As a next step in troubleshooting, it may be worth testing out a different DNS server - we have seen users have a better experience in the past if they change their Router’s DNS servers from the ISP provided ones to Cloudflare DNS, Quad9 or Google DNS.
Can you please give this a try and let me know if it helps? Thank you!
We’re not equipped to troubleshoot further without a response here. This thread will close shortly due to inactivity - if the above suggestions haven’t resolved your issue, please reach out in a new technical support request to continue the conversation.
AceRimmer
(Smoke me a kipper, I'll be back for breakfast!)
12
I reopened this for you but please respond before it automatically closes again due to lack of action.
After multiple sessions of working on the network, I am able to get good performance for periods of time, but then the same problems starts again for a while, only to resolve itself sometime later. For example, this afternoon (7/12) from about 1650 to 1700 EDT, multiple cycles occurred of looking for server, uh oh somethings not right, roon symbol for long periods, interface opens, looking for roon server, uh oh… and so on.
My Nucleus One is connected directly to the main router (ORBI 850) via ethernet with a static IP address. I have two satellites which are both connected wired with Good backhaul. My main remotes are connected directly to these satellites via ethernet cables. Other remotes are on the wireless network. When this behavior exhibits, it doesn’t matter what remote and what condition it’s in, they all do the same thing. I changed the router DNS settings to the Cloudfare settings, and checked again that all of the various tickboxes and settings are ticked and set how the various troubleshooting guides on the Roon site tell me to do so. Every other device, every other connection (e.g., Tidal & Qobuz connect), every other manufacturer app/connectivity method (I have Bluesound, Naim, ELAC, Chord, etc. components) works absolutely seamlessly on the network, and overall network performance is solid, snappy, and without hitch (even better now that I wired the satellites). Hoping the logs from this ten minute period can shed some light on what’s going on.
Now at 0905 EDT on 7/13, I get a “Waiting for your Roon Server. Roon is still trying to connect, but it’s taking longer than usual.” on an ethernet connected remote (PC). On my android phone, I have a hanging Roon symbol.
From 0922 to 0932 (and beyond), I am now in multiple cycles where it slowly loads into the remote interface, displays the recently played and listen later (as well as library stats), then hangs up as it tries to load the recommendations, etc. below that - cycle after cycle of “Waiting…” followed by “Uh oh, somethings not right”)
Largely seamless operations at various points after this morning. Now at 2244-2245 on 7/13 same problems, continuous cycles of getting hung up and returning errors. I pointed it out above, but for troubleshooting purposes, I didn’t have these problems before I switched the Nucleus One. For various reasons, I don’t want to go back to the NUC that had my server on it before.
Problem resolves at about 2249 and music will now play.
Thanks again for providing those timestamps. Unfortunately, I was only able to review the most recent one, as earlier logs had already been overwritten. Around that last timestamp, we are seeing the kind of network interruptions you described, including devices temporarily dropping out.
In your Orbi mesh setup, please make sure that multicast is enabled. Also, check whether band steering is turned on. This can sometimes cause instability for networked audio devices. If it is enabled, try turning it off to see if that improves things. Let us know how it goes!
There is no specifically labeled “multicast” feature in the router settings (basic or advanced). Perhaps relatedly, I have ensured that “Disable IGMP Proxying” is unchecked as noted above. Please advise if I’m missing something here.
Re: “band steering”, it does not appear that Orbi routers have the ability to toggle this - it has dual band capability under a single SSID. I can adjust the relative power of the bands to try and steer devices toward the stronger signal, but as the core (connected directly to the router via ethernet) appears to be the common denominator, would band steering affect all remotes across bands at the same time the same way? Not sure if that’s the issue if we’re trying to address the stability of “networked audio devices” (components? Roon core on Nucleus? Remotes?) - the problems are the same with all remotes, regardless of connection method/status (wired, wireless, agnostic to platform - PC, Android, Apple, etc.)
