· I use a single personal router not provided by my ISP
ARC Status
· ARC is *Not Ready*
Roon Error Code
· None of these are listed. It simply says "TIMEDOUT" or similar.
System or third-party *firewalls *or *antivirus software* can sometimes block RoonServer from reaching ARC.
· Try adding RoonServer and its associated processes to the whitelist of any firewalls or antivirus software you have installed, including the Windows system firewall, if applicable. [You can learn more about firewall exceptions with Roon here.](https://help.roonlabs.com/portal/en/kb/articles/firewall)
Has the status in Roon -> Settings -> ARC changed after adding exceptions in your firewalls and antivirus software for Roon? I don't have any system or third-party firewalls or antivirus software.
Have you successfully located and enabled the UPnP or NAT-PMP settings in your router's web UI?
· I've turned UPnP/ NAT-PMP on and ARC won't connect
Select the Diagnostic Keyword or Text String
· Something else
Don't give up yet.
· I'm stuck. I'd like to create a post to ask Roon Community for help.
Describe the issue
ARC status is "Not Ready", Error 504, tried all suggestions but no change. Using own modem and router. UPNP is enabled and manually set up port forwarding
Describe your network setup
ISP = Xfinity Roon Core running on QNAP NAS T-651 Router = Netgear Nightwawk X4S R7800 (I own) Modem = Netgear CM500 (I own) Logged into modem to look for NAT forwarding but didn't see anything like that (I don't think this modem can do it) Verified UPNP is enabled in Router. Tried turning it off and back on - no change Port 55000 in router was set up for port forwarding. When I hit "reset" in Roon app next to "listening port" it changed the port to 55002, so I manually created a port forward using TCP (not TCP/UDP) but no change. Note that TCP is not a choice under "Port Forwarding" so I had to manually create the forward. Here's the error from Roon app: { "ipv4_connectivity": {"status":"NetworkError","status_code":504,"error":"error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined"}, "external_ip": {"actual_external_ip":"73.aaa.bbb.ccc","actual_external_ipv6":"null","router_external_ip":"73.aaa.bbb.ccc"}, "natpmp_autoconfig": {"server_ip":"192.168.1.1","found_natpmp":true}, "upnp_autoconfig": {"server_ip":"192.168.1.1","found_upnp":true} }
Thanks for taking the time to write in and share your report!
It can sometimes cause conflicts when both UPnP and manual port forwarding are active - have you tested out disabling UPnP while still having your manual rule active?
Give this a try, reboot both your router and mobile device, and let me know if anything changes.
Thanks Benjamin,
No change. Still getting a “Not Ready” and the only thing that changed was the last line of the error dialog - upnp_autconfig is now “NotFound”
{
“ipv4_connectivity”: {“status”:“NetworkError”,“status_code”:504,“error”:“error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined”},
“external_ip”: {“actual_external_ip”:“73.aaa.bbb.ccc”,“actual_external_ipv6”:“null”,“router_external_ip”:“null”},
“natpmp_autoconfig”: {“server_ip”:“192.168.1.1”,“found_natpmp”:true},
“upnp_autoconfig”: {“status”:“NotFound”}
}
What else can I try? I’d really like to get it running directly on my NAS, and would prefer to avoid using Tailscale unless absolutely necessary. Thanks
Thanks for your post. Xfinity isn’t known to implement CG-NAT so this is likely a resolvable settings configuration issue in either the router or the QNAP.
Can you please try recreating the manual port forwarding rule, but applying these settings?
Format: TCP/UDP
Internal port: 56000 or something outside the 5500x range
External port: identical to internal port
IP address: copy from Roon Settings → ARC
Make sure you set an identical port number in Roon Settings as well.
I’d double-check that QFirewall isn’t restricting access inadvertently, for due diligence.
Thanks Connor,
I tried that and no change. But you did have the answer. I’m just not sure how to fix it.
I looked at my firewall settings on my NAS (which runs the ROON server) and I only allowed connections from the list of approved IP addresses.
The only address I have is that of my router with a subnet mask of 255.255.255.0
I thought that would be OK because all my external traffic comes through my router. But apparently not. When I changed it to “allow all connections” Roon reported ARC as “ready”. I’m pretty horrible at network stuff and it feels to me like a security risk leaving it as “allow all connections” so I have changed it back for now. Is there an IP address I can add to the list that’s associated with ROON ARC so this will work while still only allowing connections from the list?
Thanks very much.
-Paul
As long as your router firewall is engaged, then your main line of defense is intact. The key is to avoid making changes to the DMZ or firewall settings within the router (other than the port forwarding rule).
If you expose the NAS to all external traffic per the setting you tried, the router still polices the connection upstream, so it’s not an inherent security exposure.
Roon ARC connections are encryptedand require authentication. An outsider can’t just connect and control your NAS or access files. So, malicious actors or port scanners might see an open port associated with your WAN IP, but that port will only allow encrypted Roon traffic from your account to go in/out.
If you want an additional layer, try adding a new rule in the page you shared that only permits traffic through the port you’ve assigned in your manual port forwarding rule.
We’re reaching out to ask if you had any additional questions before this thread auto-closes.
My previous post addresses the specific security concern you raised in this thread, but we’re always happy to answer any other questions you might have.
Thanks Connor. I meant to update you on this, but got distracted. I just went ahead and allowed all connections. That fixed it. Thanks.
I have an unrelated question - not an issue, just a question. I’ll ask it here, but let me know if I should make a new ticket for it. I am running my ROON core on my NAS - it’s VERY convenient that way since the NAS is always on anyway. The NAS is on lower end of your minimum requirements per this page: https://help.roonlabs.com/portal/en/kb/articles/faq-what-are-the-minimum-requirements#Typical_Usage.
It’s a QNAP T-651 with a dual core Celeron, 16GB RAM and is running a RAID-5 volume across 6 disks. So it has plenty of RAM, the RAID read/write bandwidth should be very good, but the processor is bit less powerful than what you recommend. I have VERY rarely noticed issues streaming the music to my streamer - and really only when I am doing a big file copy, so I think the core is running well. However, when using the ROON app on my Mac Laptop (MacBook pro M1 with 32GB of RAM) that there is a little lag when scrolling. It’s most noticeable when scrolling through my Artist list or when I have selected an artist - the information has a little bit of hesitation when scrolling.
Is that most likely from the core running on the NAS or from the app running on my MacBook? I don’t know whether all the data and graphics are being sent from the ROON core or if my MacBook is gathering and displaying the data (images, names, information), etc. Is there a brief overview of what data the core is sending to the app and what data the app itself is collecting, manipulating and displaying? I am trying to decide if running the core on my NAS is good enough since it doesn’t seem to affect the music at all. Thanks
-Paul
Thanks Alex,
I appreciate the help. I am relieved to hear that it’s not my NAS and hope to see updates in the future to help smooth out the scrolling. But for now, it is certainly fine to work with it as-is. I don’t need any more help on this. Thanks
-Paul
