I run Roon server EA on a Qnap NAS (HS-264) working flawlessly with recent versions.
Since I updated to B1532, every time the roon server app is launched (which happens regularly due to energy schedule and remote booting), roon remote (any) will not recognize it automatically. I have to go through the ´Choose another roon server´ procedure including signing-in an de-authorizing what appears to be a remnant of the previous login on the same server. Seemingly roon fails to identify that it is one and the same server I am running it on.
A side effect of this behavior is me loosing all audio device preferences. Not even a backup restore helped bringing them back.
Interestingly Roon ARC will show several of these ´ghost servers´ of mine which have been online recently but are all not available anymore.
Me too. Everytime I restart Mac mini M2 pro in which Roon server is running, I am urged to select a different server, and I do so. However, the server is eventually the same server I had to quit.
I had this happen with 1532 also. I rebooted my W11 Roon Server PC and after resetting all my remotes to connect to my “new” Roon Server, everything is stable. A weird anomaly I found is that my Roon Server ID is different for 1532 than previous to 1532. My Roon Backup seems to see my 1532 Roon Server as a different device. Not sure what happened, but as I noted, everyrthing is stable again.
Can confirm as well. Uninterrupted service for weeks, just this afternoon got prompted for a macOS update. Got caught in a loop of sign in, authorization already in use, sign in again, deauthorize, sign in again, authorize. Thank goodness my listening stats were retained.
