What happens if you press the "Select a different Roon Server" button?
· I don't see Roon Server.
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?
· *Roon Optimized Core Kit* (ROCK)
Select any of the following components that are present in your local network setup
· None of the above
Describe the issue
After upgrading to the latest Roon Rock and Roon remote on various Android devices, the remote doesn't find the Roon Core anymore. If one enters the Roon Rock IP address into the browser on the Android device, it immediately connects to the admin dashboard of ROCK.
Describe your network setup
ROCK = Ethernet, Remote via WiFi, same Subnet, NO change to prior upgrade
Thanks for writing in! Certainly, let us know if rebooting helps things, we’ll attempt to enable diagnostic mode on your Roon Server the next time it’s online and active with our servers.
the server is up an running. Rebooting the server does re-connect, but only when the remote is in search mode. Once the tablet falls into sleep mode, the remote app doesn’t recover the server upon re-launch. Even when entering the IP address, no connection can be establsihed. It then needs the remote app kept in search mode and the server to manually reboot.
It have never experienced this issue before. It started directly after installing the latest updates for server and remote (I have also removed the remote from the tablet and re-installed it).
Thanks for the update! And, my apologies for not being more detailed above, did you also test out fully rebooting your router / any other network gear as well?
Thanks for letting us know. Can you please let us know the exact local time + date when the reboot resolves the issue, and then the local time + date when the issue next occurs? We’ll enable diagnostics for your account to see if there are any specific errors logged.
The app was in the middle of receiving an image when the ROCK stopped talking. Because the app didn’t get an “End of File” signal, it threw a ReceiveFailure.
Can you please try the following:
Go to your Android Settings > Apps > Roon > Battery, and set it to "Unrestricted."
Toggle WiFi "Keep-Alive": Ensure your phone isn't set to "Disconnect WiFi when sleeping" or similar power-saving modes.
Check for IP Conflicts: Ensure 192.168.178.61 is reserved/static in your router. If another device is occasionally trying to claim that same IP, it will "kick" the server off the network momentarily.
situation is not really improving, At 08h10 CET (February 15th) it needed several re-boots of the server to get it up and running. It also failed twice connecting to Qobuz and Tidal.
Sorry to hear it - we’re having issues connecting to your Roon Server to enable diagnostic mode, could you please share a set of manual Roon Server logs?
Can you please use the directions found here and send over a set of logs to our File Uploader? Once logs have been uploaded, please let us know so that we can check the server for your files, thanks!
Thanks for sending those over! We’re seeing quite a few recurring network-related failures happening across multiple areas from your ROCK.
/login check network configuration: socketerr (NetworkUnreachable): Network is unreachable (172.66.148.147:443)
We’re also seeing some interesting Qobuz-related errors:
Warn: [qobuz] [http] error result from http request: {"status":"error","code":401,"message":"Current authenticated user is not authorized to perform this request"}
You have my apologies if this has been glazed over, but could you test out using a different ethernet cable, as well as port, and see if you experience the same issues?
You have my apologies here, but I believe you may be experiencing a known issue related to our upstream DNS providers, here’s the tracking link to the issues:
We don’t yet have any immediate next steps for you to troubleshoot, but the DNS maintenance shouldn’t last long.
