Issue accessing Roon server on Synology 920+ due to login problem, metadata update pause, and license exceeded notification (ref#MYDIQM)

Is Roon Server running?

· Yes, Roon Server is turned on and running.

What do you see on your screen?

· "Looking for your Roon Server"

Please try to restart your Roon Server by closing the Roon app in the taskbar or rebooting your Roon Server machine.

· No, the issue remains the same

Please try to restart your network setup by unplugging, waiting 30 seconds and then replugging in your networking gear.

· No, the issue remains the same

Please select how you've connected your Roon Server to the internet

· Roon Server is connected by *WiFi*

Have you checked your firewall settings to ensure that Roon is allowed through?

· Roon still won't connect even after checking this aspect

Have you verified that Roon Server is on the same subnet as your Remotes?

· My Remotes and Server are on the same subnet and I still can't connect

Sometimes the issues can be resolved with a reinstall of your Roon Remote app. Let's try to perform a reinstall and see if it helps.

· I've reinstalled the Roon Remote but it did not help

What is the operating system of your Roon Server host machine?

· Roon on a *NAS* (Synology, QNAP, ASUSTOR)

Select any of the following components that are present in your local network setup

· None of the above

Describe the issue

I installed the Roon suite on Synology 920+. I can find the Roon server when connecting through the client, but there is no response every time I log in. I used to be able to access it for a while by restoring the backup (at this time, there was also a prompt that the metadata update was paused. , prompting that the Roon server cannot be connected), but it was no longer accessible the next day. Before this, Roon server was also installed on the PC, and there was a prompt that the license was exceeded.

Is the Synology the machine called „dgjin“? Note that it is using an Early Access version. Are your remotes also using Early Access (or Beta for mobile devices)?

“dgjin” is my Synology server. I installed the latest version before and had the same problem. I just installed the current version, but the same problem persisted after installation.

This is the error recorded in the system log. The technical expert will check what went wrong.

06/20 18:58:06 Debug: [accounts - LoginSSOConfirm] pkceVerifier: XXXX
06/20 18:58:06 Debug: [accounts - LoginSSOConfirm] pkceChallenge: XXX
06/20 18:58:06 Debug: [accounts - LoginSSOConfirm] code: XXXX
06/20 18:58:13 Trace: [broker/accounts] [heartbeat] now=06/20/2024 10:58:13 nextauthrefresh=06/20/2024 11:32:24 nextmachineallocate=06/20/2024 14:28:13
06/20 18:58:19 Info: [stats] 9062mb Virtual, 3367mb Physical, 1120mb Managed, 307 Handles, 50 Threads
06/20 18:58:22 Trace: [push2] exception thrown. restarting connection (The remote party closed the WebSocket connection without completing the close handshake.)
06/20 18:58:22 Trace: [push2] retrying connection in 10723ms

If you’re China based, there are several threads about problems with reaching Roon from China.

Hi @jin_Dg,

Are you using a consumer VPN with this setup? If so, which one are you using?

Yesterday, I deleted all the files in the original installation directory on the NAS and reinstalled the Roon server. When I logged in again, it prompted that the authorized usage had exceeded, and a button to cancel the authorization of another authorized server appeared. After canceling the authorization, the server installed on the NAS was normal. The network environment was the same as before without any changes. But later, when restoring the most recent backup, an exception occurred again. The element data was temporarily updated, and then an earlier backup was restored. Everything was normal, including ARC, which could be accessed normally.
I still feel that Roon is still unstable in some cases.

Hi @jin_Dg,

If you’re regularly migrating your database between multiple machines, you’ll need to make sure the RoonServer folder not in use on the NAS has been deleted or renamed. Roon is attempting to launch and connect with an extinct database.

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.