A few weeks ago my ARC started working improperly and doesn't work at all now in the car. Subsequently, I started having issues with ROON itself and roon has become unstable on iPad into my main sound system (and iPhone). It even became a problem to use Bluesound but I have resolved that issue by deleting all the apps and gradually reinstalling Bluesound and then Roon. Roon continues not work - it cycles from working to "uh oh, something is not right" and back to working, etcetera, etcetera... Roon still works properly on my Mac mini playing into my main sound system. With regard to ARC I attach diagnostics from roon arc: { "ipv4_connectivity": {"'status":"NetworkError","status_code":504,"error":"error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined"}, "external_ip": {"actual_external_ip":"174.aaa.bbb.ccc""actual_external_ipv6": "status": "status": MultipleNatFound "natpmp_autoconfig". ("status"."'NotFound"]. "upnp_autoconfig": '"'server ip'"192.168.10.1"'found uprp'" true)
Describe your network setup
EasyConnect 02512 Modem. Roon core is Roon Nucleus Rev B. Araknis Network switches and Gigabit Router.
Thanks for reaching out to us about this issue. The ARC error message you shared suggests that your ISP may be using Carrier Grade NAT, which can cause the public IP address for your home network to change frequently. This can interfere with ARC’s ability to connect reliably.
One solution is to contact your ISP and request a static IP address for your connection. That should resolve the issue. Let us know if you need any help with that process!
Thanks for your help Daniel. I have a couple of things to add before I contact my ISP for a static IP address.
I noted in my inquiry to you that Bluesound was working and stable after deleting the app and starting again. Bluesound is unstable again just like Roon. Does this further support your suggestion to get a static IP address?
Once I get a static IP address how do I go about resetting Roon, Bluesound and Roon ARC? Do I delete the three apps on my iPhone and iPad and then reinstall the apps?
Wayne
No, reinstalling shouldn’t be necessary. A simple restart of your router and affected devices (your Roon Core and mobile devices) should be sufficient after your ISP assigns the static IP.
It’s possible; intermittent instability across multiple devices can point to a deeper network issue. In that situation a static IP address can help. That said, I can’t speak with certainty about Bluesound’s behavior, since it has its own networking stack and variables. Still, if both systems are experiencing trouble, stabilizing the network with a static IP is a reasonable step forward.
Unfortunately my ISP only provides a static IP to business customers. This would be extremely expensive and would also impact my other services for wifi, phone and tv very detrimentally. How would you suggest we go from here?
The other option you can consider is using Tailscale, which creates a secure connection between your Roon server and ARC devices. This can often bypass the challenges introduced by Carrier Grade NAT or dynamic IPs from your ISP.
We’ve written this article to guide you through setting up Tailscale on macOS with RoonServer. If you’d prefer this method instead of requesting a static IP address, it’s a solid alternative that many users have had success with.
Let us know if you need help during the setup — we’re happy to assist!
I think that my first need before dealing with ARC is to resolve the problem of Roon cycling from working - to trying to connect with nucleus - to not working - to working - to trying to connect with nucleus - to not working …This endless cycling makes it very difficult to try and fix anything when the system hangs up most of the time. During the endless cycling the music will continue to play but the access to any Roon functionality remains locked.
Once we can get Roon working properly again we could tackle Roon ARC.
Thanks for your patience. I was able to retrieve diagnostics from your RoonServer, and I’m seeing multiple instances where the Nucleus appears unable to reach your network. Based on this, I’m beginning to suspect a potential hardware issue with the Nucleus’ Ethernet port.
To help confirm this, the next time your remotes can’t connect to the Nucleus, could you please check your router settings and see if the Nucleus still appears as a connected device? That will give us a better idea of what’s happening behind the scenes.
Hi Daniel. Not sure what you did but I actually had Roon working normally for a short time. But it went looking for the network again and became unfunctional.
I checked the network and didn’t find nucleus. But when I went back a few minutes later this is what I saw:
Based on the diagnostic data from your account, it appears that your network is segmented into two separate subnets: 192.168.40.0/24 and 10.0.0.0/24. This kind of setup can interfere with Roon’s ability to connect properly across devices.
Could you please provide more details about your network configuration? Specifically, let us know if there are any routes set up between these subnets, and whether any protocols are enabled to allow multicast traffic to pass between them.
