Nucleus.
iPhone 13 Pro Max running iOS 16.3.1.
Nucleus connected via ethernet to Xfinity Gateway router.
NAD M33 amp hardwired to router.
About 14,000 tracks and Qobuz
Up until today, Roon and my Nucleus have been working fine. Now, I cannot Roon cannot locate my core.
Roon app states LOOKNG FOR ROON CORE, but cannot locate it.
Can you connect to the Nucleus by starting a web browser (Safari) on your iPhone (while it is connected to your home wifi) and going to the admin web interface like this?
Typing in the IP Address of the RoonOS Device in a Web Browser
Typing the hostname, http://nucleus , or http://nucleusplus
Typing the .local suffix for the device, http://nucleus.local , or http://nucleusplus.local
If not, what is the exact error message in the browser?
Hey @Tim_Keough,
Following up on this thread, are you still having issues? I was able to pull your account up and all looks well on my end.
Let me know! 
Yes. Still having ARC issues. Before it was only when using CarPlay (could not load albums, only playlists, and album art only showed last album played at home), now it will not connect remotely at all. It is showing ROON ARC WAS UNABLE TO SECURELY ACCESS YOUR ROON CORE.
And @benjamin this continues in this pleasant thread:
https://community.roonlabs.com/t/roon-arc-issues-continue/238016?u=suedkiez
I run Roon Nucleus and have a MacBook Pro on OS VENTURA
NUCLEUS CONNECTED VIA ETHERNET. XFINITY GATEWAY. NO VPN
NUCLEUS STREAMING TO NAD M33 (ROON READY)
ABOUT 14,000 TRACKS
I HAVE HAD CONSTANT ISSUES WITH ARC. I NOW CANNOT CONNECT OUTSIDE OF MY NETWORK, AND ROON STATES ARC CANNOT ACCESS THE CORE. IT WORKED FORA WHILE, AND NOW CANNOT CONNECT. WHEN I WAS ABLE TO CONNECT REMOTELY, IT WOULD NOT WORK WITH CARPLAY. I COULD ONLY SELECT PLAYLISTS. ALBUMS AND SONGS WOULD NOT LOAD. ALSO, ALBUM ART WOULD EITHER NOT SHOW, OR THE SAME ALBUM COVER WOULD SHOW FOR ALL SONGS.I HAVE REBOOTED THE ROUTER, THE NUCLEUS, AND STILL CANNOT CONNECT
What does the arc tab in roon server settings show
today it states ARC cannot connect to the CORE. It had connected before, but now is not connecting.
What exactly is the error message in Roon > Settings > Roon ARC, not in the ARC app
Hi. It is showing ROON ARC WAS UNABLE TO SECURELY ACCESS YOUR ROON CORE.
There should be detailed diagnostics data in the box on the right with a copy button next to it. Click the button to copy the text and paste it here
And by the way we can all read your posts EVEN WITHOUT WRITING IN ANNOYING CAPS ALL THE TIME
{
“ipv6_connectivity”: {“status”:“NetworkError”,“status_code”:504,“error”:“error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined”},
“ipv4_connectivity”: {“status”:“NetworkError”,“status_code”:504,“error”:“error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined”},
“external_ip”: {“actual_external_ip”:“73.hhh.iii.jjj”,“actual_external_ipv6”:“2601:aaa:bbb:ccc:ddd:eee:fff:ggg”,“router_external_ip”:“null”},
“natpmp_autoconfig”: {“status”:“NotFound”},
“upnp_autoconfig”: {“status”:“NotFound”}
}
Thanks. It looks like maybe UPnP stopped working on your router. ARC worked for you previously, right? And am I correct to assume that it was auto configured previously, i.e, you didn’t set up manual port forwarding rules?
If so, did you try rebooting your router for starters?
Hi. Yes, I did not make any manual adjustments to the router (which is fairly new from Xfinity). Unfortunately, I only know enough to be dangerous with the router. Yes, I have tried rebooting the router, as well as Roon Core. I also deleted ARC and reinstalled.
Hm, OK, was worth trying 
I am a bit surprised by this “ipv6_connectivity” in the error message. Searching the forum for this, there are only 7 other occurrences where users posted this text from the ARC error message.
Some of these occurrences are from users testing the new ARC IPv6 functionality in the Early Access test version of ARC. You aren’t using Early Access, are you?
Most other occurrences are from users whose ISPs use CG-NAT to provide limited IPv4 addresses while their network is essentially based on IPv6. The regular (production, non-Early Access) version of ARC does not work in this configuration, and this is what the new version in Early Access is supposed to address.
It’s not impossible that something changed on your ISP’s side and they switched to a CG-NAT configuration some time after your ARC worked. We have seen it happen before.
Who is your ISP?
Do you know if they promised a standard IPv4 address to you? Asking because if they did, then most likely they didn’t switch it around to CG-NAT (and you would have to talk to the ISP if they did). If you have a regular residential ISP account, most don’t come with such promises and it’s at least possible that the ISP is in the process of rolling out IPv6 with CG-NAT and they happened to do this for your account.
This topic was automatically closed 45 days after the last reply. New replies are no longer allowed.
