Debian Linux, running Docker and Portainer., Xeon E-2146G, 16GB ram.
Networking Gear & Setup Details
Untangle (router/firewall), Ubiquiti switches, Ubiquiti WAPs. No VPN.
Connected Audio Devices
Chromecast, Sony SRSX77 (Airplay/Chromecast), Windows PC, Android Phone.
Number of Tracks in Library
5665 tracks.
Description of Issue
I’m having issues getting ARC to work.
When I go to the Roon ARC tab, it tests, then comes back with “Not ready”. Otherwise the system works great. I can connect locally with the regular Roon app on all my devices.
I’ve forwarded the 55000 port to the host machine, checked that Roon is set to listen on 55000. I also tested with a different port, but no luck.
I’m using the elgeeko1 image, in privileged mode, and network set to host.
The team would be happy to pull diagnostic reports from your account in the ARC framework and RoonServer to investigate the connection loss more closely, but we’d want to confirm this with you first.
In the meantime, I recommend augmenting or decreasing the port range assignment in Settings → ARC and any associated port forwarding rules by a few thousand. 55000 is sometimes reserved by ISPs or third-party software - try 60000 or 54000 briefly, just to see.
Not all implementations of carrier-grade NAT will trigger a multipleNAT line in the port diagnostic message. From experience with other users, staff and moderators here know Rogers has partially implemented CG-NAT on their residential tier. The age of your account and geographic location within Canada will often determine the implementation. It might be worth clarifying with Rogers whether they’'ve supplied a dedicated IP address to your account, or if you’re fully behind their translation.
I did option 1, privileged container and host network.
Yes that sounds good. Thank you.
I will try selecting other ports as you suggested. I did previously test with 55005, but had the same issue.
Also, no I don’t have a dedicated IP from Rogers.
Do you know what domain or IP Roon is contacting to check the ARC connection?
Great to hear! I’m going to mark your previous post as Solution, which will auto-close this thread in several days, giving some time to repost if the problem returns.
If functionality returned without intervention, then one possible culprit was another software program competing for the available port in your router settings that has since restarted and chosen a different port. If that’s the case, it’s possible you’ll encounter intermittent issues moving forward until we isolate what’s actually interfering. If the issue returns, please start a new topic thread and we’ll pick the investigation back up.
