What happens if you press the "Select a different Roon Server" button?
· I see my Roon Server, but I still can't connect.
When you try to connect, what screen do you see?
· I see the Server but the Connect button is grayed out
Please try to restart your network setup by unplugging, waiting 30 seconds and then replugging in your networking gear.
· No, the issue remains the same
Please select how you've connected your Roon Server to the internet
· Roon Server is connected by *Ethernet*
Have you checked your firewall settings to ensure that Roon is allowed through?
· Roon still won't connect even after checking this aspect
Have you verified that Roon Server is on the same subnet as your Remotes?
· My Remotes and Server are on the same subnet and I still can't connect
Sometimes the issues can be resolved with a reinstall of your Roon Remote app. Let's try to perform a reinstall and see if it helps.
· I've reinstalled the Roon Remote but it did not help
What is the operating system of your Roon Server host machine?
· *Linux Server* (Ubuntu, Fedora, ArcLinux...)
Select any of the following components that are present in your local network setup
· *Mesh networks*
You mentioned a mesh network in your setup. Certain common mesh networks might require slight reconfiguration to support Roon.
· Orbi
Click below for next steps with an Orbi mesh network.
· I still need help.
Describe the issue
I reinstalled Roon Server on SonicTransporter i5 Roon Remote keeps indicating "Update Required" but sonictransporter is updated to the latest 2.65 build. I cannot get to Settings without connecting to a core. The Core is updated by the remote is not recognizing it. I have reinstalled the Remote App, stopped the Roon Server on the sonictransporter, Rebooted the sonictransporter, restarted the Roon Server, sonictransporter reports the latest verstion installed but the Remote App still says "Update Required" How do I get the remote app to recognize the software version so I can connect to my Roon Server?
Describe your network setup
The sonictransporter is connected via Ethernet. Some remotes like the one I am using on the Macmini are connected via Ethernet. Other remotes like my iPhone and iPad connect via WiFi. None of this was a problem yesterday.
If you want to use Early Access on the SonicTransporter server, you probably have to update your remotes to Early Access versions, too:
Generally, it is always recommended to use either Production or Early Access for all devices. Otherwise, it may cause weird issues. However, it is often nevertheless possible to connect to the server if you mix Production and Early Access versions. However, the current Early Access version has larger changes including changes to the authentication protocols, so this may not be possible right now.
The fact that the message says “update required” for the server is probably just a confusion caused by the mismatch of Early Access and Production. It’s not that you have to “update” the server, it’s just that the versions don’t match. Either change the server to Production or change the remote(s) to Early Access.
I wanted to check in and see if you were able to review the excellent advice provided by Suedkiez above!
To officially confirm: the issue you are experiencing is due to a version mismatch. Your SonicTransporter is currently running build 2.65, which is our Early Access (Beta) branch. However, your Roon Remotes (MacMini, iPhone, iPad) are running build 2.64, which is the current Production release.
Roon requires all devices to be on the same release branch to communicate properly. To fix this and get your remotes to connect, you have two options:
Option 1: Move your Remotes to Early Access (Recommended if you want to test beta features) You can update your Mac, iPhone, and iPad to the Early Access branch so they match your server. You can find the instructions on how to join the Early Access program for your remotes here: Roon Early Access Program
Option 2: Revert your SonicTransporter to Production If you did not intend to install the beta software, you will need to roll your SonicTransporter back to the stable Production build (2.64). Since the SonicTransporter is a third-party device, you will need to do this through the Sonicorbiter web interface:
Please let us know which route you choose and if you are able to get reconnected!
