Roon ARC fails to sync after network configuration changes (ref#F3WYMG)

Support
1

What’s happening?

· I'm having trouble with Roon ARC

What best describes your issue with ARC

· Other

Describe the issue

I have been having various problems with the current early access version of roon arc for a few days now.
The programme ran smoothly until I changed my network configuration. With this changed configuration, I was shown a problem with Double Nat on the ARC Settings page. So I reset the configuration to its original state.

The ARC Settings page now shows me ‘Roon ARC can securely access your Roon Server’ again.

However, ARC either takes a very long time to find my Roon Server, and even if it doesn't, it displays ‘something went wrong while syncing to your Roon Server’ after a successful connection.

I tried to restore a backup from a week ago when ARC was still working, but this did not change the situation, so I restored a recent backup. I also reinstalled the app several times and restarted all the devices involved.

After restoring the backup, ARC now finds three servers, only one of which is shown as ‘ready’ (I only have one Roon server). I can connect to this server, but then ‘something went wrong while syncing to your Roon Server’ appears. This message appears both via WLAN in the local network and via mobile data.

How can I use ARC again?

Describe your network setup

ROCK on a NUC (no idea which model), wired to my router via two passive switches.

2

Sounds like the issue that’s under investigation here:

3

To be clear, the issue appeared before I fiddled with backups. But yes, right now, it may be related.

4

I think such an issue occurs often (at the moment) after any server or possibly network change. E.g. the post directly after the linked one

5

I tried to switch to production, as proposed in the other thread, and it solved my issue. So, yes, it looks like it’s related after all.
Will stay on production for the time being, my daily commute without ARC is boring.

1 Like
6

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