Unifi Updates borked my Roon set up :-(

Support
1

Core Machine

Roon Core running in Docker on unRaid server (Threadripper 2950X, 96GB RAM)

Network Details

Unifi USG
Multiple Unifi Gigabit switches
Multiple Unifi Access Points

Audio Devices

Ropiee on Raspberry Pi (wired ethernet)
Roon App on MacBook Pro (wired ethernet & wifi)
Roon App on iPad (wifi)

Description of Issue

My Roon infrastructure has been running fine for at least 6 months , albeit with occasional track halts)
I recently applied pending updates to my unify devices (access points, router, switches and controller)
Subsequently, no clients can access my Roon controller.

For example, on my MacBook, I can force the Roon client to forget the Roon Core and it will find it when it searches for a new core;

Screenshot 2021-05-06 at 14.07.30
Screenshot 2021-05-06 at 14.07.30778×483 29 KB

But when I ask it to connect, I get stuck on this loading screen;

Screenshot 2021-05-06 at 14.07.40

The same thing happens on my iPad - it just gets stuck on the animated loading/connecting page…

Here’s what I’ve tried;

  • Restarted the Roon Core
  • Stopped core, removed Cache directory & restarted Core
  • Reinstalled Roon on my MacBookPro
  • Restarted client and server hardware
  • Toggled multicast and IGMP Snooping settings in my Unifi Controller
  • Tried both WiFi and Wired network connections exclusively on MacBookPro

It feels to me like something in the UniFi updates has changed some network setting that’s now blocking Roon. The Core is running and accessible on the network as evidenced from the screen grabs above as clients can find it, but cannot connect to it.

Thoughts on next steps appreciated.

2

Have you already tried and rebooted your Core and all the network devices?

3

I’ve been experiencing something similar since the Unifi update yesterday. My local library is working okay, but I’m getting various login issues with Tidal and browsing Tidal albums is very slow or not working at all. I can’t get Tidal Playlists no matter what I do.

I think I’m in a slightly better start than you in that some things are working rather than nothing at all. But it’s very clear that this started when I upgraded my Unifi switch.

I’m running on a QNAP NAS and I’ve restarted the application but it doesn’t help. My next step is to restart the NAS and then maybe some of the Unifi kit.

4

Try turning off IPS if you have it enabled.

5

Yes, as indicated in OP I have Restarted client and server hardware

6

IPS / Threat Management is OFF in Unifi (hasn’t been ON)

7

Looks like it’s running on Linux, do you know how to tail log files?

Connect to it via SSH and run:

sudo tail -f /var/roon/RoonServer/Logs/RoonServer_log.txt

Try to connect the client and look for any errors or failures.

1 Like
8

Thanks

05/06 17:12:21 Info: [stats] 3947mb Virtual, 447mb Physical, 162mb Managed, 0 Handles, 37 Threads
05/06 17:12:36 Info: [stats] 3947mb Virtual, 447mb Physical, 162mb Managed, 0 Handles, 37 Threads
05/06 17:12:42 Info: [brokerserver] Client connected: 192.168.1.170:52408
05/06 17:12:43 Trace: SENT NONFINAL DistributedBroker.ConnectResponse={ BrokerId=5f9b6035-b141-4408-9dfe-29fb19809dc8 BrokerName='UNRAID' }
05/06 17:12:43 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/06 17:12:43 Trace: [push] restarting connection (Unable to read data from the transport connection: interrupted.)
05/06 17:12:43 Trace: [push] retrying connection in 52955ms
05/06 17:12:48 Debug: [easyhttp] [20] GET to https://messaging.roonlabs.net/1/api/messages/2225cdde-15fc-4abb-9b5d-a8b01d05d1c9 returned after 499 ms, status code: 200
05/06 17:12:51 Info: [stats] 3947mb Virtual, 448mb Physical, 163mb Managed, 0 Handles, 45 Threads
05/06 17:12:53 Trace: Successful POST response from https://push.roonlabs.com/push/1/connect
05/06 17:12:53 Trace: [push] connecting to 35.237.106.222:9200
05/06 17:12:53 Trace: [push] connected
05/06 17:13:06 Info: [stats] 3950mb Virtual, 448mb Physical, 163mb Managed, 0 Handles, 47 Threads
05/06 17:13:21 Info: [stats] 3951mb Virtual, 449mb Physical, 164mb Managed, 0 Handles, 46 Threads
05/06 17:13:25 Info: [brokerserver] Client disconnected: 192.168.1.170:52408
05/06 17:13:25 Trace: [push] restarting connection (Unable to read data from the transport connection: interrupted.)
05/06 17:13:25 Trace: [push] retrying connection in 53966ms
05/06 17:13:36 Info: [stats] 3951mb Virtual, 449mb Physical, 164mb Managed, 0 Handles, 44 Threads
05/06 17:13:36 Trace: Successful POST response from https://push.roonlabs.com/push/1/connect
05/06 17:13:36 Trace: [push] connecting to 35.237.106.222:9200
05/06 17:13:36 Trace: [push] connected
05/06 17:13:51 Info: [stats] 3951mb Virtual, 449mb Physical, 164mb Managed, 0 Handles, 43 Threads
05/06 17:14:06 Info: [stats] 3951mb Virtual, 449mb Physical, 164mb Managed, 0 Handles, 42 Threads
05/06 17:14:21 Info: [stats] 3951mb Virtual, 449mb Physical, 164mb Managed, 0 Handles, 41 Threads
05/06 17:14:36 Info: [stats] 3951mb Virtual, 449mb Physical, 164mb Managed, 0 Handles, 40 Threads

17:12:42 is where I launch Roon on my MacBookPro and it finds the Roon Core. I then click ‘Connect’
17:13:25 is where I quit the Roon client on the MBP.

(no matter how long I leave it, the client never moves from the ‘connecting’ screen)

9
  • Did you update the controller or the FW on said devices or both?
  • If so what version(s) did you update from > to?
  • what is your controller running on?
10

Weird I’d expect to see the raatserver register the client once it is connected and start setting up the devices.

Do you see any entries for raatserver in the roonserver log file?

11

what do you get for:

sudo service roonserver status

12

Following up on my post earlier - a full NAS reboot has fixed this for me.

13

Both device FW and controller.
I did device FW first, and the problem arose. I updated controller afterwards.
Controller is now on 6.1.71 (don’t know what it was on before, but pretty recent)
All devices are up to date as of writing.
Controller is running in a Docker on unRaid

14

Only these lines when the Roon core started up > 4 hours ago. No other references to 'Raat’in the log file;

05/06 14:07:18 Trace: [devicedb] initializing
05/06 14:07:18 Info: [raatserver] [runner] Start or Connect...
05/06 14:07:18 Info: [raatserver] [runner] Start or Connect... /app/RoonServer/Appliance/RAATServer
05/06 14:07:18 Info: ConnectOrStartAndWaitForExit RAATServer, path: /app/RoonServer/Appliance/RAATServer
05/06 14:07:18 Info: [raatserver] [runner] Status: Started
05/06 14:07:18 Info: [loadstatus] IsLibraryLoading True => True
15 
# service roonserver status
roonserver: unrecognized service
16

what version of linux are you using?

If you run this can you see roonserver.service in the list?

systemctl list-units --type service

17

First, I appreciate the patience and help here.

unfortunately, it’s not that straightforward. As my Roon Core is running in a Docker, many of these commands wont work as System MD is not loaded. The Docker base image is some version of Ubuntu, I believe, but that shouldn’t really matter too much - all of this has been working and there have been no recent updates made to the Roon server. It really looks like its my network thats the issue, not my Roon.

In any case, I tried restarting the underlying server once more as per @Jamie_Tudor 's post, above.

Lo and Behold, I now get access to my roon server from clients, though none of my deveices are showing up. At least my client device should be listed here, right???

Screenshot 2021-05-06 at 19.23.52
Screenshot 2021-05-06 at 19.23.521513×981 62 KB

18

Ah I have no idea how Roon works in docker.

I believe that raatserver adds the devices which was I was trying to see if it had loaded correctly, looks like your client connects ok but raatserver doesn’t seem to discover the client devices (or try to)

Beyond redeploying I’m probably no help now

19

Thanks anyway.

I have a plan to rebuild this server and will likely install Roon Core on a standalone system so we’ll see how that goes. Will be without music for a few weeks though, so it’s Spotify for me.

20

Apologies for the delay, @Meep2020! Our team’s queue is longer than typical at the moment, but we’re working to get back to everyone as quickly as we can.

Are you still seeing any issues here? Were you able to get Roon set up in the new configuration you mentioned? Are things working for you with that setup?