ARC should alway work when the phone is connected to the same network as your Roon Server (i.e. when using your home WiFi). However, when using a Cellular service or a WiFi service other than your own, ARC will not work unless you have set up port forwarding or Tailscale.
It looks like your router is not configured for port forwarding. Your router is not provideing a uPnP or natPMP service and, from the diagnostic text above, there is no evidence that you have correctly set up a manual port forwarding rule.
The Roon Help pages on Port forwarding can be found at:
Further help with port forwarding trouble shooting, should you need it, can be found at:
The alternative to setting up port forwarding, is to set up Tailscale on the Roon Server. The Roon help centre also has a handy guide for this at:
There are linked pages for detailed instructions for installing Tailscale on the common Roon Server platforms but Unraid is not among them.
Instead, you can follow the directions given at:
Note: If tailscale is used, the port forwarding status will continue to indicate that Roon ARC is ‘not ready’ and you will continue to get the diagnostic text describing the problems with port forwarding. This is normal and expected and can be ignored.
The fortigate clearly states, the traffic from the phone is answered by the roon-Server.
There is trafic from 176.xxx.xxx.xxx to 192.168.2.5 which is the IP on the wanside of the fortigate, and it’s mapped to the external ip. All traffic is answered. see screenshot.
Portforwarding is active and ok.
ARC won’t work in internal network either. it’s the same error exactly.
This thread indicates you might require assistance from Roon technical support.
To equip the Roon Technical Support team to assist you directly, please follow this link to provide the details of your case to Technical Support: Technical Support Request
Respond to the prompts there to ensure that you’ve performed basic troubleshooting and to ensure Technical Support has the full details necessary to expedite Technical Support’s investigation into the case. Your responses will auto-generate a Community thread in the appropriate section.
I’ll close this thread now, and a moderator can merge the content into the support ticket.
issue described in Forum There is traffic between the iPhone with arc and the roon-Server, but it says, something is wrong with roon https://community.roonlabs.com/t/is-arc-broken/291103/4
Describe your network setup
1und1 DSL > Fritzbox 7530AX > Exposed Host > Fortigate 40F (no filters on the roon rules) > Unraid > Docker > Roon it worked before.
Roon support processes tickets according to the date and time received. Your ticket was created on a weekend, it’s now Monday, and the working day has barely started in the US.
If I’m understanding this correctly, your next-gen firewall in the enterprise-grade switches is blocking traffic to and from ARC from your RoonServer, which you’re running in a docker?
You’re going to need to establish a single, reliable network path for NAT traversal between your server and the phone, and you’ll need to restrict RoonServer’s access to whatever network interface serves this pathway on your RoonServer machine.
Tailscale, if installed on both server and phone, will create a proxy mesh that bypasses the Fortinet apparatus entirely. We usually recommend that route for networks with this level of security.
1&1 has widely restricted IPv4 addresses and implemented DS-Lite/CG-NAT across their residential tier. Tailscale will also reliably traverse CG-NAT.
It seems it’s kind of not getting, or falsly reporting to roon, which IP is used… maybe that’s due to 1und1, while dslite is disabled by choice.
It would be very kind of you, to tell me, how to configure roon, not to use the discovery script for determing the IP, but putting in dynds.tld instead, that would solve the problem once and for all, because it seems it isn’t stable and i want to put an end to it without using another service i really don’t need.
Thank you for your patience. Unfortunately, we don’t have evidence this situation is not highly specific to the enterprise-grade network components and docker-based environment in which you’re running Roon.
Excuse me, but are you serious?
This is a pretty straight forward job.
I’ve got an VIP, which listens to port 5**** on my public IP-Adress and it points to the roon-Server on the same port.
Again, it works at the moment, but your script, which determins my ip-Adress and the port doesn’t work properly with this.
All i need is to know, where to put IP/FQDN and port manually and fortget about this script, you use. or are you telling me, there is no way, to do this?
btw. I do this for a living, and so far, till today, every service i made public this way, is still up running. No matter if dyndns or static IP. there is no real challenge in it. it’s your script, that is challenging.
I’m sorry that we’re not able to provide what you’re looking for, but Roon’s official support apparatus at this time does not extend to include enterprise-grade managed networks involving components like the Fortigate 40F.
