Persistent Roon ARC connectivity issue after public IP change (ref#THU0E3)

[oz.garnett]

Hi! What’s not quite right with Roon?

· Can’t reach my Server, remotes or ARC

Can’t connect to my Server, remotes or ARC

· Other ARC issues

Tell us what's going on

· Hello Roon Support,

I am experiencing a persistent Roon ARC connectivity issue following a recent public IP address change from my ISP (HOT).

Current situation:

Public IPv4 is correctly assigned and matches the router WAN IP.

No Double NAT.

Port forwarding is configured correctly.

External port check confirms the ARC port is OPEN.

Core machine has been fully rebooted.

Router has been power-cycled.

ARC has been disabled and re-enabled.

Despite this, ARC diagnostics show the following:

{
"ipv4_connectivity": {"status":"NetworkError","status_code":530,"error":"error code: 1016"},
"ipv6_connectivity": {"status":"NetworkError","status_code":530,"error":"error code: 1016"},
"external_ip": {"actual_external_ip":"","router_external_ip":""},
"natpmp_autoconfig": {"status":"NotFound"},
"upnp_autoconfig": {"status":"NotFound"},
"multinat_autoconfig": {"status":"Success","error":"No Error","routers":1,"routers_mapped":1}
}

Since the port is externally reachable and there is no NAT issue, this appears to be a Cloudflare 1016 Origin DNS error related to Roon’s cloud registration of my Core endpoint.

It seems possible that the previous public IP is still cached or registered on the Roon/Cloudflare side, and ARC is attempting to resolve an outdated origin.

Could you please verify:

Whether my Core endpoint is correctly registered in your cloud infrastructure.

Whether the previous IP needs to be cleared or re-provisioned.

If there is any manual reset required on your side.

Please let me know if you need a Diagnostics ID or any additional logs.

Thank you for your assistance.

Best regards,
[Your Name]

Tell us about your home network

· HOT Box 5F

[alex_h (Alex)]

Hello @oz.garnett ,

Thanks for reaching out to us.

The error code 1016 you shared with us indicates maintenance from our provider, Cloudflare.

Please view this post for more information.

We expect this problem to be resolved soon and your connection reestablished.

Thanks.

[oz.garnett]

this is a matter of days or weeks?

[vadim]

Hello @oz.garnett

Thank you for your patience and for the extremely professional breakdown of the situation. You hit the nail on the head regarding the Cloudflare 1016/530 errors.

The infrastructure issues with Cloudflare that caused these DNS resolution errors have now been fully resolved.

Just to clarify: While the Cloudflare outage was active, the diagnostic “Not Ready” message was often a false alarm. Were you actually unable to connect your phone to ARC during that time, or were you mainly concerned by the error codes in the settings?

Please check your ARC tab now—it should be back to green. If you still encounter any issues with the connection, let us know and we will investigate further!