· -ROCK won't connect to ARC with/without Tailscale on Starlink-
I'm having issues setting up ARC with ROCK. I'm on Starlink but have bridged their modem to an Asus AI Mesh network, with my ROCK wired into the core router. Even with Tailscale logged in on the ROCK, I'm getting unusual multiple NAT errors and external connection issues. Here's one example:
UPNP is turned on, as is NAT, so I'm unsure why it reports that neither are active.
The weirdest thing is I can stream Qobuz via ARC outside my home, but can't stream my personal library unless I download it all first and go to offline mode.
If I set up port forwarding in the ASUS console (which used to work on other ISPs), I get even weirder issues, with Roon throwing an error on ARC setup that has an empty diagnostics data report.
I realize my ROCK hardware config is technically unsupported, but I've read of many other Roon users who've installed and run ROCK just fine on AMD chipsets.
Tell us about your home network
· ISP: Starlink Residential, 4th gen dish, 3rd gen modem (bridged with router unused) Routers - ASUS AI Mesh network (most recent WRT firmware). Primary router - GS-BE12000 Additional nodes (not used for Roon) - GT-AX11000 Pro, RT-BE3600
Roon Core: ROCK, wired to primary router. System hardware = Framework (standalone 13" mainboard) AMD Ryzen 5 7640 Roon OS Version 2.1 (build 271) production
AceRimmer
("I’m not just a hero; I’m a legend!")
2
Using Tailscale will still give an Arc error inside of Roon.
But the question is outside of throwing the error does it actually work?
I use Tailscale and get the error but it just works.
Roon is configured on my home server, which is also using Tailscale. My router has UPnP enabled and the port 55000 open, so does the firewall on that machine. Roon confirms that ARC is able to run on port 55000; ARC works when I’m on home WiFi or when I have Tailscale enabled, but not when I’m on 5G outside the home. This just cropped up on me.
Using Tailscale, Arc only halfway works outside my home. I can stream Qobuz through Arc, but my personal library isn’t reachable.
It would be helpful if it were added to the ROCK or Arc documentation that Roon will still show an error even when Tailscale works. That has sent me down false trails before.
To summarize what’s already been stated, the port test in Roon Settings → ARC only pings the downstream connection through the open port to ensure authenticated Roon traffic can use the port forwarding assignment. It won’t actually ping the downstream connection to the phone. You’re correct that the port test won’t correctly indicate when a separate NAT traversal pathway has been set up (like Tailscale), since it only checks the port forwarding stack. The team has work in the pipeline to overhaul this confusing facet of the interface.
As for why the port test returns an empty diagnostic when you disable Tailscale: logs seem to show the port test timing out intermittently before it can return the expected multipleNAT. The port mapping process fails validation. This isn’t uncommon with Starlink’s CG-NAT implementation, which behaves a little less predictably than other ISPs.
When you experience poor connectivity with Tailscale in ARC outside your home, do you have a strong cellular signal? What do you see in ARC Settings under the cloud/server connectivity indicators? If you can share the name of a track that was playing or an approximate timestamp of a poor connection event, we can pinpoint the event in logs.