· Arc will not play Qobuz tracks. It plays my tracks in my library on the server and the Qobuz app plays perfectly fine over cellular network. My Tidal tracks play fine in Arc.
Tell us about your home network
· Deco 10 mesh network Roon server on Mac mini Qobuz service Tidal service
I uninstalled and reinstalled the app. Same problem. Qobuz tracks will not play on cellular network. On WiFi network I use the Roon app and everything works perfectly. Photo from one hour ago
From a Roon Server diagnostic report, one detail worth mentioning: it isn’t failing every single time. A few Qobuz tracks did play through completely in ARC, including “Stockholmsvy,” the same track showing the error in your screenshot, which played start to finish at 9:29am on Wednesday. So it’s intermittent rather than a hard block, which fits with something in the cellular path being the sticking point.
Two things would help us narrow this down:
1. Try ARC on WiFi. So far the comparison has been ARC on cellular against the Roon app on WiFi, two different apps on two different networks. If you connect your phone to WiFi and play a Qobuz track in ARC (not the Roon app), that tells us whether this is specific to cellular or specific to ARC.
2. Lower the streaming quality in ARC for cellular. In ARC, go to Settings, and set the cellular quality to something below “Original” “Balanced” or “Bandwidth Optimized” . That changes how the audio reaches your phone, and if Qobuz starts playing at the reduced setting, it confirms where the problem lives. Please try a few Qobuz tracks after changing it.
Let us know how both of those go and we’ll take it from there.
One unrelated thing we spotted while we were in there: your Deco isn’t successfully forwarding the IPv4 port for ARC, the UPnP setup is being rejected by the router, so ARC is currently reaching your server over IPv6 only. That isn’t what’s causing the Qobuz issue, but it’s worth sorting out separately since it can make ARC unreliable on networks that don’t offer IPv6. Happy to walk you through that once we’ve got the Qobuz side settled.
Thank you so much for your response. Here are the results.
ARC on WiFi works fine. Everything plays including what is in my library.
I lowered the streaming quality to CD Quality, Balanced, and Bandwidth Optimized and none of them worked. As you mentioned, Stockholmvy did play but nothing else after that. There are times when it will play one song from Qobuz but that is it. When it gets to the next Qobuz song in the list it doesn’t play. In addition, once it doesn’t play a Qobuz song, it will not play the Tidal songs or any other songs in the playlist.
Once we get Qobuz working over cellular I would like to have your help in forwarding IPv4 port on my Deco.
Thanks for running those tests, we pulled fresh server logs, which told us a lot.
A correction on the network side. Your Deco isn’t rejecting UPnP outright, it’s answering, but refusing to map port 55000 because something already holds a mapping on it. Also, the router answering UPnP sits at 192.168.y.254, which isn’t a typical Deco address, and the path out to the internet passes through several layers of private addressing, usually a sign your ISP uses carrier-grade NAT. If so, inbound IPv4 may not be possible on your line regardless of how the Deco is set up.
IPv6 is working, but your Mac mini’s IPv6 address changes every 24 hours. On a setup reachable only over IPv6, that’s a real source of instability.
The most useful test, two minutes:
On cellular only, standing at home, try one of the failing Qobuz tracks.
Then try the same tracks on a different WiFi network, a friend’s, or a hotspot from another phone.
Together those tell us whether the trigger is cellular specifically or being away from home generally, very different directions.
Alongside that, could you let us know:
Is the Deco your main router, or in access point / bridge mode? What’s at 192.168.y.254?
Is there an existing port forward or UPnP entry on port 55000? Removing it and restarting Roon Server should let Roon create its own. You can also change the port under Settings → Roon ARC.
Can you ask your ISP whether your line uses CGNAT?
Optional: if you’re comfortable in Terminal on the Mac mini, giving your server a stable IPv6 address is safe and reversible:
sudo sysctl -w net.inet6.ip6.use_tempaddr=0
Then restart the Mac mini. If you’d rather not, the tests above matter more.
· Qobuz songs will not play on Arc. I’ve reported this before and the issue was closed before resolution. I’m attaching screenshots of the previous post. The last suggestion was to try through a hotspot and another WiFi. Both worked fine but when I go back to Arc through cellular data either one Qobuz song plays then nothing plays or the first Qobuz song doesn’t play and the whole thing crashes.
mjw
(You want nice, supportive? Call a damn helpline.)
11
The original thread was closed because you didn’t respond for 1 week. If this happens, please flag the last post, select Something else, and ask the moderators to reopen the topic. Thank you.
Our apologies for the hassle. Long story short, the port forwarding issue should be quite simple to workaround, as it only concerns NAT traversal and there are backups. The Qobuz problem with cellular data might be more difficult to pin down, since the infrastructure involved isn’t Roon’s. Here’s what’s happening and what we can do to resolve it:
For some context, Roon and ARC communicate with Qobuz using the Qobuz API. The Qobuz app relies on direct communication with the Qobuz servers, as do browser players and certain other apps. This isn’t important other than that your phone OR your Roon Server machine will always be communicating with the Qobuz API when you’re streaming from Qobuz in Roon and ARC.
When ARC is using your home WiFi, your home Roon Server handles all the downloading and buffering from the Qobuz API as you stream. Once you switch to cellular data or use a WiFi network that isn’t yours, the phone itself contacts the Qobuz API and streams audio directly.
This means that your cell provider’s infrastructure has to be well aligned to reach the Qobuz API. The CDNs and infrastructural partners that provide the network pathways between Qobuz and your cell provider might impose restrictions on data transfer well upstream of your account, and high-quality files might start to buffer and then. The effect for you would be that a Qobuz track plays in ARC at first, then the next one fails. This is, unfortunately, not terribly uncommon, although it’s not common. We can likely explore workarounds, and since you mentioned ARC sometimes freezes or even crashes, we can absolutely help fix that.
To begin, who is your cellular provider? We don’t need to know specific account details or any technical information, and you’re welcome to share this information via PM to keep it private. Knowing the provider will help expedite our investigation.
As for port forwarding, the same question will also help us quickly resolve this problem and provide clear next steps. Who is your ISP, and do you have an ISP-provided gateway (modem/router combo) in addition to the Deco?
We’ll watch for your reply. Hopefully this helps illuminate where things stand.
No worries and apologies for long delay. My cellular data provider ISP is Fastweb. I have their Fastweb 7 modem to which I have my Deco mesh network connected. Hope that helps. Shout if you need more info.
To look at this from the phone’s side, we have turned on diagnostic logging for Roon ARC on your account. Please fully close and reopen Roon ARC on your phone and restart the Roon server multiple times, then, on cellular data, play the Qobuz tracks that fail until it stops playing. Please note the exact time (including your time zone). When you have done that, please reply here and keep Roon ARC open on your phone while you do, so we can retrieve the logs from our side.
We’re simply circling back on this to see if you’d be able to take the steps above that would send us the logs we need to take troubleshooting to the next step.
Please, then, test the failing Qobuz tracks on cellular data and note the exact time, including your time zone, so we can pull the logs from our side. L
Depending on when you are able to get back to us, this technical support request may close automatically soon.
If that happens and you still need us, please submit a reopen request (None of the above quite fits → Reopen a previous technical support request):