Roon ARC cannot access Roon server suddenly (ref#WLIKNL)

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

· Roon Arc is suddenly not accessing the roon server.

Tell us about your home network

· It's a Cox modem/router that's standard issue.
Roon Arc has worked on/off for the 3 years I've had it.
Typically a computer restart fixes the problem but it hasn't the past two days.

Hi @John_Shaw, thank you for the diagnostics. They answer the question, and the answer is not something you can fix in your router settings.

Your connection is behind carrier-grade NAT. Roon traced the path out of your house and found two routers before the internet:

Network Hop 1..Found Router: 192.168.0.1
Network Hop 2..Found Router: 10.хх.ууу.1
Network Hop 3...Reached WAN, Stopping trace
Carrier Grade NAT (CGNAT) Detected...Exiting!

The first is your own Cox router. The second, 10.хх.ууу.1, is a private address belonging to Cox, not to you. Your public address is shared with other Cox customers, and the device that shares it sits inside their network.

This is why upnp_autoconfig and natpmp_autoconfig both report NotFound, and it is why manual port forwarding will not help either. A forwarding rule on your own router only carries traffic as far as the Cox equipment, and Roon ARC cannot get past that from the outside.

It is also consistent with what you describe. Roon ARC working on and off for three years, with a restart sometimes fixing it, is what happens when the address you are given changes. Once an account is moved permanently onto carrier-grade NAT, restarting stops helping, which matches the last two days.

There are three ways forward.

1. Ask Cox for a routable IPv4 address. This is the clean fix and it makes everything work as designed. Call them and ask whether your account is on CGNAT and whether they can move you to a public IPv4 address. Some plans include it, some charge a small amount, and some only offer it on business accounts. If you get one, Roon ARC will configure itself with no further work.

2. Use Tailscale. This connects Roon ARC to your server without any port forwarding at all, which sidesteps CGNAT entirely. It is free for personal use and it is the usual answer for people in your situation:

We would start with the call to Cox, since that is the only option that fixes the underlying situation rather than working around it. If they cannot help, Tailscale will get you running.

Please let us know what Cox say, and we will pick it up from there.