You are hitting a “perfect storm” of three potential issues here: a known display bug in Roon, a likely ISP configuration, and a UniFi-specific quirk.
Here is how to break them down:
1. The “False Negative” Check (Error 526)
First, we are currently experiencing a display glitch where Roon Settings reports Error 526 and “Not Ready” even when ARC is working perfectly.
Please test this first: Turn off Wi-Fi on your phone and try to play music via ARC over cellular data.
If it works, ignore the error message for now.
If it fails to play, proceed to step 2.
2. The ISP Check (Leaptel & CGNAT)
Leaptel (like many Australian ISPs) often uses CGNAT (Carrier Grade NAT) for residential connections. This means multiple customers share one public IP address, which makes Port Forwarding impossible, regardless of your router settings.
How to check:
Log into your UniFi Network Dashboard.
Go to your Internet / WAN settings and look for your WAN IP Address.
Compare this IP address to what you see on a site like whatismyip.com.
The Verdict:
If the UniFi WAN IP starts with 100.x.x.x (or 10.x.x.x), you are behind CGNAT.
Solution: Contact Leaptel support and ask to “opt-out of CGNAT” or request a static public IP. They are usually very helpful with this.
To bypass the CG-NAT restrictions, we are offering the Tailscale solution more information, you can find here:
I was aware of the “false negative” and tested for it before submitting my support ticket. You were also correct that my ISP uses CGNAT by default, but I logged into their portal and turned it off since my earlier error messages were indicating that this was a problem. Today, mysteriously, ARC is working. I haven’t changed anything since I contacted you last night, but the last change I made was to revert to UPnP and disable port forwarding (I had tried both ways many times before). Perhaps my router took some time for the changes to be reflected. You mentioned three possible issues in your reply, including one that was a quirk with Unifi, but you didn’t actually list point three or tell me what the quirk was. Could this be it?
Thanks for letting us know that ARC is working. The 526 error was due to the recent server-side outage, glad to hear that everything appears to be working properly again!