Suddenly can't connect to Roon Core on NAS

Core Machine

Synology DS918+

Network Details

Mikrotik

Audio Devices

Hegel h120, Airplay
Linux machine - Roon Bridge

Description of Issue

Suddenly I can’t connect to my core. It was working yesterday without a problem. I don’t think I have changed anything, but today when I tried to connect to core from my iPhone remote, I could connect, but didn’t see any Audio devices (settings - audio was blank. Nothing, no text there). So I tried to restart remote app. Didn’t work.
Then I restarted the Roon Core on NAS. And till then I can’t connect to it. The only thing I see is logo on white screen trying to connect.
I have tried to restart everything including my router, but nothing changed.

Here it the log from Roon Server:

  12:09:10 Info: [stats] 2938mb Virtual, 802mb Physical, 359mb Managed, 0 Handles, 31 Threads
05/16 12:09:25 Info: [stats] 2938mb Virtual, 802mb Physical, 359mb Managed, 0 Handles, 31 Threads
05/16 12:09:40 Info: [stats] 2938mb Virtual, 802mb Physical, 359mb Managed, 0 Handles, 31 Threads
05/16 12:09:55 Info: [stats] 2938mb Virtual, 802mb Physical, 359mb Managed, 0 Handles, 31 Threads
05/16 12:10:10 Info: [stats] 2938mb Virtual, 802mb Physical, 359mb Managed, 0 Handles, 31 Threads
05/16 12:10:25 Info: [stats] 2938mb Virtual, 802mb Physical, 359mb Managed, 0 Handles, 31 Threads
05/16 12:10:40 Info: [stats] 2938mb Virtual, 802mb Physical, 359mb Managed, 0 Handles, 31 Threads
05/16 12:10:55 Info: [stats] 2938mb Virtual, 802mb Physical, 359mb Managed, 0 Handles, 31 Threads
05/16 12:11:10 Info: [stats] 2938mb Virtual, 802mb Physical, 359mb Managed, 0 Handles, 31 Threads
05/16 12:11:25 Info: [stats] 2938mb Virtual, 803mb Physical, 359mb Managed, 0 Handles, 31 Threads
05/16 12:11:40 Info: [stats] 2938mb Virtual, 803mb Physical, 359mb Managed, 0 Handles, 31 Threads
05/16 12:11:55 Info: [stats] 2938mb Virtual, 803mb Physical, 359mb Managed, 0 Handles, 31 Threads
05/16 12:12:10 Info: [stats] 2938mb Virtual, 803mb Physical, 359mb Managed, 0 Handles, 31 Threads
05/16 12:12:25 Info: [stats] 2938mb Virtual, 803mb Physical, 359mb Managed, 0 Handles, 31 Threads
05/16 12:12:40 Info: [stats] 2938mb Virtual, 803mb Physical, 359mb Managed, 0 Handles, 31 Threads
05/16 12:12:55 Info: [stats] 2938mb Virtual, 803mb Physical, 359mb Managed, 0 Handles, 31 Threads
05/16 12:13:03 Info: [brokerserver] Client connected: 192.168.1.24:51440
05/16 12:13:03 Trace: SENT NONFINAL DistributedBroker.ConnectResponse={ BrokerId=219559e5-d576-4d2c-9304-734ba1752c6b BrokerName='synology' }
05/16 12:13:03 Trace: SENT NONFINAL DistributedBroker.UpdatesChangedResponse={ IsSupported=True WasJustUpdated=False Status='UpToDate' HasChangeLog=False CurrentVersion={ MachineValue=100800790 DisplayValue='1.8 (build 790) stable' Branch='stable' } }
05/16 12:13:03 Trace: [push] restarting connection (Unable to read data from the transport connection: interrupted.)
05/16 12:13:03 Trace: [push] retrying connection in 86333ms
05/16 12:13:04 Debug: [easyhttp] [24] GET to https://messaging.roonlabs.net/1/api/messages/a6f49251-c668-45a6-831b-bf8df54e99cf returned after 487 ms, status code: 200
05/16 12:13:10 Info: [stats] 2939mb Virtual, 803mb Physical, 360mb Managed, 0 Handles, 32 Threads
05/16 12:13:13 Trace: Successful POST response from https://push.roonlabs.com/push/1/connect
05/16 12:13:13 Trace: [push] connecting to 34.73.66.119:9200
05/16 12:13:13 Trace: [push] connected
05/16 12:13:25 Info: [stats] 2939mb Virtual, 803mb Physical, 360mb Managed, 0 Handles, 34 Threads
05/16 12:13:40 Info: [stats] 2939mb Virtual, 803mb Physical, 360mb Managed, 0 Handles, 33 Threads
05/16 12:13:55 Info: [stats] 2939mb Virtual, 803mb Physical, 360mb Managed, 0 Handles, 33 Threads
05/16 12:14:07 Trace: [broker/accounts] [heartbeat] now=5/16/2021 10:14:07 AM nextauthrefresh=5/16/2021 10:34:08 AM nextmachineallocate=5/16/2021 12:29:07 PM

Hey Jakub,

I am having the exact same issue on my Synology 1621+

I’ve restarted the NAS, stopped/restarted the Roon package a few times, but still nothing.

Any other logs we could be looking at for clues?

Same issue. Stuck initializing.

Anything new guys? I still haven’t been able to resolve this.

Still the same here… Can we get some help here, Roon? Thanks

Has something change on the roon side?
I have checked everything possible here. Still the same network all my devices (192.168.1.X) , still the same version of the operating system on NAS (6.X.X), still the same versions of roon server and remotes. Yet, I can’t connect all of the sudden.

Also there is no firewall anywhere in my network, nothing.

My solve was to delete and redo the Core. All better now.

Hi @Jakub_Sporek / @Morbeas ,

Can you please use these instructions to access your Roon logs and upload a full log set for review? Thanks!

1 Like

Hi @noris , here are the logs: https://www.dropbox.com/sh/6c9go7kmvjc736c/AABxBZf7-1hoxZm7rhCpVDfna?dl=1

Hi @Jakub_Sporek — I sent you a PM.

Ok, just sent you and dylan a link with the logs.

Much appreciated. Thank you.

Any updates?

Hi, I have solved this issue with the help of @dylan .
It was a matter of Tidal account, which was disabled for me due to payment issue. Apparently Roon had some difficulties with this. I had to delete the tidal_account file from Roon Registry and after that, Roon started as usual.
Try to look into that. (Have you send the logs to the guys as you wrote? Didn’t get any feedback from them still?)

Ok, I kept getting a Tidal login failure as well before all this started happening, so maybe it’s the same issue.

How exactly did you delete the Tidal account from the Roon Registry?

Yes, I did send the logs but still no response!

Thanks very much for following up.

  • Exit out of Roon/Roon Server
  • Navigate to your Roon Database Location - you can also paste this in an explorer window’s address bar: %localappdata%\RoonServer\Database\Registry\Core
  • Locate your tidal_account file and delete it
  • Try to start Roon + RoonServer again
1 Like

Thank you so much! That did it! Much appreciate you taking the time to post the solution. :pray: :+1:

1 Like

Aha, I didn’t connect to Tidal afterwards, so I don’t know. I got rid of it altogether, because it just slowed things down for me and I didn’t use it much anyway.

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