Cannot connect to the Roon Core running on DS920 after upgrade to build 795

After upgrading to 1.8 build 795, suddenly I can no longer connect to the Core running on DS920.
Click connect will ask me to login. However, when I use the account / password to log in, then it will says that I’ve already had 1 device logged in. I have to unauthorizes it.
Is this a known issue?

Can anyone help with it? Thanks

Some logs like this

05/20 23:33:17 Trace: Successful POST response from https://push.roonlabs.com/push/1/connect
05/20 23:33:17 Trace: [push] connecting to 35.237.106.222:9200
05/20 23:33:18 Trace: [push] connected
05/20 23:33:20 Info: [stats] 2922mb Virtual, 787mb Physical, 361mb Managed, 0 Handles, 47 Threads
05/20 23:33:35 Info: [stats] 2922mb Virtual, 787mb Physical, 364mb Managed, 0 Handles, 46 Threads
05/20 23:33:50 Info: [stats] 2922mb Virtual, 787mb Physical, 367mb Managed, 0 Handles, 46 Threads
05/20 23:34:05 Trace: [push] restarting connection (Unable to read data from the transport connection: interrupted.)
05/20 23:34:05 Trace: [push] retrying connection in 20074ms
05/20 23:34:05 Info: [stats] 2922mb Virtual, 787mb Physical, 370mb Managed, 0 Handles, 45 Threads
05/20 23:34:15 Trace: Successful POST response from https://push.roonlabs.com/push/1/connect
05/20 23:34:15 Trace: [push] connecting to 35.237.106.222:9200
05/20 23:34:15 Trace: [push] connected
05/20 23:34:20 Info: [stats] 2922mb Virtual, 787mb Physical, 374mb Managed, 0 Handles, 48 Threads
05/20 23:34:35 Info: [stats] 2922mb Virtual, 787mb Physical, 377mb Managed, 0 Handles, 46 Threads
05/20 23:34:49 Trace: [push] restarting connection (Unable to read data from the transport connection: interrupted.)
05/20 23:34:49 Trace: [push] retrying connection in 49945ms
05/20 23:34:50 Info: [stats] 2922mb Virtual, 787mb Physical, 380mb Managed, 0 Handles, 46 Threads
05/20 23:34:59 Trace: Successful POST response from https://push.roonlabs.com/push/1/connect
05/20 23:34:59 Trace: [push] connecting to 35.237.106.222:9200
05/20 23:34:59 Trace: [push] connected
05/20 23:35:05 Info: [stats] 2922mb Virtual, 787mb Physical, 383mb Managed, 0 Handles, 49 Threads
05/20 23:35:20 Info: [stats] 2922mb Virtual, 787mb Physical, 387mb Managed, 0 Handles, 47 Threads
05/20 23:35:35 Info: [stats] 2922mb Virtual, 787mb Physical, 390mb Managed, 0 Handles, 47 Threads
05/20 23:35:50 Info: [stats] 2922mb Virtual, 787mb Physical, 393mb Managed, 0 Handles, 47 Threads
05/20 23:35:59 Debug: [broker/filebrowser/drive] GetEntries: doing LsDir of  Synology DS920+ DS920, 2090SBRY4T4XM, DSM 6.2.4, /
05/20 23:36:05 Info: [stats] 2922mb Virtual, 787mb Physical, 396mb Managed, 0 Handles, 47 Threads
05/20 23:36:08 Info: [brokerserver] Client disconnected: 192.168.68.99:65505
05/20 23:36:08 Trace: [push] restarting connection (Unable to read data from the transport connection: interrupted.)
05/20 23:36:08 Trace: [push] retrying connection in 85100ms
05/20 23:36:18 Trace: Successful POST response from https://push.roonlabs.com/push/1/connect
05/20 23:36:18 Trace: [push] connecting to 35.237.106.222:9200
05/20 23:36:18 Trace: [push] connected
05/20 23:36:20 Info: [stats] 2924mb Virtual, 787mb Physical, 399mb Managed, 0 Handles, 49 Threads
05/20 23:36:35 Trace: [broker/accounts] [heartbeat] now=5/21/2021 6:36:35 AM nextauthrefresh=5/21/2021 7:31:35 AM nextmachineallocate=5/21/2021 10:31:35 AM
05/20 23:36:35 Info: [stats] 2924mb Virtual, 787mb Physical, 403mb Managed, 0 Handles, 48 Threads
05/20 23:36:50 Info: [stats] 2925mb Virtual, 787mb Physical, 405mb Managed, 0 Handles, 46 Threads
05/20 23:37:01 Info: [brokerserver] Client connected: 192.168.68.99:49341
05/20 23:37:02 Trace: SENT NONFINAL DistributedBroker.ConnectResponse={ BrokerId=0d6469ef-4b72-4394-92aa-c1cda8d2394f BrokerName='DS920' }
05/20 23:37:02 Trace: SENT NONFINAL DistributedBroker.UpdatesChangedResponse={ IsSupported=True WasJustUpdated=False Status='UpToDate' HasChangeLog=False CurrentVersion={ MachineValue=100800795 DisplayValue='1.8 (build 795) stable' Branch='stable' } }
05/20 23:37:02 Trace: [push] restarting connection (Unable to read data from the transport connection: interrupted.)
05/20 23:37:02 Trace: [push] retrying connection in 36136ms
05/20 23:37:03 Debug: [easyhttp] [26] GET to https://messaging.roonlabs.net/1/api/messages/ returned after 344 ms, status code: 500
05/20 23:37:05 Info: [stats] 2929mb Virtual, 791mb Physical, 411mb Managed, 0 Handles, 47 Threads
05/20 23:37:12 Trace: Successful POST response from https://push.roonlabs.com/push/1/connect
05/20 23:37:12 Trace: [push] connecting to 35.237.106.222:9200
05/20 23:37:12 Trace: [push] connected
05/20 23:37:20 Info: [stats] 2933mb Virtual, 796mb Physical, 414mb Managed, 0 Handles, 49 Threads
05/20 23:37:35 Info: [stats] 2937mb Virtual, 800mb Physical, 417mb Managed, 0 Handles, 48 Threads
05/20 23:37:50 Info: [stats] 2940mb Virtual, 803mb Physical, 419mb Managed, 0 Handles, 46 Threads
05/20 23:38:05 Info: [stats] 2944mb Virtual, 807mb Physical, 423mb Managed, 0 Handles, 46 Threads
05/20 23:38:07 Trace: [broker/images] Checking for image updates
05/20 23:38:07 Critical: scx: System.NullReferenceException: Object reference not set to an instance of an object
  at Sooloos.Broker.ImageCollection._UpdateImages () [0x000bd] in <f5946fdae6544d939fe69f2eca825652>:0 
  at Sooloos.Broker.ImageCollection+<>c__DisplayClass16_0.<Init>b__0 () [0x00014] in <f5946fdae6544d939fe69f2eca825652>:0 
  at Sooloos.CallingThread+<>c__DisplayClass18_0.<AddOneShotTimer>b__1 () [0x00000] in <7355f3f0ed474ae2968a5532637edf8d>:0 
  at Sooloos.CallingThread+<>c__DisplayClass12_0.<Post>b__1 (System.Object <p0>) [0x00000] in <7355f3f0ed474ae2968a5532637edf8d>:0 
  at Sooloos.SynchronizationContextThread._Dispatch (Sooloos.SynchronizationContextThread+SendOrPostWrapper& ret) [0x00012] in <7355f3f0ed474ae2968a5532637edf8d>:0 
05/20 23:38:20 Info: [stats] 2948mb Virtual, 810mb Physical, 425mb Managed, 0 Handles, 45 Threads
05/20 23:38:35 Info: [stats] 2952mb Virtual, 814mb Physical, 429mb Managed, 0 Handles, 45 Threads
05/20 23:38:50 Info: [stats] 2955mb Virtual, 818mb Physical, 432mb Managed, 0 Handles, 45 Threads
05/20 23:39:05 Info: [stats] 2959mb Virtual, 822mb Physical, 435mb Managed, 0 Handles, 45 Threads
05/20 23:39:20 Info: [stats] 2963mb Virtual, 825mb Physical, 438mb Managed, 0 Handles, 44 Threads
05/20 23:39:35 Info: [stats] 2966mb Virtual, 829mb Physical, 441mb Managed, 0 Handles, 44 Threads
05/20 23:39:50 Info: [stats] 2970mb Virtual, 833mb Physical, 444mb Managed, 0 Handles, 44 Threads
05/20 23:40:05 Info: [stats] 2974mb Virtual, 836mb Physical, 447mb Managed, 0 Handles, 43 Threads
05/20 23:40:20 Info: [stats] 2977mb Virtual, 841mb Physical, 450mb Managed, 0 Handles, 43 Threads
05/20 23:40:35 Info: [stats] 2981mb Virtual, 844mb Physical, 454mb Managed, 0 Handles, 43 Threads
05/20 23:40:50 Info: [stats] 2985mb Virtual, 847mb Physical, 457mb Managed, 0 Handles, 43 Threads
05/20 23:41:05 Info: [stats] 2988mb Virtual, 851mb Physical, 460mb Managed, 0 Handles, 43 Threads
05/20 23:41:20 Info: [stats] 2992mb Virtual, 855mb Physical, 463mb Managed, 0 Handles, 42 Threads

The problem exists after one night

Yes, I have exactly the same problem.

It turns out after the login session, I should ‘unauthorize’ the existing entry. I think somehow the system thought the same device logins twice and blocked it.

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