Haven’t used ARC in weeks, so I don’t know when this started, but the server connection check in ARC said „last seen 1 days ago“ when I noticed the problem earlier today while on cell network. (I don’t think I started ARC yesterday while on home wifi but can’t be 100% sure)
Did you, like me, perhaps activate IPv6 in the EA branch a month ago by starting Roon Server and all Roon Remotes twice in succession? If I understand several posts on this forum correctly, this action added some rules to my Roon profile that caused problems (including possibly the ARC issue).
Last friday evening the issue with ARC was suddenly solved. I am still not sure why and I might be stubborn, but I think these rules were removed last Friday from my profile by the Roon team.That could have caused ARC to suddenly work again.
Hmm, weird. I don’t understand how the changes as detailed here would affect ARC communication to the Roon server on the external static IPv4 address. None of the “who is affected” details seem to apply to me
Plus there were 9 days between my first and second test in the other thread. I think I tested ARC the second time, too, but of course can’t be 100% sure anymore.
I had the same issue since last Wednesday. I was on IPV6. It worked for about a month and suddenly not anymore. After a restart of my titan it worked again and after a few hours it stopped again. I have disabled ipv6 on my modem and now it works ok again.
I have a dual stack network and I can say that Roon had been very stable in spotty cell connection zones and then in the past week got crappy again, suddenly…meaning, once it loses cell connection and regains connection, I almost always have to quit and restart ARC, and that wasn’t necessary before the past week (since a few months back when this behavior had improved).
Yes, but they enabled it apparently since the announcement (but not sure, given the confusing communication, and not sure if it’s build specific) and it worked after that AFAICT
Well, I made the mistake of not doing that first, so now we can’t know anymore
Nothing else changed on my side after I undid my changes, but maybe something was temporarily broken on the Roon side - the fact that ARC could not reach the Roon cloud for a while may be a hint that not all was well there.
Had exactly the same ARC connection issue, except for being fully on IPv6 on both ends and were unable to get satisfactory result of roon´s ARC connection test: