After last update Roon forgets it's core and wants to register newly

[Jurgen_Pohler (Jürgen Pöhler)]

Hi there,

since last update I experience issues with Roon:

immediately after the update process Roon forgot it’s Core and after typing my credentials again it created a new Core with a different unique ID. I can verify this in the backup history

after booting my QNAP NAS (Core is running on this device) Roon is now requesting me again to sign in, and as next to de-authorize the Core because I am only eligible to register one Core.

This never happened in the past. What is wrong here?

[ged_hickman1]

Known issue. Select deauthorise and it will continue.
There is a new qnap build available to stop this.

Fix for recurring authorization prompt

I have put updates for the QNAP and Asustor NAS (which have been sent to QNAP App Center / Asustor App Central) on the roononnas.org website, for manual installation as long as they are not officially published. It should fix the recurring authorization prompt after NAS reboot, introduced in Roon Server build 571.

[ged_hickman1]

Whilst you are there ensure your qnap us up to date with its operating system.

[Jurgen_Pohler (Jürgen Pöhler)]

Guess so, see image