Unable to stream tracks via Roon ARC despite library visibility and download capability (ref#BFP0XJ)

[Thomas_Fournier]

What’s happening?

· I'm having trouble with Roon ARC

What best describes your issue with ARC

· I can't log into ARC but I can log into Roon

How can we help?

· None of the above

Other options

· Other

Describe the issue

I am able to connect to my Roon server via ARC however I am unable to stream any of my tracks. My music library is shown in the app and I can download albums but can't stream. The server indicates that ARC is not ready.

Describe your network setup

Roon server: Mac mini M4, Gateway: Ubiquiti Dream Machine Special Edition, Switch: Ubiquiti USW Ultra, Router: TMobile 5G. Mac is connected via ethernet through the Ultra to the Dream Machine.

Ping results from Roon Server to Gateway: 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.370 ms

Traceroute to Roon server from iPhone on public network through Tailscale is 271 ms

[benjamin]

Hey @Thomas_Fournier,

Thanks for writing in and welcome to the community - we’re excited to have you here, but also apologize for it’s an issue thats prompted your first post.

From a recent Arc diagnostic, we’re seeing timeout failures, it looks like Arc is able to ping your Roon Server, but your server isn’t able to communicate back with Arc on your mobile device:

roon_mobile_apphello https://100.94.126.22:55000/mobile/1/api/
roon_mobile_apphello https://192.168.1.249:55000/mobile/1/api/ => unknownError (HttpError [HttpErrorType.connectTimeout]: )
roon_mobile_apphello https://192.168.1.124:55000/mobile/1/api/ => unknownError (HttpError [HttpErrorType.connectTimeout]: )

Are you attempting to use Arc through port forwarding or through Tailscale? If you’re using tailscale, you won’t want a specific port number in your Roon Settings>Roon Arc, you’ll want to set the number to 0. Here’s more info on Tailscale :

Tailscale Setup Instructions: MacOS RoonServer

As a simple step in troubleshooting as well, can you temporarily bypass your Dream Machine and connect your Mac running Roon Server directly to your primary TMobile router?

If you’re planning on using port forwarding for Arc, we’ll need to know the functionality of your network setup - is your Dream Machine acting as your primary router, or the TMobile device? If it’s a modem/router combo, you may need to set it to bridge mode.

We’ll be on standby for your reply, thank you!

[Thomas_Fournier]

Thanks for the quick reply Benjamin.

I’m currently trying to connect through Tailscale. I have it running on the Roon Server as well as my iPhone.

I’d prefer not to configure the Dream Machine in bridge mode since I’d lose a lot of the functionality the device is providing.

I’ll try zeroing out the port number as well as a direct connect to the TMobile modem and report back.

[connor]

Hi @Thomas_Fournier,

Sorry for the confusion. If you’re using Tailscale to connect, you won’t need to tinker with any of your LAN infrastructure or bridge any routers. The Tailscale NAT traversal should punch through a second active router’s NAT layer without issue.

However, you will need to ensure that the port assignment is set to 0 Settings → ARC, to prevent RoonServer from attempting to rely on the failed port forwarding that has been automatically configured.

If Tailscale is relying heavily on DERP or other routing servers for NAT traversal, the latency can increase. Try the following test - stream local library tracks with ARC oni your *home WiFi testing with Tailscale first active and then inactive. Is there any observable difference in speed?

Next, test with Tailscale + cellular data and compare that to home WiFi without Tailscale.

Is there any difference between tracks of different formats and qualities? Are you able to stream lower-quality tracks, for instance, but not high-res?

We’ll watch for your response.

[Thomas_Fournier]

Looks like updating the port assignment to 0 fixed the issue. Really appreciate the assistance!

Tom

[daniel]

Hi @Thomas_Fournier,
Great we’re glad you were able to figure that out! I’ll mark this thread as solved for you. It’ll remain open for a few more days in case there are any further issues.