Roon Arc is not able to connect to Root Core in QNAP

Support
1

I have no problem accessing other services in my QNAP from the Internet.
But I can’t figure out how to configure Roon for remote access.

How can I change the port Roon Core in QNAP is listening to? Is it always 55000?

So when I run Roon app in my laptop and go to Settings → Roon ARC what is that port value there?
Is it a configuration for Roon Core? Is it going to reconfigure my Roon Core in QNAP to listen to that port? Or is it just an “advertised” port for clients and I need to forward that port to Core’s port 55000?

Diagnosing data is showing

{
“ipv4_connectivity”: {“status”:“NetworkError”,“status_code”:504,“error”:“error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined”},
“external_ip”: {“actual_external_ip”:“220.aaa.bbb.ccc”,“actual_external_ipv6”:“null”,“router_external_ip”:“null”},
“natpmp_autoconfig”: {“status”:“NotFound”},
“upnp_autoconfig”: {“status”:“NotFound”}
}

External ip is correct. But no port information is included.

I don’t know why such simple thing has to be that complicated. :slight_smile:

Please send help.

3

It’s the port number that the Roon server listens on for ARC traffic. If UPnP is enabled on the router, Roon will auto-open this port. With UPnP off and using manual forwarding rules, it’s the port number that must be entered in the manual rule for forwarding on the router. (If you change the number in the Roon settings to a different supported port, it will use this other number).

Sounds like UPnP is off and you did not create a manual rule either

4

Yep, no UPnP, everything is handcrafted. :slight_smile:

Here is what I do.
I pick non-standard port, I telnet into my QNAP into that port from my laptop, I got connection error.
I put this port number into Roon app → Settings → Roon ARC and exit edit control (there is no “Apply” button but it looks like this triggers the update)
I telnet into my QNAP into that port from my laptop again and this time I am connected. So I assume I am connected to Roon server.

If you know the command I can issue in telnet session to trigger some response from Roon server this will help to confirm I am in the right place. Or some connection log on the sever I can check - this will do as well.

I telnet into my external ip-address the same port number as before and I get connection error.
I add port forwarding rule to forward both TCP and UDP and I put the same port number in “From” and “Forward To” and the host is my internal ip-address of my QNAP storage.
I telnet into my external ip-address the same port number as before again and this time I am connected.

So I assume port forwarding works as well.

The issue: at any stage if I hit “Refresh” button in Roon app → Settings → Roon ARC (top right corner) it will come up with the same diagnostic error and “Not ready” status.

5

Just to confirm, you are adding a Port Forwarding Rule to your Router.

6

Yep, port forwarding in my router.
Port number is the same for both “ends”.

7

It looks like I have few issues combined.
One issue was default QNAP firewall rule blocking all connection outside of my region.
With explicit QNAP firewall rule added for TCP traffic on my port I am getting Roon app showing Ready tick now.

The app still doesn’t work outside of my network. Checkin of there is anything else has to be done in my Router other than port forwarding…

Hmmm… I was under impression I am in control of my network. :slight_smile:

8

Finally got it working.

Did another round of troubleshooting by spinning up a Windows VM in AWS and trying to telnet from there listening with netcat inside my network I confirmed nothing is blocking the connection from outside and it reaches the host inside.

Then I switched to another port - instead of 55xxx I used 35xxx port and now I am getting both Roon Arc tick in Roon app as well as my mobile phone can connect to Roon Code remotely.

9

A quick recap for future generations:

I got it working

  • with lower port number - 35xxx instead of 55xxx
  • adding firewall rule into QNAP Firewall to allow TCP traffic for this port from Anywhere.

Thank you for listening.

10

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.