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
I have moved my Roon Core from my Qnap Nas to a Nucleus One and Roon arc no longer works.
I have the following error { "ipv6_connectivity": {"status":"NetworkError","status_code":504,"error":"error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined"}, "ipv4_connectivity": {"status":"NetworkTimeout","status_code":998,"error":""}, "external_ip": {"actual_external_ip":"94.hhh.iii.jjj","actual_external_ipv6":"2a02:aaa:bbb:ccc:ddd:eee:fff:ggg","router_external_ip":"null"}, "natpmp_autoconfig": {"status":"NotFound"}, "upnp_autoconfig": {"status":"NotFound"} }
I have a sky hub but the WiFi is handled by an eero mesh which is in bridge mode.
Describe your network setup
Sky Standard sky fibre hub Ethernet linked to eero mesh Nucleus one plugged in via Ethernet to eero.
The diagnostic snippet you’ve shared indicates that RoonServer didn’t find a UPnP stack installed in the router. This is preventing port forwarding from automatically configuring on the network for the Nucleus One.
If you’d previously created a manual port forwarding rule in your router for the QNAP, you’ll need to edit that rule so it points to the IP address of the new Nucleus One. The rule should match the port number and IP address listed in Roon Settings → ARC when you’re connected to the Nucleus One in Roon.
An alternative, since you have a Nucleus One, is to use Tailscale instead of port forwarding. It’s often simpler than trying to configure manual rules. Please see here:
The Tailscale free plan includes up to 6 users and 100 devices - I strongly recommend reaching out to their support, as it’s highly uncommon to require a Pro-level Taiscale plan for a Roon ecosystem unless you already rely on Tailscale for a commercial-scale setup with the same email address.