Is there a specific error message you see? If so, please select from the following options:
· Other
Please try to reboot your Roon Server and check to see if this helps.
· Rebooting my Server had no effect, the issue remains
Please try to reboot and unplug/replug in your affected audio device and check to see if this helps.
· Rebooting and unplugging/replugging my audio device, the issue remains
Please open your Roon Remote and select the "System Output" Zone and try to play to it. Do you encounter any playback errors with this Zone?
· I don't have a System Output available, but I'd like to keep troubleshooting
Please try fully rebooting your network equipment
· No, I'm still having trouble
An issue with playback on System Output and another zone often indicates a network security problem. *Check your firewall(s)* to ensure that *Roon*, *RoonServer *and *RAATServer* are allowed to properly communicate
· I'm still having problems / This isn't relevant to me
Does the issue happen with local library music, streaming service music, or both?
· Only streaming content while local content works fine
Please select the streaming service(s) with which you're encountering playback problems.
· TIDAL, Live Radio
Streaming errors can sometimes stem from DNS failures. Have you tried changing the assigned DNS server in your router settings?
· I reassigned the DNS server and I'm still having problems
What is the model/manufacturer of the affected audio device(s) and the connection type?
· Lumin U2 Mini, and McIntosh MA9500
Describe the issue
My Roon Rock server is configured with a Static IP Address. After performing the recent upgrade to build 1438. It lost the ability to access the Internet to play streaming music from Tidal, or Live Radio channels. The only way to resolve the issue was for me to change its static IP-Address. Then it was working again. The IP-Address configuration of the RoonRock Server is static on the server, - I have not configured a static - ip-address to be allocated from the dhcp server. This is the 3rd time that I bump into this issue, where an update disconnects it from the internet and I would need to change its IP-Address manually. Nothing else is different or changed. I only need to change its Static IP address, and it works again. At present things are working. I am raising this support ticket, as it merits some attention. Thank you.
Describe your network setup
Internet connection to firewall then to switch and RoonRock server.
That may well be your problem. Why don’t you set a static allocation for your Roon server on your DHCP server? Depending on your router, DHCP server, and network configuration, your Roon server static address may not be properly propagated to every other node in your network. You should let your DHCP server do the job, and not set a static IP address on your Roon server.
I originally had the DHCP allocate the Static IP address. But on certain occasions I may be restarting the firewall-DHCP server, and would want to continue playing music from my local library. And unfortunately, the same issue just occurred with allocating a DHCP static address, as I’m trialing it now, and have lost all internet connectivity.
Something is amiss with assigning Rock with a static IP-address.
A normal dhcp IP-address from the pool, that was not allocated to roon before, works everytime. It’s just an issue with static ip-addresses that need to be changed. If nobody is facing this issue, - then it’s my luck. If necessary, I’ll re-install the Rock server and Roon.
update to the above: I managed to re-configure a static IP-address directly on roon after a couple of shutdowns and start-up of the Rock server. Things are working again.
I suspect that when an update happens, it messes up the static ip-address on the rock server. Not sure whether shutting down the server and starting it up, could be a solution - did not try this. But, changing the IP-address and restarting roon solves it.
To keep things simple. The issue is Roon loses connection with the internet (cannot check for updates, cannot play Tidal streaming, or Live radio channels). I am able to ping the server locally, and it still has access to the local music library that is sitting on a NAS. I have checked the fw-logs and adguard logs, - all DNS queries are passing fine without anything being blocked. I have also configured Roon to use 1.1.1.1 as a DNS server, and confirmed outgoing queries from the fw-logs.
The DHCP server is only needed by the Roon server at startup, or on lease renewal. If you set a static IP in the DHCP server, renewal is not an issue. So, your Roon would keep working fine even while rebooting the DHCP server.
Thanks, am giving the dhcp allocation a try again now. Added Roon into the static allocated addresses on the dhcp. Amended lease renewal - requests to 24hrs. Adjusted Roon to dhcp allocation. Then restarted the virtualization server hosting everything - so the lot loads up in sequence.
Everything has worked fine. Will do a bit of maintenance work on sunday on the firewall/dhcp system, and see if Roon continues to work, and then wait to see for the next early release update.
Thanks for the guidance to change things up. Will close this thread after a bit of time to confirm things are smooth.