Cannot connect to ARC; UPnP is enabled

I’m not able to connect to Roon ARC. I have enabled UPnP, and this is the diagnostics readout I get:

{
“connectivity”: {“status”:“NetworkError”,“status_code”:504,“error”:“error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined”},
“natpmp_autoconfig”: {“status”:“NotFound”},
“upnp_autoconfig”: {“server_ip”:“192.168.1.1”,“found_upnp”:true}
}

Hi @Joe_Keller,

Sorry to hear you’ve encountered a snag out of the box. It sounds like you’re encountering a double NAT layer, usually caused by having a second router in your setup. Most often, this is resolved by accessing the web GUI of the upstream router (the modem/router combination) and enabling Bridge mode, or similar.

You can read more context here in our Help Center article: https://help.roonlabs.com/portal/en/kb/articles/arc-port-forwarding#Multiple_NAT

Please let me know if this helps illuminate the issue. If you continue to have problems, we’ll be watching for your response to ask some more specific questions about your network setup.

1 Like

Thanks! That ended up being the solution to my problem.

A post was split to a new topic: Multiple NAT issue

I am having the same issue too:
{
“connectivity”: {“status”:“NetworkError”,“status_code”:504,“error”:“error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined”},
“external_ip”: {“actual_external_ip”:“xx.xxx.xx.xxx”,“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/\” s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/\“>\n<s:Body>\n<s:Fault>\ns:Client\nUPnPError\n\n<UPnPError xmlns="urn:schemas-upnp-org:control-1-0">\n501\nPAL_UPNP_SOAP_E_ACTION_FAILED\n\n\n</s:Fault>\n</s:Body>\n</s:Envelope>\n”}
}

UPnP is enabled, I tried all suggestions, put my upstream router in bridge mode, enabled port forwarding for the specific IP, etc. Did not help.

A post was split to a new topic: 504 Port Forwarding Issue on Sagemcom F@st5260 router

I resolved this temporarily by using port forwarding on both my NAT layers (modem/router)

2 Likes