Port Forwarding Issue with Nucleus for Remote Access (ref#8JE3KY)

[JDINMD]

What’s happening?

· I'm having trouble with Roon ARC

What best describes your issue with ARC

· Other

How can we help?

· None of the above

Other options

· Other

Describe the issue

Port Forwarding Issue

Describe your network setup

Mac Mini

[connor]

Hi @JDINMD,

There are a number of reasons port forwarding can fail out-of-the-box.

1. If you have two active routers, you’ll need to either a) place on in Bridge/AP mode or b) create a manual, TCP port forwarding rule in both routers that used the port number and IP address from Roon Settings → ARC. The rules should be identical.

2. If you only have one router, then try disabling UPnP and creating a manual port forwarding rule instead.

3. The blockage might be at the level of your internet service provider in the form of CG-NAT. If you’ve tried steps 1-2 above to no avail, share the name of your service provider here or reach out to them directly to inquire if they block port forwarding with CG-NAT.

A simple alternative to steps 1-3 is to install Tailscale on this Mac and also on the phone alongside ARC. This proxy-mesh VPN creates a secure connection between RoonServer and ARC that can bypass any blockages that restrict port forwarding.

See here for specific instructions on the Mac Mini:

Tailscale Setup Instructions: MacOS RoonServer

[JDINMD]

Thanks for the reply. I use two routers. One is an Xfinity Gateway that’s plugged directly into the Mac Mini that serves as my Roon Core. The other router is a Linksys Velop mesh router that I use in bridge mode.

I created a manual port forwarding rule on my main (Xfinity) router using 55000, and everything works again. (Yay!)

That said, I’ve been running Arc since it was deployed with no problems. So I wonder why I had a port forwarding issue now (when I did not make any changes to any settings). I have no recollection of ever creating a port forwarding rule in the past.

I’m just happy everything is working now. Thanks.