NUC5i3RYH - i3-5010U Processor (3M Cache, 2.10 GHz), 8 Gb, 4TB Samsung 870 QVO SATA III RAM
Networking Gear & Setup Details
Icotera i4850 Ethernet Router
Zyxel GS1100-16, all units connected with cables, no wifi
Connected Audio Devices
Currently 2 x Sonos Play 5 1st Gen
Number of Tracks in Library
11.000 tracks + Qobuz
Description of Issue
Roon Core keeps shutting down after around 5 minutes. I have not measured the duration accurately. No clue as to why it happens. It has been like this before, but the problem went away and now it has come back again. I access the PC which runs Roon core remotely from another PC or via a client on Windows or Android. The problem persists also when accessing the PC hat runs the core directly. I had difficulties getting the two Sonos devices connected but succeeded after many attempts. From the router interface I see them both listed as 192.168.0.x.
Sorry, forgot to mention. It’s Windows 11, fully updated.
Since I wrote my last addition, I have tried to turn off the screen power saving mode on the NUC (it was set to 5 minutes but with no screen connected to the NUC), and so far, it has not closed down. Will try to have it running for some time now with music playing.
I have Roon Core on the NUC. I started setting up and running the NUC with a screen and keyboard/mouse, now it is without. So you suggest I uninstall Roon Core and instead install the Roon Server package on the NUC?
I reinstalled Roon Server on the headless NUC and restored my Roon database. For now, it seems to keep playing. I can access the Roon Server from Roon clients on two different PCs on my network, both cabled. However, two Android wireless devices on the same network, one of them tested also as cabled and with uninstall/reinstall of the Android app, are not able to connect to the new core. It is found but the Android app keeps showing “connecting” with a red dot. Could it be something with the firewall on the NUC? I did get a pop-up firewall message which I accepted when I first re-connected one of the PCs, but I don’t think there was something similar related to the Android devices.
@Geoff_Coupe, after another full restart of the Roon Server, the Android devices now connect. So far, the system has been stable for some hours now, so it seems your tip has solved my problem. Thanks.
I have now had Roon Server in use for some days. It is stable.
If the server is turned off and back on again, the Windows autologon I earlier set up, still works. It is connected to my own main admin Windows account.
However, I cannot get autostart of the Roon Server to work (I had that working in my earlier setup). I have tried both to tick the “Launch at startup?” right-click menu from the task bar, and to include a shortcut to Roon Server in the startup-folder. The only way I can get the Roon Server to start is to logon remotely to the headless server. Then the Roon Server starts on its own.
The help instructions on this issue points to an insecure setup that will compromise the security of the server severely, cf. https://help.roonlabs.com/portal/en/kb/articles/configuring-windows-to-log-in-automatically-for-headless-servers and especially the Windows support page it links to.
If I were were to use this approach, I would do so only with non-admin account. I tried to set up a local account on the server, but I could not figure out how to proceed. @Geoff_Coupe , how did you solve this on the headless windows server you had running?
Hi @Geoff_Coupe . What you are linking to and suggesting, is similar to what I linked to above. Those methods leave the computer and possibly also the local network open to virtual attack and physical theft without any kind of login security. I have instead chosen to keep the PC running 24/7 with an option to turn it off remotely when on vacation, or using an automated routine via a smart plug. For login after restart, I found Microsoft’s RD client app for Android, which requires the same level of authentication as if I were using the PC with remote login from another PC. The setup with Roon Server and login as described here has now been stable for a week. Thanks for your help.