Roon ARC is working again for me!

Since yesterday evening, Roon ARC has thankfully been working again, just like it did a few weeks ago.

To get Roon ARC working, I’ve been using manual port forwarding rules in my router for a long time. This has always worked well (since the introduction of Roon ARC). In recent weeks (somewhere at the end of August/the beginning of September) Roon ARC suddenly stopped working properly. This was around the time the Roon team introduced/announced IPv6.

Over the past few days, I’ve been fiddling around with my port forwarding rules in the router, thinking that might be the cause. No matter what I did, I couldn’t get Roon ARC to work (properly). But, to my surprise, last night Roon ARC suddenly started working again as usual, even though the port forwarding rules in my router were configured exactly as they were before the problems.

I firmly believe that the fact that Roon ARC is suddenly working again is related to this post from @beka:

Audio devices disappear on Roon Server and then re-appear [Roon Investigating] - #151 by beka.

Over the past few weeks, the Roon team has been diligently investigating the cause of a problem causing users to experience dropped connections to their audio devices. Last night, Beka announced that the Roon team had found the source of these issues. I believe this is also why Roon ARC is working again.

Kudos to the Roon team!!! :grinning_face:

Apparently they never enabled the change:

I am on Early Access. A few weeks ago there was a post from Roon that IPv6 could be enabled by restarting Roon Server and all the remotes twice. I did that.

@support,
There’s a lot of confusion about what exactly is happening (in combination with the latest Early Access and/or Production version) regarding IPv6 and the recent issue with disconnecting devices. It would be helpful if there were more clarity on the situation. Could you provide that clarity?

I didn’t know / forgot.

Indeed, another less than stellar Roon communication, but Vova already said what he said 3 days ago in the link above

Good day @Alfred_van_Hoorn !

I hope you’re doing well today and we’re glad that your Roon ARC app is functioning as expected now!

I would like to appoint that changes affecting IPv6 were not released yet so that might not be a root cause of your previous device malfunction.

Likely, something has changed in your local network that has brought the stability back.

We can see from our analytics data report that your network set up is quite unusual since your devices have many IPs.

Since everything is working well now there is no issue to investigate anything now.

But in case it breaks again we tend to think it worth looking at network setup first to narrow down the scope of potential issues.

Have a nice day!

Regards.

Hi @alex_h,

Many thanks for your reply. I am happy with it!

Are you sure that the IPv6 changes were not released? I am on the Early Access branche and on 13th of August @vova wrote this:

Enabling network discoverability change for external testers

Almost immediately after @vova published this post, I restarted the Roon server and all Roon remotes twice, as @vova indicated. That’s why I think the IPv6 change was implemented in my case and that the Roon team changed it last Friday. Please let me know if I’m correct or if my assumptions are incorrect.
(For your information. After I twice restarted the EA branche Roon Server and Roon Remotes on 13th of August I got problems with Roon ARC. To find a solution I then replace the EA branche with the Production branche for all my Roon software. This did not make any difference so I returned to the EA branche. You might see these changes in your analytics data reports and this might raise some questions. But now you know the background.)

Furthermore, thanks for looking in the analytics data report for my network! I do indeed have several devices (mainly Raspberry Pis) and IP addresses. I think there were no issues with them but to be sure I’ll will look after it. Thanks for the advise!

Have a nice day too.

Regards,

Hello @Alfred_van_Hoorn

Sorry for the confusion.

Since you are on the early access build, I’m moving your topic to the Early Access section where our QA team may take a closer look.

Hi @vadim,

Thanks for you post!

I await the QA team’s response with interest.

P.S. To be sure the right team would find my issue, I also posted this short message in the EA forum yesterday. Perhaps you could merge/link the threads or something like that?

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