Roon ARC app unable to connect (ref#R8NDQ0)

What’s happening?

· I'm having trouble with Roon ARC

What best describes your issue with ARC

· Other

How can we help?

· None of the above

Other options

· Other

Describe the issue

ARC app connection issue

Describe your network setup

Roon server connection doesn't seem to be an issue any more. The ARC connection status on the server is showing "Ready"

To add to the above posting. ARC issue started after I switched to a new provider since we don’t get static IP. The connection issue continued even after I got static IP, for some reason roon was unable to get IP information and diagnostic data was showing IP. One of the threads has information on how to fix the issue by disabling IPv6, so I added the following to my Linux server to disable IPv6.

sysctl -w net.ipv6.conf.all.disable_ipv6=1
sysctl -w net.ipv6.conf.default.disable_ipv6=1
sysctl -w net.ipv6.conf.lo.disable_ipv6=1

IPv6 was disabled but didn’t fix the connection issue. After checking the logs, it turns out it was DNS issue which was weird since the server didn’t have any issue resolving other hostname.

01/18 12:10:24 Debug: [.NET ThreadPool Worker] [easyhttp] [100] GET to https://api.roonlabs.net/push-manager/1/connect returned after 274 ms, status code: 200, request body size: 0 B
01/18 12:10:24 Debug: [.NET ThreadPool Worker] [push2] push connector url received from push manager: ws://push-connector-v2-1.prd-roonlabs-1.prd.roonlabs.net/
01/18 12:10:24 Trace: [.NET ThreadPool Worker] [push2] connecting to push2 connector at ws://push-connector-v2-1.prd-roonlabs-1.prd.roonlabs.net/
01/18 12:10:24 Trace: [.NET ThreadPool Worker] [push2] exception thrown. restarting connection (Unable to connect to the remote server)
01/18 12:10:24 Trace: [.NET ThreadPool Worker] [push2] retrying connection in 30295ms

Fixed the DNS issue and finally showed that it’s connected.

Unfortunately, the issue doesn’t end there. Now my ARC app can’t connect and since I don’t have access to this app logs, I’m totally lost here.

Hi @Kentaga_Kartadinata,

ARC diagnostics that the session has become invalidated because the RoonServer ID has changed. If you’ve migrated your RoonServer between machines or restored a Backup, you’ll need to resync ARC by reinstalling.

Disabling IPv6 likely won’t have any effect here, and NAT traversal doesn’t appear to be the problem, but you can try installing Tailscale instead of relying on port forwarding as a first step.

We generally recommend assigning Cloudflare (1.1.1.1) or QuadNine (9.9.9.9) as the router’s DNS server, since these reliably resolve all Roon-related addresses.

Please let us know if this helps.

Thanks @connor,

Reinstalling the app resolved the issue. Although it was inconvenient, it worked :slight_smile:

I’ve updated the DNS as suggested, thanks again.

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