I can still reproduce an issue that would be hard to diagnose based on the ARC settings page information.
My home network supports IPv6 and Ipv4 but my Phone service only supports IPv4.
If I correctly open a pinhole in my ipv6 firewall but do not create an ipv4 port forwarding rule, then the Roon → Settings → ARC page reports ‘ready’ and gives no diagnostic information - despite the fact that no ipv4 connection is available.
Under these circumstances, when my mobile has WiFi disabled, so it is using the cellular service which only supports ipv4, then Roon ARC will not connect to my Roon Server (it does connect to the cloud service as you would expect).
Only when I correctly add an ipv4 port forwarding rule, does ARC successfully connect to my Roon Server over the mobile connection.
For someone like me who has a better than average understanding of how ipv4 and ipv6 work, this is exactly what would be expected to happen. However, for those that have little or no ipv4 or ipv6 knowledge, then this could be very confusing with the Roon Server reporting ARC connectivity ready but ARC reporting a failure to connect to the Roon Server.
I have already posted a feature request for reporting Ipv4 and ipv6 ARC connectivity status separately in the Roon → Settings → ARC page. The request can be found at:
In addition, it may be a good idea to report ipv4 and ipv6 availabiltiy and connectivity status separately in the ARC settings - where Cloud and Server connectivity are currently reported.