Port Forwarding Error with ECONNREFUSED (ref#R5DU6I)

Support ARC: Port Forwarding Help
1

Network Setup

· My only router was provided by my ISP

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

I have set port forwarding manually but still get this message:{
"ipv6_connectivity": {"status":"NetworkError","status_code":502,"error":"error: Error: connect ECONNREFUSED ::1:55002, response code: undefined, body: undefined"},
"ipv4_connectivity": {"status":"NetworkError","status_code":502,"error":"error: Error: connect ECONNREFUSED 84.bbb.ccc.ddd:55002, response code: undefined, body: undefined"},
"external_ip": {"actual_external_ip":"84.bbb.ccc.ddd","actual_external_ipv6":"0000:aaa:aaa:aaa:aaa:aaa:aaa:aaa","router_external_ip":"null"},
"natpmp_autoconfig": {"status":"NotFound"},
"upnp_autoconfig": {"status":"NotFound"}
}

Describe your network setup

{
"ipv6_connectivity": {"status":"NetworkError","status_code":502,"error":"error: Error: connect ECONNREFUSED ::1:55002, response code: undefined, body: undefined"},
"ipv4_connectivity": {"status":"NetworkError","status_code":502,"error":"error: Error: connect ECONNREFUSED 84.bbb.ccc.ddd:55002, response code: undefined, body: undefined"},
"external_ip": {"actual_external_ip":"84.bbb.ccc.ddd","actual_external_ipv6":"0000:aaa:aaa:aaa:aaa:aaa:aaa:aaa","router_external_ip":"null"},
"natpmp_autoconfig": {"status":"NotFound"},
"upnp_autoconfig": {"status":"NotFound"}
}
please help

2

You say you have turned uPnP and natPMP on - but the Roon Server is still reporting that it cannot find either a uPNP service or a natPMP service on the router to which it is connected.

This suggests that, maybe you have got two routers and you are turning uPnP/natPMP on on the wrong router.

If this is the cause, and you do have two routers (maybe the second is a part of a Mesh WiFi system), then uPnP/natPMP will not work anyway because they only provide a mechanism to configure port forwarding on the first router encountered by the client - in this case the Roon Server. Instead, you will have to configure manual port forwarding on both routers - on the router connected to your ISP service, forward TCP connections on the ARC port (55002) to the WAN side ip address of the second router. On the second router, forward TCP connections on the ARC port to the Roon Server ip address. This will work best if both the second router WAN side IP address and the Roon Server ip address do not change which can be done by configuring a DHCP address reservation on each router - On the ISP connected router configure an IP address reservation for the WAN side ip of the second router and on the second router, configure an IP address reservation for the Roon Server.

If this feels like too much work, you could try using Tailscale instead. The Roon help centre has and article on Tailscale use with linked installation instructions for the different Roon Server platforms. It can be found at:

Note: When using Tailscale, the connection status reported on the Roon → Settings → Roon ARC page is irrelevant because they only pertain to port forwarding.

2 Likes
3

I do have a switch and access points. But I didn’t consider it a router since it does not perform router actions. It merely transmits wifi signal.
But I will try your solution.
Thank you!

4

Hi @Marco_Santos,

@Wade_Oram’s response is quite thorough and worth considering.

There are (at least) two NAT layers in your network - two pieces of router-capable hardware are performing network address translation. There is the possibility that your ISP is also implementing, or will eventually implement, CG-NAT above your account.

Tailscale is the most robust workaround for these double-NAT scenarios. It’s invulnerable to ISP changes or topology rearrangements. Please let us know if you have any questions.