Just curious, in case this suggests something amiss my Nucleus. Requires a fresh Roon login (generating an automatic security email from Roon) on every power cycle, whether from an outage or after I do “power down” from the web interface.
I don’t run a Nucleus by ROCK doesn’t do this and I doubt the Nucleus should
Shouldn’t do
I switch mine off after every listen - logs in automatically
Roon Core Machine
Nucleus rev. A
OS Version 1.0 (build 254) production
Networking Gear & Setup Details
Netgear Nighthawk X6 R8000
connected by Ethernet
Connected Audio Devices
dCS Rossini (ethernet through EtherRegen switch), various Chromecast Audios and Sonos Play3 (WiFi)
Number of Tracks in Library
~50,000
Description of Issue
After power cycle (whether outage, or after power down via web interface, or manually pressing the power switch), my Nucleus requires a fresh login. That then generates a “new device logged into your Roon account” security email from you all. Also frequently loses Tidal or Qobuz login status, as well. I’m told this isn’t normal behavior. Ideas?
Hey @Fred_von_Lohmann1,
Thanks for providing some additonal information around your setup!
How often are you running into power outages? I would strongly suggest adding an APC to your setup as soon as possible.
Power outages can negatively impact the Roon database stability and SSD health. I am not yet seeing any SSD errors at the moment, but continued power outages may cause further instability.
If possible, I would go ahead and do a full power cycle of your router and network as well. From there, please reproduce the issue and share the date and time around when you reboot and are forced to log in again.
Thanks, Fred! 
1 Like
OK, I’ve just power cycled my Nucleus twice, both times by choosing “power off” from the web interface. I also powered down my router and switch at the same time. The first time, the Nucleus came back without needing me to log back in, but the second time, it required the login (and also for TIDAL).
1 Like
Hey @Fred_von_Lohmann1,
Thanks for giving that a try! I would next check your Nucleus Web UI to make sure that you have valid DNS servers setup there and then if the issue is still ongoing after checking the WebUI DNS, I suggest you change your router’s DNS servers from the ISP provided ones to Cloudflare DNS , Quad9 or Google DNS.
Can you please give this a try and let me know if it helps? With that, do you have any third-party firewalls/ VPNs or additional network gear at play?
Thanks!
OK, in the Nucleus web UI, I changed from DHCP to Static IP (I’d already set my router to give the Nucleus a static IP) and manually set the DNS to Google’s DNS. Then power cycled from the Web UI, and all seems to be working. Will test a few more times just to be sure.
Just be sure that if you ever change anything on the network you also update the static IP. DHCP should work with any reasonable router and is usually the safer option, and should never be the cause of such problems. I’d recommend that you try again to set it back to DHCP now that you have changed to Google DNS on the router (which is most likely what fixed it). There is simply less potential for future problems due to collisions with the static IP.
Sensible advice, but I’d already set my router DNS to Google’s (8.8.8.8 and 8.8.4.4) when I did my last test and still had the same problem. ¯_(ツ)_/¯
OK, weird. If I was you I’d investigate that, but on the other hand you can live fine with the static IP, just don’t forget that the Nucleus has one and you might have to update it if anything changes 
This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.
Hey Ben, this didn’t fix it. Just had a power cycle, and again it’s forcing me to log in again.
Hey @Fred_von_Lohmann1,
I’m sorry to hear this. Can you please confirm your previous settings that helped earlier are still enabled?
I’m actually not seeing your Nucleus online at all, are you able to bring it back online so we can enable diagnostics?
We had a bit of ISP outage. Should be up now.
Settings still the same, static IP and hard coded DNS to Google 8.8.4.4.
Hey @Fred_von_Lohmann1,
Thanks for letting me know. I’d be curious to see how things run on a fresh database. Please before doing anything else, make sure to create a fresh backup. Steps to follow below:
- Create a Backup of your current Roon Database
- Stop RoonServer from running in Nucleus’s WebUI
- Navigate to your Nucleus’ Database Location
- Find the folder that says “RoonServer”
- Rename the “RoonServer” folder to “RoonServer_old”
- Restart the RoonServer in the WebUI to generate a new Database
- On the Roon Remotes, press “Use another Core” and connect to the new database
Now, if you can, please test out how things run before restoring from a backup, and if your issue persists. Thanks!
OK, that seems to have fixed it, at least after three power cyclings (once by web UI, once by unplugging, once by physical switch on the Nucleus) before restoring from backup, and one after restoring from backup.
Hey @Fred_von_Lohmann1,
I’m glad to hear things are functioning better on a fresh database! To be clear, you then restored from a backup, and things are still running smoothly?
Well, the news is mostly good. When powered down from the Web UI, it seems to log itself back in just fine. But we had a power outage tonight, and it once again required me to log in. At that point, after logging in, it gave me the “there was an issue loading your library,” After a reboot, it logged itself in and all seems to be fine again. So it seems like the issue still arises when power is unexpectedly cut.