Overview
Roon ARC is designed to connect to your Core outside your home, allowing you to access your Roon library, playlists, favorites, and more while on-the-go. To do so, Roon relies on a mechanism called "port forwarding." Through the use of port forwarding, your Roon Core and network router work together to make your Roon library available in ARC.
Roon can configure port forwarding automatically using protocols known as UPnP (Universal Plug-and-Play) or NATPMP (NAT Port-Mapping Protocol). When you first launch Roon 2.0, the software will test if your router has these protocols enabled and accessible. In Settings -> Roon ARC, you will see the results of this port forwarding test.
If the automatic configuration fails, Roon will then display a warning in the Settings -> Roon ARC tab, as well as a diagnostic message showing what went wrong. While these diagnostic messages might appear highly technical, each one points to a specific network blockage that is preventing ARC from connecting.
The vast majority of these network blockages can be resolved with a few simple changes in your router settings.
Below, we've included the most common diagnostic error messages and the best steps to resolve each one.
More Common Errors
Multiple NAT error
Example diagnostic message:
- { “connectivity”: {“status”:“NetworkError”,“status_code”:504,“error”:“error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined”}, “external_ip”: {“actual_external_ip”:“100.37.159.105”,“router_external_ip”:“192.168.1.108”}, “status”: “status”: MultipleNatFound, “natpmp_autoconfig”: {“status”:“NotFound”}, “upnp_autoconfig”: {“server_ip”:“192.168.1.1”,“found_upnp”:true} }
Meaning:
The port forwarding diagnostics you’ve provided suggest there is a redundant layer of network address translation preventing port forwarding. This prevents ARC from recognizing the external IP address of your home network.
The second layer of NAT can either be at the local-network level (commonly as a result of two routers), or at the level of your service provider (called "carrier-grade" NAT, or CG-NAT).
Symptoms:
Diagnostics will contain the following snippets for this error:
connectivity: (Any Error)
status: MultipleNatFound
Solution:
If your setup involves an ISP-provided gateway (modem/router combination) and your own third-party router:
In the web administration interface of the ISP-provided gateway (modem/router combination), enable Bridge Mode or equivalent, where the ISP-provided gateway does not have DHCP routing enabled.
Alternatively, if you have already created a manual port forwarding rule in your 3rd-party router, you can add an additional rule to forward the port through the ISP/second router.
If you only have one router in your setup or your modem is already in Bridge mode, please take a look through our list of known router and internet service provider solutions, as other users may have already encountered the same situation: ISPs and Routers: List of Known Solutions and Workarounds.
You can reach out directly to your service provider to ask if they support port forwarding; this question will often enough to prompt them to explain whether or not the carrier-grade NAT they’ve implemented can function with ARC.
Additional Notes:
The MultipleNAT error is not reported unless UPnP or NATPMP is working. Since these protocols configure port forwarding automatically, once you've removed the cause of the MultipleNAT error, port forwarding should automatically configure in Settings -> Roon ARC.
Missing UPnP/NATPMP
Example diagnostic message:
- { “connectivity”: {“status”:“NetworkError”,“status_code”:504,“error”:“error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined”}, “external_ip”: {“actual_external_ip”:“xxx.xx.xxx.xxx”,“router_external_ip”:null}, “natpmp_autoconfig”: {“status”:“NotFound”}, “upnp_autoconfig”: {“status”:“NotFound”} }
Meaning:
The protocols that configure port forwarding automatically are either not available or have failed. UPnP and NATPMP are not functioning in your router as Roon expects.
Symptoms:
Diagnostics will contain the following snippets for this error:
connectivity: (Any Error)
"status":"NotFound" in both "upnp_autoconfig" lines
Solution:
Additional Notes:
This error often results from VPNs interfering with UPnP and NATPMP.
Port mapping conflict
Example diagnostic message:
- { “connectivity”: {“status”:“NetworkError”,“status_code”:502,“error”:“error: Error: connect EHOSTUNREACH 73.143.156.12:50002, response code: undefined, body: undefined”}, “external_ip”: {“actual_external_ip”:“73.143.156.12”,“router_external_ip”:null}, “natpmp_autoconfig”: {“server_ip”:“192.168.1.1”,“found_natpmp”:true}, “upnp_autoconfig”: {“server_ip”:“192.168.1.1”,“found_upnp”:true,“error”:“<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/\” s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/\“><s:Body><s:Fault>s:ClientUPnPError<UPnPError xmlns="urn:schemas-upnp-org:control-1-0">718ConflictInMappingEntry</s:Fault></s:Body></s:Envelope>”} }
Meaning:
The error is saying that another program or app is using the same port that Roon is trying to use. The most common culprits are gaming setups that have already enabled port forwarding, routers that have reserved certain port ranges for their own processes, or a second Roon Core on the same network.
Symptoms:
connectivity: (any error)
"upnp_autoconfig" diagnostics line contains "ConflictInMappingEntry"
Solution:
- Try finding and closing those programs using the same port.
- Try changing the port connection settings for Roon by adding 1 to the previous port setting.
- For example, change the port from Port: 55000 to Port: 55001.
Additional Notes:
This problem can be caused by another Roon Core using the same default setting, even if the Core is not the current active one in use. If you've recently migrated your Core, make sure you fully uninstalled Roon on the old device.
Less Common Errors
Miscellaneous UPnP error
Example diagnostic messages:
{ “connectivity”: {“status”:“NetworkError”,“status_code”:504,“error”:“error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined”}, “external_ip”: {“actual_external_ip”:“94.XXX.XXX.36”,“router_external_ip”:null}, “natpmp_autoconfig”: {“status”:“NotFound”}, “upnp_autoconfig”: {“server_ip”:“192.168.50.1”,“found_upnp”:true,“error”:“doaction request return statuscode: ConnectFailure”} }
OR
- { “connectivity”: {“status”:“NetworkError”,“status_code”:504,“error”:“error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined”}, “external_ip”: {“actual_external_ip”:“73.125.39.218”,“router_external_ip”:null}, “natpmp_autoconfig”: {“status”:“NotFound”}, “upnp_autoconfig”: {“server_ip”:“192.168.1.1”,“found_upnp”:true,“error”:“<s:Envelope xmlns:s=“[http://schemas.xmlsoap.org/soap/envelope/\](http://schemas.xmlsoap.org/soap/envelope/\)” s:encodingStyle=”[http://schemas.xmlsoap.org/soap/encoding/\](http://schemas.xmlsoap.org/soap/encoding/\)“><s:Body><s:Fault>s:ClientUPnPError501ActionFailed</s:Fault></s:Body></s:Envelope>”} }
Meaning:
This error indicates UPnP is available on the router but is failing for reasons not reported by the router or identified by Roon. In most cases, this means a firewall, VPN, or security software is interfering with UPnP.
Symptoms:
connectivity: (any error)
upnp_autoconfig error that does not contain “ConflictInMappingEntry”
- Restart your network hardware and update router firmware.
- Try to set up manual port forwarding in your router.
- Make sure the IP/Port matches in any port forwarding rule you create.
- Toggle UPnP on/off in your router settings before attempting to autoconfigure again in Settings -> Roon ARC.
- Double-check to make sure you don't have any VPNs, Firewalls, or other network filtering software blocking Roon.
Additional Notes:
Routers with outdated firmware will oftentimes not allow UPnP to run until the firmware has been updated. Similarly, certain VPN or proxy server configurations will cause this message. This message will also appear when enterprise-grade networks have certain filtering in place or are blocking UPnP despite it being enabled on the upstream router.
Outgoing timeout
Example diagnostic message:
- { “connectivity”: {“status”:“NetworkTimeout”,“status_code”:998,“error”:“”}, “external_ip”: {“actual_external_ip”:“107.77.203.219”,“router_external_ip”:null}, “natpmp_autoconfig”: {“status”:“NotFound”}, “upnp_autoconfig”: {“status”:“NotFound”} }
Meaning:
This error indicates Roon is timing out when attempting to reach Roon's servers, not ARC. This is not a port forwarding failure, but rather a broader problem with your Roon Core's upstream connection. Users who experience this error code will more than likely have underlying network problems that also affect Roon outside of ARC.
Symptoms:
connectivity: “status”:“NetworkTimeout”,“status_code”:998
Solution:
- Verify your Core is not on a separate subnet.
- If your Core is connected via WiFi, try an ethernet connection directly to the upstream router.
- List Roon as an exception in any antivirus software or network firewalls on your Core machine.
- We recommend reviewing our Networking Best Practices since this error indicates Roon is struggling on your local network.
UPnP Service not found
Example diagnostic message:
- { “connectivity”: {“status”:“NetworkError”,“status_code”:502,“error”:“error: Error: connect ECONNREFUSED XXX.XXX.XXX.XXX:55002, response code: undefined, body: undefined”}, “external_ip”: {“actual_external_ip”:“XXX.XXX.XXX.XXX”,“router_external_ip”:null}, “natpmp_autoconfig”: {“status”:“NotFound”}, “upnp_autoconfig”: {“server_ip”:“XXX.XXX.XXX.XXX”,“found_upnp”:true,“error”:“Did not find UPnP service with WANIPConnection on network”} }
Meaning:
Your router is advertising support for UPnP in general but not for the specific UPnP service that is used to configure port forwarding.
Symptoms:
connectivity: (any error)
upnp_autoconfig line contains “Did not find UPnP service with WANIPConnection on network”
Solution:
This is most commonly a simple miscommunication within the UPnP protocol between the router and your Core.
- Toggle UPnP on/off in your router settings before attempting to autoconfigure again in Settings -> Roon ARC.
- Try to set up manual port forwarding in your router.
- Make sure the IP/Port matches in any port forwarding rule you create.
- Restart your router and network hardware.
- Update any outdated network firmware to verify you have the latest iteration of UPnP.
Additional Notes:
The most likely explanation is that there is a setting to enable UPnP port forwarding specifically in the router somewhere. Note, outdated router firmware often triggers this message.
Generic Error (unknownerror / undefined)
Example diagnostic message:
- { “connectivity”: {“status”:“NetworkError”,“status_code”:502,“error”:“error: Error: connect EHOSTUNREACH XXX.XXX.XXX.XXX:55002, response code: undefined, body: undefined”}, “external_ip”: {“actual_external_ip”:“94.XXX.XXX.36”,“router_external_ip”:null}, “natpmp_autoconfig”: {“status”:“NotFound”}, “upnp_autoconfig”: {“status”:“NotFound”} }
Meaning:
This message indicates that Roon was both unable to reach ARC and unable to determine what went wrong. This is a rare error and usually indicates severe filtering of your upstream and downstream connection or a Multiple NAT layer that Roon failed to detect. For certain internet service providers, carrier-grade NAT (CG-NAT) can present this message.
Symptoms:
connectivity: (Any error that is not “status_code”:998)
no other error state above applies
Solution:
- Toggle UPnP on/off in your router settings before attempting to autoconfigure again in Settings -> Roon ARC.
- If your Core is hardwired to an access point or managed switch, try connecting it directly to your upstream router before attempting to autoconfigure again in Settings -> Roon ARC.
- Restart your network hardware and update router firmware.
- If you have an ISP-provided modem/router or gateway, place it in mode (see MultipleNAT above).
- Try to set up manual port forwarding in your router.
- Make sure the IP/Port matches in any port forwarding rule you create.
What If I Need More Help?
If the troubleshooting steps above are not helpful, the Roon Team and Roon ARC user community are standing by to assist on Roon Community. You'll need to have some basic information ready about your network hardware and settings in order for the Community to provide the most expedited and efficient support.
2. If you don't see a thread applicable to your situation, please enter our
Technical Support troubleshooting module. You can use the module to create a #support thread on Community if your issue remains unresolved.
3. You will be prompted to provide details on your ARC mobile device, RoonServer, as well as any port forwarding diagnostic messages from Settings -> Roon ARC. Please share as much technical detail and context as possible within the form.