Unable to connect to Roon ARC (ref#V5B3C3)

Support
1

Network Setup

· Do you have a mesh network? (Google Mesh, Eeros, Ubiquiti, etc.)

ARC Status

· ARC is *Not Ready*

Roon Error Code

· “natpmp_autoconfig”: {“status”:“NotFound”}, “upnp_autoconfig”: {“status”:“NotFound”} }

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

Unable to connect to roonarc

Describe your network setup

Using TP Link deco, roon nucleus
Wired connection, tplink port extender
{
"ipv4_connectivity": {"status":"NetworkError","status_code":504,"error":"error code: 504"},
"external_ip": {"actual_external_ip":"156.aaa.bbb.ddd","actual_external_ipv6":"null","router_external_ip":"null"},
"status": "status": MultipleNatFound
,
"natpmp_autoconfig": {"status":"NotFound"},
"upnp_autoconfig": {"server_ip":"192.168.68.1","found_upnp":true},
"multinat_autoconfig": {"status":"Failed","error":"Unknown Error code"}
}
Please assist

2

Hi @Ismael_gopal1,

Thank you for your post. The diagnostic code you’ve shared indicates that Roon can’t reach ARC because there is more than one layer of network address translation.

This can either mean that you have a second router active somewhere in your network, or that your internet service provider has implemented CG-NAT.

If you don’t have a second router in your local network setup, then who is your internet service provider? We can check if they’re among the list of providers known to have implemented CG-NAT and suggest options.

Another option is to install Tailscale as a workaround to port forwarding.

3

Hi

My ISP is Axxess in South Africa

They have implemented CG-NAT

Would a static IP help?

4

Hello @Ismael_gopal1,

Yes, a static IP from your ISP will absolutely help, provided that it is a public-facing (routable) IP address.

Why a Public Static IP Fixes the Issue

The MultipleNatFound error and the CG-NAT implementation by Axxess essentially mean your home network is hidden behind a large "private" network shared with many other customers. Because of this, Roon ARC cannot "see" your Nucleus from the outside world.

By switching to a public static IP, Axxess gives your home network its own unique address on the open internet. This removes the CG-NAT layer and allows the port forwarding rules on your TP-Link Deco to work exactly as intended.

A Few Things to Check First:

  • Confirm with Axxess: Before you sign up, explicitly ask them if the static IP is a "Public Routable IP." Some providers offer "Static IPs" that are still trapped within their private CG-NAT network, which wouldn't solve the problem.
  • The Tailscale Alternative: If Axxess charges a significant monthly fee for a static IP, remember that the Tailscale solution mentioned by Connor is a free way to bypass CG-NAT entirely without needing any changes from your ISP.
If you do go ahead with the static IP, let us know once it is active, and we can help you verify the settings in your Roon ARC tab!
5

Hi

Confirmed static IP is public routable

Enabled

All up and running now

Thanks

6

Hello @Ismael_gopal1

Thank you for the update. We are glad to hear that you are back up and running again. Enjoy your music!