QNAP TS-1655 compatibility and performance with Roon (ref#HARG60)

[J.A]

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

· QNAP TS-1655

Tell us about your home network

· ZTE F8748

[alex_h (Alex)]

Hi @J.A ,

Thank you for reaching out and providing such detailed information about your network setup. The diagnostic code you shared (status_code: 526) is very helpful.

Error 526 is a Cloudflare-specific error indicating an “Invalid SSL Certificate.” Since Roon ARC relies on Cloudflare’s infrastructure to establish a secure connection, there are two main reasons this usually happens.

1. Recent Cloudflare Outage (Please test again) There was a widespread Cloudflare outage earlier today that affected SSL handshakes in certain regions, which perfectly aligns with the error you are seeing. The good news is that Cloudflare has resolved this issue.

• Next Step: Could you please try testing your ARC connection again in the Roon client? It is likely that the issue has resolved itself now that the outage is over.

2. Local Network Security Settings (If the issue persists) If ARC is still showing "Not Ready" with the same 526 error, it means something on your local network is intercepting the secure traffic and replacing the SSL certificate.

• Check Router Security: Please log into your Router’s web interface and look for any settings related to "Cyber Security," "Advanced Security," or "Web Protection" (ISPs like CenturyLink sometimes enable these automatically). Try temporarily disabling these features to see if ARC connects.
• Verify Static IP: Double-check your machine’s current local IP address in windows/linux Network settings. Sometimes, even with a static IP setup, a machine might grab a different address (e.g., switching from Ethernet to Wi-Fi), meaning your Port forwarding rule is no longer pointing to the correct device.

Please let me know if ARC connects after the Cloudflare fix.

[J.A]

Hi,

Sorry, I replied to you by email yesterday and you didn’t receive the message.

Thank you for your response.
I tried again as you suggested, but I still couldn’t connect.
I disabled the QNAP firewall, but it still didn’t work. I enabled UPnP on the router, and ARC connected.
I re-enabled the QNAP firewall, but it’s giving a connection error.
I added a rule to allow connections from 192.168.146, but it still won’t connect. It only connects with QuFirewall disabled.
I suspect I entered the settings incorrectly.
I’ve attached screenshots.

[alex_h (Alex)]

@J.A,

Thanks for the update.

Since you’ve confirmed that the firewall is blocking the connection, we just need to adjust the rule to allow outside access.

The Issue:

Currently, your firewall seems to be configured to only allow connections from the local network. When you switch to cellular data (4G/5G), your phone attempts to connect from an external IP address, which the firewall is rejecting.

The Solution:

To fix this, you need to configure QuFirewall to allow incoming connections on your ARC port from any source, not just your local devices.

Please apply the following settings to your rule:

• Permission: Allow
• Interface: All interfaces (or the specific adapter connected to the internet)
• Source: Any (This is the most important setting—it allows connection requests from outside your home network)
• Protocol: TCP (or TCP & UDP)
• Port: 55002

Please let us know if updating that rule gets everything working for you.

Thanks.

[J.A]

Hi,

Thank you so much for your help.

I configured it exactly as you said (although the TCP&UDP option isn’t available) and it worked correctly after enabling QuFirewall.

Thank you very much.

One thing that happens is that whenever some time passes without me using Roon ARC, the server doesn’t connect on my iPhone 14.

I fix it by uninstalling the app and reinstalling it.

Is this normal?

Regards.

[alex_h (Alex)]

@J.A,

Thanks for the update.

While I am glad to hear it is working, we do not typically expect this specific behavior to occur. To prevent it from happening again, we want to be sure we understand the root cause.

Isolating the Variable At this stage, it is difficult to determine if the issue is strictly due to the firewall configuration or if there is a conflict with the app/phone itself.

To help us distinguish between the two, could you please try temporarily disabling the firewall completely?

• If the issue disappears entirely with the firewall off, we know it is a rule configuration issue.

• If the issue persists even with the firewall off, we know the problem lies elsewhere (e.g., the phone or app).

Please let us know your observations after testing this.

Thanks.