Cannot get Roon ARC working

[hallo_leo]

Roon Support Template

Roon Core Machine

Model	Synology DS1520+
CPU	Intel Celeron J4125 4-core 2.0 GHz
RAM	8 GB DDR4 non-ECC
OS	DSM 7
Roon Version	2.0 (1324)
Connection to LAN:	Ethernet

Networking Gear & Setup Details

Netgear D6200 Router

• Connecting via Ethernet: Roon Core on Synology
• Connecting wirelessly: Roon client as Audio Device on Mac Mini

Connected Audio Devices

Roon client as Audio Device on Mac Mini:

Model	Mac Mini
CPU	M2 Pro
RAM	16GB
OS	macOS 13.5.2
Roon Version	2.0 (1311)
Connection to LAN:	WiFi

Number of Tracks in Library

18000

Description of Issue -

What is the exact port forwarding error message you see in the Roon Settings → ARC tab?

When i do the test on the Roon ARC Settings page, I getthe following diagnositcs data:

{
"ipv4_connectivity": {"status":"NetworkError","status_code":502,"error":"error: Error: connect EHOSTUNREACH 58.aaa.bbb.ccc:55005, response code: undefined, body: undefined"},
"external_ip": {"actual_external_ip":"58.aaa.bbb.ccc","actual_external_ipv6":"null","router_external_ip":"null"},
"natpmp_autoconfig": {"status":"NotFound"},
"upnp_autoconfig": {"server_ip":"192.168.0.1","found_upnp":true,"error":"<s:Envelope xmlns:s=\"http://schemas.xmlsoap.org/soap/envelope/\" s:encodingStyle=\"http://schemas.xmlsoap.org/soap/encoding/\">\n<s:Body>\n<s:Fault>\n<faultcode>s:Client</faultcode>\n<faultstring>UPnPError</faultstring>\n<detail>\n<UPnPError xmlns=\"urn:schemas-upnp-org:control-1-0\">\n<errorCode>718</errorCode>\n<errorDescription>ConflictInMappingEntry</errorDescription>\n</UPnPError>\n</detail>\n</s:Fault>\n</s:Body>\n</s:Envelope>\n"}
}

It says sometghing with “not found”. – However, my internet is wroking and the LAN is working too: The Roon client on my Mac can connect to the Roon Server on the Synology NAS and play music beautifully…

[Wade_Oram]

The natpmp_autoconfig ‘not found’ is just saying that your router does not support (or is not configured to support)i the NATPMP method of automatic port forwarding.

You may have an option in your router to enable NATPMP - but you may not.

The next line - upnp_autoconfig - is reporting that the router is configured to provided upnp services for opening ports - however, it appears that it does not like the upnp request because the port being requested is already being forwarded to another device - "errorDescription>ConflictInMappingEntry
".

You should try using a different port for ARC. In Roon → Settings ARC set a different port number (typically in the range 1024 - 65535).

The default is 55000, so trying 60000 might be a good start.

If you can not get this to work with uPnP, you can, instead opt to create a manual port forwarding rule. However you will still have to resolve the issue that you appear to have two different devices that require port forwarding from the same port.

If you configure manual port forwarding, you will need to configure a rule with a name of your choice - but make it specific for the service - e.g. “RoonARC” -, the external port should be set to the port number configured in the above ARC settings page, the internal port should be left blank or set to the same value, and the destination ip address should be set to the ip address shown in your ARC settings page.

Manual port forwarding works best when you have configured your router’s DHCP server to reserve an ipaddress for the Roon Server so that it always uses the same ip address and thus you will not have to update the port forwarding rule in the future when the ip address changes (which can be a problem when away from home) which can happen after a router reboot.

A static ip address (outside the range of ip addresses managed by your router but still with in the same subnet) can also be used but this can cause complications if you later change ISP’s and a new supplied router uses a different sub net.

Roon has configuration help for port forwading at:

ARC Port Forwarding

And a troubleshooting guide at:

Port Forwarding Troubleshooting

[hallo_leo]

Thanks for looking into this, @Wade_Oram!

@Wade_Oram

it appears that it does not like the upnp request because the port being requested is already being forwarded to another device - "errorDescription>ConflictInMappingEntry

I had run the setup from the client on another machine, a few months earlier, but have now moved top a new Mac – and heer the Ronn ARC pane was saying “MNot ready” That’s why i ran the setup again.

Can this cause the port duplication? In that case, how can I switch off the old forwarding?

[Wade_Oram]

If you do not have any explicit port forwarding rules set on your router, then either:

• You have another Internet facing server using upnp to open the same port as Roon ARC is using.
• The upnp request from the second install is trying to open the same port as the first.

To fix the first issue you will need to change the port number used by ARC as I suggested above.

To fix the second issue, you could simply change the port number, or you could try turning off your router and then stopping Roon server on your Synology NAS. Then power up your router and then, when the router reboot is complete, restart Roon Server on the NAS.

There is nothing special about the 55000 port number used by default. It is just a port number chosen as a default because it is unlikely to be used by other network services. If it is used for another service, changing it has no operational, reliability or support implications.

There is no need to reinstall Roon Server to fix this.

[hallo_leo]

I had a look at my router and for UPnP it says the following:

192.168.0.16 is not a currently attached device. I guess when I manage to delete this line, things might get better. - But how can i delete this entry on the router (a Netgear D6200)?

You probably can’t tell me because this might be router specific, but I thought at least I can ask…

[Wade_Oram]

@hallo_leo

I had run the setup from the client on another machine, a few months earlier, but have now moved top a new Mac – and heer the Ronn ARC pane was saying “MNot ready” That’s why i ran the setup again.

The Roon installer on a Mac (or a Windows machine for that matter) installs two programs. Roon desktop client (just called Roon) and Roon Server. Since you use your Synology DiskStation as your Roon Server, you should not ever need to run Roon Server on the Mac.

Having installed Roon on the new Mac, the only ‘setup’ required is to run the Roon client and connect it to the Roon Server already running on the Diskstation. Everything else should have stayed the same. It certainly should not affect ARC connectivity (port forwarding). Re-runing setup will not do anything to fix the issue.

I’m guessing that that rule is left over from a previous uPnP configuration request. Has the ip address of your Synology diskstation changed recently? Such things can occaisionally happen when ip address allocation is left to DHCP.

The ARC error diagnostic that you posted mentions ‘ConflictInMappingEntry’. This is the cause of the issue. It is saying that it cannot honour the uPnP request to forward traffic because traffic for the specified port is already being forwarded to a different ip address. I’m assuming your Roon Server is configured to use port 55005 for ARC connectivity (in the Roon->Settings->ARC settings page as in the image I posted above). This would explain the conflict with the rule shown in your router screen shot.

I would start by rebooting your router - then wait for it to stabilise. Hopefully, this will clear out the previous port forwarding rules created by uPnP. The uPnP Portmap Table should, at this time, either be empty or it should show a new forwarding rule for the Roon Server with the correct ip address.

If Roon is still reporting a conflict in mapping entry, then restart your Roon Server. I believe that you can do this by stopping and then restarting the Roon Server service on the Synology - you should not have to do a full Synology reboot (although that would achieve the same result).

If you still have the same problem, and the 192.168.0.16 port 55005 forwarding rule has not gone away, then the easiest solution would be to change the port in Roon to avoid using 55005. Try using something like 60000.

As a matter of interest, could you post a screen shot of your Roon->Settings->General page showing the details like (Note: you should block out your email address as I have done before posting):

[hallo_leo]

Ok, firstly I managed to get the server configured for Roon ARC:

The trick was to fix the IP address of the Synology (the Roon Server) in my router and to reboot evrtything. Thanks heaps for your help!

Secondly, here the info from the General pane:

Quick PS for other people finding this

@Wade_Oram

I would start by rebooting your router - then wait for it to stabilise. Hopefully, this will clear out the previous port forwarding rules created by uPnP. The uPnP Portmap Table should, at this time, either be empty or it should show a new forwarding rule for the Roon Server with the correct ip address.

I guess that was the starting point which got things moving in the right direction!

[Wade_Oram]

OK. Good.

I can also see that you changed the ARC port from 55005 to 55002. This alone should have fixed the issue because it means that the port (55002) now being requested to be opened and forwarded to the Roon server does not conflict with the old rule (forwarding port 55005).

However, the router reboot should have cleared out the old rule anyway. What does your router’s uPnP portmap table (as posted in your post at Cannot get Roon ARC working - #7 by hallo_leo) look like now?

It should have just one entry forwarding port 55002 to the Synology hosted Roon Server at 192.168.0.10.

[hallo_leo]

@Wade_Oram

What does your router’s uPnP portmap table […] look like now? It should have just one entry forwarding port 55002 to the Synology hosted Roon Server at 192.168.0.10.

Yes, it does show exactly and only this:

So, the server seems to be ready, but now I have troubles with the Roon ARRC app on my phone. (I have opened a new thread for that.)

Anyway, thanks again for your very patient help with Roon Server, Router and Port Forwarding!