I recently installed Roon ARC: worked perfectly even from abroad after port forwarding, now suddenly I get this message { "ipv4_connectivity": {"status":"NetworkError","status_code":502,"error":"error: Error: connect ECONNREFUSED 86.aaa.bbb.ccc:55002, response code: undefined, body: undefined"}, "ipv6_connectivity": {"status":"NetworkError","status_code":504,"error":"error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined"}, "external_ip": {"actual_external_ip":"86.aaa.bbb.ccc","actual_external_ipv6":"2a02:ddd:eee:fff:ggg:hhh:iii:jjj","router_external_ip":"null"}, "natpmp_autoconfig": {"status":"NotFound"}, "upnp_autoconfig": {"server_ip":"192.168.2.254","found_upnp":true,"error":"Did not find UPnP service with WANIPConnection on network"} } I have restarted my modem/router and Roon core: no effect
Could you give details of your network please? It may help understand what is going on.
How is you Roon server connected to your network?
Ethernet direct to ISP router
Ethernet to MESH Wifi Access point
Wifi to ISP router
Wifi to MESH access point.
The “Did not find UPnP service with WANIPConnection on network” would seem to indicate that you have connected a router to you network and then you have connected your Roon Server to this second router. The uPnP request is then being handled by the second router which does not have an internet connection.
If this is the case, the solution would be to put the second router into access point mode so that it does not offer routing services (including uPnP).
Could you also supply the LAN side (192.168.?.?) ip address of your router (as displayed on its web status pages) and of your Roon server (as displayed on the Roon → Settings ->ARC settings page). This will likely tell us more about the configuration (correct or otherwise) of you network.
If everything is correctly configured, the ISP router should be the one on 192.168.2.254 (as seen in the diagnostic text originally posted) and your Roon server should have an ip address in the range 192.168.2.1 to 192.168.2.253.
Note: There is no security risk to publishing these ip addresses because addresses in the range 192.168.0.0 to 192.168.255.255 are non-routable and so can’t be used outside of your network.
OK. Both devices are on the same subnet so this looks good.
If you are certain that the tp-link DECO is in access point mode as described here:
Then I would, as @AMT suggested, try disabling uPnP in the ISP router and configure an manual port forwarding rule to forward port 55002 to ip address 192.168.2.13.
It might be a good idea, at the same time to use a DHCP address reservation to make sure that the 192.168.2.13 address is always associated with the Roon server so that the port forwarding rule will not break due to a change in the Roon server ip address.
If the manual port forwarding does not work, then it is almost certain to a CG-NAT issue as described by @AMT above.
OK, this is quite beyond my level of knowledge, but what I especially do not understand is that ARC quit without me changing any settings that previously worked perfectly: well: any ideas on this?
It quite possibly could be your ISP provider changing things in the background. I would call your ISP and verify that you are NOT on a CGNAT connection. They may have moved you to one without telling you. ISPs do things like that all the time, Change things in the background and only take care of those who notice and complain.
The experience of users on this forum backs @Rugby’s assumption. We haven’t made any changes to the port forwarding component of ARC or RoonServer, so if the variables in your own network remain constant, it’s most likely an implementation change on the part of your ISP. CG-NAT rollout is surprisingly common as carriers navigate the landscape of IPv4 address allocation and acquire new use rights for fibre lines, etc.