Unable to connect to Roon Core on Synology

Support
1

Core Machine (Operating system/System info/Roon build number)

Linux 4.4.59+/, Verizon 1.8 (build 778) stable

Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)

Ethernet and Wi-Fi - Airport Extreme + D-Link Switch

Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)

Can’t get this far

Description Of Issue

I’ve had the Roon Core for years on a Synology; updates no problem. I use MacOS, iOS, and Windows Roon client to connect.

Since the Synology core is on auto-update, I’m not sure when it updated. I’m using the latest roon clients.

When I launch Roon (either on iOS iPhone 12 Pro) or MacOS (I haven’t rebooted into windows to try that) - I get presented with a login screen that looks like it wants to create a new core. When I enter my credentials, it says I already have my synology core and lists it, asking me to either “Go Back” and connect to it OR log out and buy a new license to create a new core.

When I “Go Back”, I see my Synology Roon Core and a “Connect” button. If I click on it, it takes me back to the login screen - looking like it wants to set up a new core.

I downloaded a new Roon package from roonlabs.com and tried it again on MacOS - same problem.

Again - has been working problem free for years. Thanks

Edit #1: From the Roon Server Log, I see the server version:

03/31 00:27:20 Info: Starting RoonServer v1.8 (build 778) stable on linuxx64
03/31 00:27:20 Trace: Checking if we are already running
03/31 00:27:20 Warn: get lock file path: /tmp/.rnsems0-roon
03/31 00:27:20 Trace: Nope, we are the only one running
03/31 00:27:20 Info: Is 64 bit? True
03/31 00:27:20 Info: Command Line Argument: -watchdogport=44016
03/31 00:27:20 Trace: [childprocess] using .NET child process
03/31 00:27:20 Trace: [realtime] fetching time from NTP server
03/31 00:27:21 Info: [broker] starting 0ad7d406-cdf8-48ad-ad5a-46818eb62ee0
03/31 00:27:21 Trace: [orbit] init seq=2223, pending=154, spcount=7, uidcount=2

Edit #2: Log messages from Server when I launch the client:
03/31 09:35:25 Info: [brokerserver] Client connected: 192.168.0.31:60419
03/31 09:35:26 Trace: SENT NONFINAL DistributedBroker.ConnectResponse={ BrokerId=0ad7d406-cdf8-48ad-ad5a-46818eb62ee0 BrokerName=‘aero’ }
03/31 09:35:26 Trace: SENT NONFINAL DistributedBroker.UpdatesChangedResponse={ IsSupported=True WasJustUpdated=False Status=‘UpToDate’ HasChangeLog=False CurrentVersion={ MachineValue=100800778 DisplayValue=‘1.8 (build 778) stable’ Branch=‘stable’ } }
03/31 09:35:26 Trace: [push] restarting connection (Unable to read data from the transport connection: interrupted.)
03/31 09:35:26 Trace: [push] retrying connection in 29822ms
03/31 09:35:27 Info: [stats] 3314mb Virtual, 1185mb Physical, 730mb Managed, 0 Handles, 55 Threads
03/31 09:35:36 Trace: Successful POST response from https://push.roonlabs.com/push/1/connect
03/31 09:35:36 Trace: [push] connecting to 104.196.205.85:9200
03/31 09:35:36 Trace: [push] connected
03/31 09:35:42 Info: [stats] 3316mb Virtual, 1187mb Physical, 733mb Managed, 0 Handles, 58 Threads
03/31 09:35:57 Info: [stats] 3317mb Virtual, 1188mb Physical, 733mb Managed, 0 Handles, 57 Threads

###and here is the associated subset of the client log. Note 320 lines in log, not posting all here:
…
03/31 09:35:26 Trace: [inetdiscovery] added service com.roonlabs.roon.api.tcp for device broker/854e639c-dd5b-438b-af77-a583b665461c
03/31 09:35:26 Trace: [inetdiscovery] added service com.roonlabs.roon.api.http for device broker/854e639c-dd5b-438b-af77-a583b665461c
03/31 09:35:26 Info: [roonapi] listening on port 9150
03/31 09:35:26 Info: [loadstatus] IsTransportLoading True => False
03/31 09:35:26 Info: [loadstatus] IsStartup True => False
03/31 09:35:26 Trace: GOT NONFINAL DistributedBroker.ConnectResponse={ BrokerId=0ad7d406-cdf8-48ad-ad5a-46818eb62ee0 BrokerName=‘aero’ }
03/31 09:35:26 Trace: [brokerclient] connected to aero (0ad7d406-cdf8-48ad-ad5a-46818eb62ee0)
03/31 09:35:26 Debug: [easyhttp] [1] GET to https://devicedb.roonlabs.net/1/devicedb-prod.zip returned after 1135 ms, status code: 304
03/31 09:35:26 Trace: [devicedb] Not Modified. Nothing to do
03/31 09:35:26 Trace: GOT NONFINAL DistributedBroker.UpdatesChangedResponse={ IsSupported=True WasJustUpdated=False Status=‘UpToDate’ HasChangeLog=False CurrentVersion={ MachineValue=100800778 DisplayValue=‘1.8 (build 778) stable’ Branch=‘stable’ } }
03/31 09:35:26 Debug: [broker/filebrowser/volumeattached] loading from mount, and volume exists already with UUID “mounted:/”. updating values /: /|Macintosh HD|AppleAPFSMedia => /|Macintosh HD|AppleAPFSMedia
03/31 09:35:26 Info: [broker/filebrowser/volumeattached] Volume’s availability changed: True
03/31 09:35:26 Debug: [broker/filebrowser/drive] availability on drive’s volume changed: True: VolumeAttached[id:mounted:/,title: Macintosh HD,subtitle:AppleAPFSMedia,mountdir:/]
03/31 09:35:26 Debug: [broker/filebrowser] getpartitioninfo 2 command: /usr/sbin/diskutil, args: info -plist ‘/dev/disk10’
03/31 09:35:26 Debug: [broker/filebrowser/volumeattached] loading from mount, and volume exists already with UUID “mounted:/Volumes/Scratch”. updating values /Volumes/Scratch: /Volumes/Scratch|Scratch|AppleAPFSMedia => /Volumes/Scratch|Scratch|AppleAPFSMedia
03/31 09:35:26 Info: [broker/filebrowser/volumeattached] Volume’s availability changed: True
03/31 09:35:26 Debug: [broker/filebrowser/drive] availability on drive’s volume changed: True: VolumeAttached[id:mounted:/Volumes/Scratch,title: Scratch,subtitle:AppleAPFSMedia,mountdir:/Volumes/Scratch]
03/31 09:35:26 Debug: [broker/filebrowser/volumeattached] initial listing found drive mounted at /Volumes/Jool
…
03/31 09:35:27 Warn: could not run /usr/sbin/diskutil info -plist ‘/Volumes/Music HD’ – Exit code was: 1
03/31 09:35:28 Debug: ev_app_init: found previously chosen broker: [object System.Guid] [is_essentials=0]
03/31 09:35:28 Info: SuspendZones
03/31 09:35:28 Info: [client/root] Broker changed null => aero (Remote Broker 0ad7d406-cdf8-48ad-ad5a-46818eb62ee0)
03/31 09:35:28 Info: [client/root] Client is acting as a remote
03/31 09:35:28 Debug: ev_app_init: showing login window
03/31 09:35:28 Debug: trigger: appinitwasnotrun
03/31 09:35:28 Debug: trigger: do nothing
03/31 09:35:31 Debug: [easyhttp] [5] POST to https://discovery.roonlabs.net/1/register returned after 34 ms, status code: 200
03/31 09:35:31 Trace: [inetdiscovery] registered 1 devices, 2 services
03/31 09:35:35 Trace: Successful POST response from https://push.roonlabs.com/push/1/connect
03/31 09:35:35 Trace: [push] connecting to 104.196.205.85:9200
03/31 09:35:35 Trace: [push] connected
03/31 09:35:41 Info: [stats] 7144mb Virtual, 302mb Physical, 35mb Managed, 53 Threads, FDs

2

If you are connected to your synology core and it is presenting you a login screen, you just got logged out.

Log back in, and it shouldn’t ask about licensing because your synology core is already licensed.

3

Agreed it should work like that. But here’s what happens.

  1. I stopped the core and macOS client
  2. I restarted the core, waited then restarted the client
  3. I hit “connect” with my core
  4. I’m at the login screen and enter my credentials
  5. The client sits on the roon waiting logo for a long time (1-2minutes)
  6. I do see login activity on the server logs
  7. Finally, the client says:

“You’re already signed in. Your subscription allows you to sign into 1 Roon Core at a time, but it looks like you’ve already set up another Core. To Connect to the Core you previously set up, just click go back above. If you want to set up a new Core, you’ll need log out the device listed below (sic) or contact us to purchase another subscription”

  1. Then it lists my “devices” with the core and “Unauthorize”.
  2. So I hit “Go Back” and I’m back to the login screen
  3. Goto Step #4

The iOS client is similar. I enter credentials, wait a long time, then it tells me I’m logged in (like message in #7 above).

4

Are you 100% sure you are connected to your synology core?

If so, just hit unauthorize. Nothing bad can happen from hitting that button.

Maybe something changed on your Synology that caused it identify as unauthorized.

5

That was it. Something so simple. Everything auto-magically started working from iOS devices as well.

Thank you!

6

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