Roon Arc Not Ready Post-Database Recovery (ref#S0G6G4)

Support
1

Network Setup

· I use a single personal router not provided by my ISP

ARC Status

· ARC is *Not Ready*

Roon Error Code

· None of these are listed. It simply says "TIMEDOUT" or similar.

System or third-party *firewalls *or *antivirus software* can sometimes block RoonServer from reaching ARC.

·
Try adding RoonServer and its associated processes to the whitelist of any firewalls or antivirus software you have installed, including the Windows system firewall, if applicable.
[You can learn more about firewall exceptions with Roon here.](https://help.roonlabs.com/portal/en/kb/articles/firewall)

Has the status in Roon -> Settings -> ARC changed after adding exceptions in your firewalls and antivirus software for Roon?
I don't have any system or third-party firewalls or antivirus software.

Have you successfully located and enabled the UPnP or NAT-PMP settings in your router's web UI?

· I've turned UPnP/ NAT-PMP on and ARC won't connect

Select the Diagnostic Keyword or Text String

· Something else

Don't give up yet.

· I'm stuck. I'd like to create a post to ask Roon Community for help.

Describe the issue

Roon Arc Not ready experienced after database had to be recovered

Describe your network setup

ISP: Brsk

Devices: Brsk ONT, Linksys Hydra Pro 6 (AX5400) router, Netgear GS305 unmanaged switch, HP Elitedesk 800 G5 mini (onboard ethernet)

How they are linked: ONT > Linksys router > switch > Elitedesk server (each step is done over ethernet)

Roon server running on Ubuntu Server 22.04.5 LTS

Output from diagnostics: { "ipv6_connectivity": {"status":"NetworkError","status_code":504,"error":"error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined"}, "ipv4_connectivity": {"status":"NetworkError","status_code":504,"error":"error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined"}, "external_ip": {"actual_external_ip":"88.ggg.hhh.iii","actual_external_ipv6":"2a10:aaa:bbb:bbb:ccc:ddd:eee:fff","router_external_ip":"null"}, "natpmp_autoconfig": {"status":"NotFound"}, "upnp_autoconfig": {"server_ip":"192.168.1.1","found_upnp":true,"error":"\n\n\ns:Client\nUPnPError\n\n\n501\nPAL_UPNP_SOAP_E_ACTION_FAILED\n\n\n\n\n\n"} }

2

It sounds like you might experience the same problem as here:

3

Hi @Nick_Knowles,

Restoring a Backup will generate a new unique RoonServer database - you’ll unfortunately need to re-onboard ARC by reinstalling the app and syncing to the new server.

The Product team and Devs have work in the queue to improve this Backup experience with ARC.

Concerning port forwarding, depending on your Linux distribution, you might be able to install Tailscale and bypass any router configuration entirely for NAT traversal:

4

Thanks for the response. The database issue was completely out of the blue and concerning as it points to the system being very fragile. I have made no hardware or software changes on my network so my thoughts are that it’s more likely that the problem is with Roon and not the network itself. I had a brief look at Tailscale but I’m not interested in having to install a further piece of software on every device on which I want to use Roon remotely, this feels like a last resort and shouldn’t be required when port forwarding was working perfectly prior to the database issue.

My Arc Connection Status within Roon is still showing that there is a port forwarding issue so Arc won’t work regardless. What can you suggest?

Thanks

5

Hi @Nick_Knowles,

If your ISP, Brsk, has implemented carrier-grade network address translation (CG-NAT), it will block ARC’s port forwarding. This is completely outside of Roon’s control.

By all indications, your ISP is in the process of implementing CG-NAT: What is CGNAT (Carrier-Grade Network Address Translation) and Why We Use It | Brsk Help Center

We recommended Tailscale for this reason.

The port forwarding error you pasted suggests that UPnP isn’t functioning in your router properly.

You can try setting a manual port forwarding rule (TCP) in your router settings pointing to the port numer and IP address listed in Settings → ARC. You will need to do this for every active router in your network upstream of Roon.

Let us know if this helps. Thanks!

1 Like
6

Thanks Connor.

Port forwarding was not sucessful so I have cleared the instructions for that on the router.
I have now installed Tailscale on the server and the main device I use RoonARC on and it works.

Strangely, Roon server still reports the following when testing if Roon ARC can securely access my Roon Server:

{
“ipv6_connectivity”: {“status”:“NetworkError”,“status_code”:504,“error”:“error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined”},
“ipv4_connectivity”: {“status”:“NetworkError”,“status_code”:504,“error”:“error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined”},
“external_ip”: {“actual_external_ip”:“88.ggg.hhh.mmm”,“actual_external_ipv6”:“2a10:aaa:bbb:bbb:ccc:ddd:eee:fff”,“router_external_ip”:“100.jjj.kkk.lll”},
“status”: “status”: MultipleNatFound
,
“natpmp_autoconfig”: {“status”:“NotFound”},
“upnp_autoconfig”: {“server_ip”:“192.168.1.1”,“found_upnp”:true}
}

Is this to be expected? Thanks

1 Like
7

Hi @Nick_Knowles,

No problem - we haven’t yet configured the Tailscale and port forwarding mechanisms to talk to one another. So, when you’ve configured Tailscale correctly, Roon will often still indicate “Not Ready” in Settings.

If you open ARC itself, you should see both RoonServer and Cloud services as available and online in ARC settings.

FYI - we have work releasing into Early Access that should prevent restoring a Backup from requiring an ARC reinstall in the future.

In the meantime, I will mark your last post as a solution. Please let us know if you have any other questions.

1 Like
8

Thanks Connor. I appreciate the continued development of these applications and look forward to the future updates which further smooth out these quirks.

9

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