Android phone can no longer find core

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

Ubuntu Server 20.04 LTS, Roon Build 783

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

Fios-G1100 Router, Core on ethernet, phone on WiFi. Core at, phone at

Description Of Issue

I very recently installed Roon and it had been great, and I had no problems connecting from my Android phone. I’m very happy with it, and wanted to run it alongside my other services, so I backed up my roon and got roon running in docker.

I restored from my backup, fixed my storage mappings, and tested it on my Windows and Mac laptops, and they are working great and able to connect, just like before. But when I try connecting on my Android (OnePlus 7T) phone, it’s no longer able to find the core.

I figured that this could have been the result of putting roon in docker, so went back to the standard installation (exactly how I had installed it the first time) and restored from the backup, and ended up having the same exact problem. I’ve tried manually entering the IP of my core as well as the 255 trick, all to no avail. I’ve reinstalled the app and restarted the server, my phone, and my router, again with no success.

I tailed the logs from /var/roon/RoonServer/Logs and noticed this every time I opened the app on my phone.

04/05 22:46:31 Info: [raatserver] GOT SERVER REDACTED::REDACTED @ HD1905 PROTOVER=1 RAATVER=1.1.38
04/05 22:46:31 Trace: [push] restarting connection (Unable to read data from the transport connection: interrupted.)
04/05 22:46:31 Trace: [push] retrying connection in 42873ms
04/05 22:46:31 Trace: [raatserver] [RaatServer HD1905 @] connecting (attempt 1)
04/05 22:46:31 Trace: [raatserver] [RaatServer HD1905 @] connected
04/05 22:46:31 Trace: [rnet/RnetJsonClient] SENT {"request":"enumerate_devices","subscription_id":"0"}
04/05 22:46:31 Trace: [rnet/RnetJsonClient] GOT NONFINAL {"status": "Success", "devices": [{"device_id": "default", "is_system_output": true, "type": "android", "name": "Default Output", "auto_enable": true, "auto_name": "HD1905"}]}
04/05 22:46:31 Info: [raatserver] GOT DEVICE REDACTED::default Type=android Name=Default Output
04/05 22:46:32 Info: [brokerserver] Client connected:
04/05 22:46:32 Trace: [raat] [sood] Refreshing device list
04/05 22:46:32 Trace: [raatserver] [sood] Refreshing device list
04/05 22:46:32 Debug: [easyhttp] [201] POST to returned after 120 ms, status code: 200
04/05 22:46:32 Debug: [easyhttp] [200] POST to returned after 123 ms, status code: 200
04/05 22:46:32 Trace: SENT NONFINAL DistributedBroker.ConnectResponse={ BrokerId=REDACTED BrokerName='core' }
04/05 22:46:32 Trace: SENT NONFINAL DistributedBroker.UpdatesChangedResponse={ IsSupported=True WasJustUpdated=False Status='UpToDate' HasChangeLog=False CurrentVersion={ MachineValue=100800783 DisplayValue='1.8 (build 783) stable' Branch='stable' } }
04/05 22:46:33 Info: [brokerserver] Client disconnected:
04/05 22:46:36 Info: [stats] 2750mb Virtual, 596mb Physical, 229mb Managed,

I stumbled across some related issues, but the suggested 255 fix didn’t work for me. Pixel2 will not find roon core also seemed potentially relevant, but I didn’t find any IGMP settings in my router.

At this point I’m kind of at a loss and I’m not super sure what the issue might be. Any idea what could be happening here?

Aaaaand it’s magically working this morning. Not sure exactly what happened so I don’t want to close this just yet but at least it’s working now.

I’m glad to hear it’s working at the moment, @nolem! If you see any issues return please do let us know!