Network Connectivity Issues with RoonServer IPv4 (ref#N2V8D2)

Support ARC: Port Forwarding Help
1

Hi! What’s not quite right with Roon?

· Can’t reach my Server, remotes or ARC

Can’t connect to my Server, remotes or ARC

· Other ARC issues

Tell us what's going on

· {
"ipv4_connectivity": {"status":"NetworkError","status_code":504,"error":"error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined"},
"external_ip": {"actual_external_ip":"42.ggg.hhh.iii","actual_external_ipv6":"null","router_external_ip":"null"},
"natpmp_autoconfig": {"status":"NotFound"},
"upnp_autoconfig": {"server_ip":"192.168.50.1","found_upnp":true,"error":"doaction request return statuscode: UnknownError"},
"multinat_autoconfig": {"status":"Failed","error":"Unexpected Error - See Log"}
}

Tell us about your home network

· ASUS GS-BE18000

2

Hi @Tommy_Chan,

Thanks for sharing the ARC diagnostics — that helps clarify what’s going on.

From the results you posted, Roon is unable to establish IPv4 connectivity from outside your network, and automatic port forwarding is not succeeding. A few key points from the diagnostics:

  • IPv4 connectivity:
status: NetworkError (ETIMEDOUT / 504)

This indicates that inbound IPv4 connections to your network are timing out.

  • UPnP / NAT-PMP:
    • UPnP is detected, but returns an error
    • NAT-PMP is not available
    • Multi-NAT detection failed
  • External IP mismatch:
    Roon can see an external IPv4 address, but the router is not reporting one back. This often suggests an ISP-side limitation.

Taken together, this most commonly points to one of the following:

  • CGNAT (Carrier-Grade NAT) or similar ISP-level NAT
  • A router configuration that prevents inbound IPv4 connections
  • Port forwarding being blocked or unsupported on the WAN side

What we recommend checking next

  1. Confirm with your ISP whether your connection uses CGNAT or otherwise blocks inbound IPv4 traffic.
    If so, ARC cannot work with standard port forwarding.
  2. If your ISP can provide a public IPv4 address (sometimes as an add-on), that usually resolves this.
  3. Alternatively, you can use a VPN-based solution such as Tailscale, which bypasses the need for port forwarding entirely.

At this stage, the behavior you’re seeing is consistent with a network/ISP-side restriction.

Let us know what you find regarding CGNAT or if you’d like guidance setting up Tailscale — happy to help further.

3

Hi @Tommy_Chan,

Diagnostics indicate that you’re in a geographic region in which internet service providers are known to have imposed georestrictions and/or carrier-grade network address translation (CG-NAT).

This will not only limit RoonServer’s ability to automatically configure port forwarding, but it may also limit Roon’s ability to reach essential upstream services for login, metadata, and streaming service playback.

Do you use a consumer VPN with Roon? I suggest posting in Tinkering to see what users who share your internet service provider have done in the past to circumvent these infrastructural obstacles. Unfortunately, this is outside of Roon support’s ability to resolve.

4

We’re going to allow this thread to auto-close due to inactivity at this time.

If you have another issue with Roon or require further guidance or assistance with ARC, please let us know here. Thanks!