· I am having issues doing my initial setup for Roon ARC. I am getting “Not Ready”, “Roon ARC was unable to securely access your Roon Server” messages in my Roon ARC settings page. Some background:
My ISP is Verizon. I run a Verizon router in bridge mode as my internet connection point with a TP-Link BE 19000 router sitting behind the Verizon box serving as my router and providing NAT services. UPnP is “not” enabled on my router/network and I prefer not changing that setup. I have manually setup a port forward rule on the TP-Link to forward port 55XXX which matches the Listening Port setup in my Roon Settings. All protocols are allowed via 55XXX.
Note: I would go through the additional Diagnostic Data but when I try to copy that the operation fails with a “Failed to copy to clipboard” message. I am not sure how to address that problem and/or if there is an alternative method for viewing Log/Diagnostic data.
Tell us about your home network
· My ISP is Verizon. I run a Verizon router in bridge mode as my internet connection point with a TP-Link BE 19000 router sitting behind the Verizon box serving as my router and providing NAT services. UPnP is “not” enabled on my router/network and I prefer not changing that setup. I have manually setup a port forward rule on the TP-Link to forward port 55XXX which matches the Listening Port setup in my Roon Settings. All protocols are allowed via 55XXX.
I usually see the same (empty) diagnostics data as you show here – because I disabled port forwarding in Roon. Maybe it’s the same reason for you? Click on Reset behind the port number input field to enable port forwarding in Roon again.
Note: You may have to set the correct port number for you again after the reset. Please check.
One other piece of information if it matters. My Verizon gateway router/box’s IP is 192.161.1.1 (you can’t change this). My router is at 192.161.1.2. My Roon server (an independent Intel NUC running Rock) is setup with a Static IP address with the gateway set to 192.161.1.2 (the address of my router)
How is the Roon server (192.168.1.X) then supposed to connect to the internet, or even the gateway, when it is in another network?
You probably need to correct your network configuration, or your description, if the error resides there.
Note: 192.161.X.X are public addresses and should not be used in internal private networks, unlike 192.168.X.X which is a reserved address space for internal private use.
Are you having any difficulty connecting to this ROCK in the Roon app itself? What about reaching ARC on WiFi, not cellular?
Your initial screenshot shows that the Roon Server IP address hasn’t populated in the Settings → ARC page. That might be a transient startup state (if it eventually populates later), but it’s probably the reason that the dialog snippet is blank and the copy subsequently fails. In fact, if ROCK hasn’t successfully bound to the IP interface, this would cause the problem in the first place.
Please try rebooting the ROCK and closing/opening ARC itself.
Verizon Bridge mode fully disables NAT, and they don’t use CG-NAT, so this is ultimately going to be a resolvable blockage.
No problem accessing/using basic Roon functions from Wifi or hard wire. I’ve been using this Roon/Rock server for years and am only now trying to setup ARC. I had not yet loaded the ARC app on my phone but tried it and ran into another error. Apparently, my Roon Server running on the ROCK box stopped updating on version 2.60 (build 1629). There is a message, "There was an error checking for an update’ but no further info on what the actual error was.
Ensure a reliable DNS service is assigned in the TP-Link router settings admin page. Sometimes, the address for Roon updates will fail to resolve and background updates (and manual updates) won’t work. We recommend Cloudflare (1.1.1.1) as the default ISP.
Double-check that any network security/firewalls enabled have the ROCK’s IP address safelisted.
Create a Backup if you don’t have one already. The next step is not a threat to your database but we want to perform due diligence anyway.
Once you’ve verified you have a Backup available, close Roon on all your remotes, navigate to the RoonOS web admin page, and reinstall RoonOS. This should force everything to the latest available build once Roon is back online.
Well, initially had the DNS set to 8.8.8.8. Changed it to 1.1.1.1. That allowed the reinstall to start but it ended up failing with the following message:
Good News. Ran the reinstall again (just to make sure) and this time it worked. I am now running 2.67 (build 1661). Better news, this fixed the ARC setup without any further changes. It looks good in the Roon setup panel “Ready” and I can access it via my iphone ARC app.
