Roon ARC and local network connection issues after latest update (ref#IFBNVP)

Is Roon Server running?

· Yes, Roon Server is turned on and running.

What do you see on your screen?

· "Waiting for your Roon Server"

What happens if you press the "Select a different Roon Server" button?

· I don't see Roon Server.

Please try to restart your network setup by unplugging, waiting 30 seconds and then replugging in your networking gear.

· No, the issue remains the same

Please select how you've connected your Roon Server to the internet

· Roon Server is connected by *Ethernet*

Have you checked your firewall settings to ensure that Roon is allowed through?

· Roon still won't connect even after checking this aspect

Have you verified that Roon Server is on the same subnet as your Remotes?

· My Remotes and Server are on the same subnet and I still can't connect

Sometimes the issues can be resolved with a reinstall of your Roon Remote app. Let's try to perform a reinstall and see if it helps.

· I've reinstalled the Roon Remote but it did not help

What is the operating system of your Roon Server host machine?

· Roon on a *NAS* (Synology, QNAP, ASUSTOR)

Select any of the following components that are present in your local network setup

· None of the above

Describe the issue

Ihave this problem with the latest versions:
ARC: Server not online message
Roon on local network: NAS server visible but unable to connect. After a few seconds, it prompts me to log in, then tells me I’m already connected…

Everything was working fine before, no configuration changes.

What’s the problem?

Describe your network setup

Roon server on Synology NAS 224+ ; ethernet networks ; all works fine before the last versions !

Hello @Daniel_LEVY ,

Thanks for reaching out.

Can you provide more details regarding this aspect? If it is asking you to Unauthorize, you can safely go ahead and do so, and then re-authorize the server after.

Thank you for your response.
I had to log out and Roon worked again (without having to log back in !).
The same thing with ARC which worked after logging out…
In fact, it seems that I was logged in twice, it’s quite curious!

Hi @Daniel_LEVY,

We’re glad to hear that restoring the login session seems to have worked. The most likely culprit is a timeout during the initial connection attempt. Let us know if this happens again by reaching out in a new tech support request here. Thank you!