Roon arc stopped connecting

Roon Core Machine

Nuc 7i3BNH

I believe it has: 16GB ram and 64 GB sto

Networking Gear & Setup Details

Netgear GS108

Which is connected

archer tp link ax3000

The ax50 is connected to an ATT BGW320-500. This is only used as a modem with ip passthrough turned on.

Connected Audio Devices

Oppo udp203, ifi zen streamer are hardwired to the nether switch. I have an aural Aries le connect by wifi.

I also have an iPad and iPhone that connect through wifi.

Number of Tracks in Library

15376

Description of Issue

Friday, roon arc was working. Sunday it stopped. I made no changes to anything. Roon produced the following message:

{
“ipv4_connectivity”: {“status”:“NetworkError”,“status_code”:504,“error”:“error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined”},
“external_ip”: {“actual_external_ip”:“69.aaa.bbb.ccc”,“actual_external_ipv6”:“null”,“router_external_ip”:“192.168.48.2”},
“status”: “status”: MultipleNatFound
,
“natpmp_autoconfig”: {“server_ip”:“192.168.0.1”,“found_natpmp”:true},
“upnp_autoconfig”: {“server_ip”:“192.168.0.1”,“found_upnp”:true}
}

There might have been a roon update.

I’ve had ARC stop connecting a few times. Each time I just rebooted my Roon Server and the ARC device. Works every time thus far. If this doesn’t get you going try rebooting your modem as well.

I did all of those things.

But your ISP might have.

This can either be at the local-network level (commonly as a result of two routers), or at the level of your service provider (in the form of carrier-grade NAT).

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.

More specifically, you can pass along the following questions:

  • Have you implemented carrier-grade NAT for my account level?
  • Have you fully implemented IPv6, or do you have IPv4 addresses available?
  • Can I request a static IPv4 address to support port forwarding?
  • Are there any ports you have reserved at the ISP level I should be aware of?

If you’re unable to locate an existing solution in our ARC: Port Forwarding Resources subcategory, please reach out to the Roon support team and include the following information:

  1. What is the make and model of your modem and router?
  2. Do you have any additional network hardware, like additional routers or managed switches?
  3. Who is your internet service provider and what is your geographic region?
  4. Is your Modem configured in Bridge Mode so that it operates only as a modem or do you have the ports forwarded on both?
1 Like

well, never mind. We had a scheduled power outage today (to install a battery backup system). This shut down everything: the nas drive, the nuc/rock, the network switch, the router, and the modem. When everything rebooted Roon arc worked. Although it took awhile to connect. It would be nice to know what happened and what magical sequence of events brought it back. I did reboot the router, modem, and nuc without arc coming back to life.

1 Like

Hi @Robert_Lesser,

We’ve reviewed diagnostics from the affected time period with the technical support team. Here’s what we learned:

  1. On the day of your original post, Roon ARC experienced a timeout during a routine authorization request to your Roon Server.

  2. Subsequent attempts to reauthorize the session failed because ARC could no longer contact the Roon Server.

  3. ARC regained connection to the Roon Server several days later, although with a different geolocated IP address.

Were you traveling when you experienced this issue?

It’s curious that your ARC diagnostics report multipleNAT above, but you normally can connect. If you haven’t added a second router to this setup, it’s possible that your provider has implemented CG-NAT on your account. Are you using a VPN or proxy server on your network?

The network outage might have reset DHCP settings, network security settings, or UPnP, all of which might play a role here. Please let us know if issues return.

First, how does roon look at diagnostics on my system? For #3 I am not sure if ARC had a different IP or if the roon server did. I don’t know what CG-NAT is or how to check for it. I am not using a VPN and I don’t know if I am using a proxy server. I am also under the impression that I fixed the multiple NAT problem as that message went away months ago and the fix I implemented allowed ARC to work. I do sometimes start ARC while in my driveway, which means it can still connect through my router.

This topic was automatically closed 45 days after the last reply. New replies are no longer allowed.