Remotes show 'Waiting for your Roon Server' with slow performance (ref#7GJ4YY)

What app are you having the slowness issue with?

· Roon

What kind of performance/speed issue are you experiencing?

· Other

Please try to reboot your Roon Server

· No, the issue is still the same even immediately after a reboot

Please try to reboot your networking gear (Router/Switches/etc.)

· No, the issue is still the same even after a reboot

Is there any change in behavior if you try to navigate to Roon Settings -> Library and set both Background and On-Demand Audio Analysis to Throttled or Off?

· No, the issue is still the same

Does the issue happen on multiple Roon Remotes (controllers) or just one?

· Issue happens on multiple remotes

Router Domain Name System (DNS) change

· I was able to change my router's DNS servers but it did not help

What is the operating system of your Roon Server host machine?

· MacOS

Timestamp of issue occurrences

· Every time app starts - May 9 at 2:08am CT

Describe the issue

Remotes show “Waiting for your Roon Server” / other slow performance

Describe your network setup

Unifi UCG Max v4.1.22; Unifi U7 Pro Wall v8.0.19; 1GBe bidirectional WAN

A bit more detail:

Roon server on Mac Mini - hardwired to UCG

Remotes on WiFi connect via U7 Pro Wall
Remotes showing this issue include iPhone, iPad, and MacOS.

Playback to Naim MU-SO II - via WiFi / AirPlay 2

Hello @Monty_Kosma,

Thank you for reaching out to Roon support. It’s nice to see you again in our community.

macOS Sequoia (version 15), has tighter (and more obfuscated) network security settings than preceding MacOS versions.

Can you please navigate to macOS System Settings > Privacy & Security > Local Network, and make sure Roon is allowed.

If it is already enabled, toggle it off and on again. Then reboot your Mac, and see if the same issue persists.

No change after doing that.

Roon remote also seems slow on the server Mac mini.

Arc is also taking a long time - 20-30 seconds - to start playing after hitting play. And that’s on WiFi that is running > 400 Mbps (6Ghz).

Hi @Monty_Kosma ,

Can you kindly provide a few examples of the exact local time + date + remote being used when you next notice this behavior? We’ll enable diagnostics mode to see if there are any clues in the logging, thanks!

I have a few timestamps and logs from my testing before I created the support ticket. These timestamps are from the logs that I captured on my iPhone using the switch to save the logs next time the app starts. I can just send you those if you like. The behavior happens all the time on my iPhone, as well as other devices.

(US Central Time)
05/03/2025 16:29:52-16:39:27

also repeated every 10-20 minutes before that as I kept trying it under different conditions, restarting remote, server, etc.

I see the setsockopt warning occasionally, but the big one is the segment shown afterward (in the same iOS app launch sequence).

05/03 16:29:52 Info: [RAATServer] [jsonserver] listening on port 9200
05/03 16:29:52 Trace: [RAATServer] [raatmanager] announcing
05/03 16:29:52 Warn: setsockopt failed (ttl) failed: Value does not fall within the expected range.
05/03 16:29:52 Trace: [remoting/distributedbroker] Enabling remote broker tracking
05/03 16:29:52 Trace: [brooengine] Loaded atlas list. 3ms
05/03 16:29:52 Trace: [brooengine] Window is running in scale 3
05/03 16:29:52 Trace: [brooengine] Using atlas scale 2
05/03 16:29:52 Debug: [RAATServer] [discovery] broadcast op is complete

then

05/03 16:29:54 Trace: [RAATServer] [raatmanager] announcing
05/03 16:29:54 Debug: [RAATServer] [discovery] broadcast op is complete
05/03 16:29:55 Warn: frame took 19.78ms! 16.67ms preframe, 0.00ms safe queue, 0.02ms timers, 0.00ms frame calls, 0.02ms update, 19.78ms render
05/03 16:29:55 Info: [stats] iOS memory usage: 443 mb
05/03 16:29:56 Info: [stats] iOS memory usage: 444 mb
05/03 16:29:57 Debug: ev_app_init: showing disconnected core screen
05/03 16:29:57 Warn: AddTopLevel: win_disconnected_broker(127)
05/03 16:29:57 Debug: Created new font texture with id: 4
05/03 16:29:57 Info: [stats] iOS memory usage: 447 mb
05/03 16:29:58 Info: [stats] iOS memory usage: 450 mb
05/03 16:29:59 Info: [stats] iOS memory usage: 454 mb
05/03 16:30:00 Info: [stats] iOS memory usage: 457 mb
05/03 16:30:01 Warn: frame took 28.25ms! 18.43ms preframe, 0.00ms safe queue, 0.03ms timers, 0.00ms frame calls, 1.72ms update, 28.25ms render
05/03 16:30:01 Info: [stats] iOS memory usage: 461 mb
05/03 16:30:02 Info: [stats] iOS memory usage: 461 mb
05/03 16:30:02 Debug: [easyhttp] [3] GET to https://api.roonlabs.net/push-manager/1/connect returned after 118 ms, status code: 200, request body size: 0 B
05/03 16:30:02 Debug: [push2] push connector url received from push manager: ws://push-connector-v2-1.prd-roonlabs-1.prd.roonlabs.net/
05/03 16:30:02 Trace: [push2] connecting to push2 connector at ws://push-connector-v2-1.prd-roonlabs-1.prd.roonlabs.net/
05/03 16:30:03 Trace: [push2] connected to push2 connector at ws://push-connector-v2-1.prd-roonlabs-1.prd.roonlabs.net/
05/03 16:30:03 Debug: [easyhttp] [4] POST to https://api.roonlabs.net/device-map/1/register returned after 57 ms, status code: 200, request body size: 566 B
05/03 16:30:03 Trace: [devicemap] device map updated
05/03 16:30:04 Info: [stats] iOS memory usage: 464 mb
05/03 16:30:06 Info: [stats] iOS memory usage: 471 mb
05/03 16:30:08 Info: [stats] iOS memory usage: 478 mb
05/03 16:30:10 Trace: [remoting/remotebrokerv2] [Montys-Mac-mini] Authenticating => Connected
05/03 16:30:10 Info: [client/root] Broker changed null => Montys-Mac-mini (Remote Broker 22354105-a6d3-430c-a4c8-769766cdf7b4)
05/03 16:30:10 Info: [client/root] Client is acting as a remote
05/03 16:30:10 Info: [client/root] Broker ready changed False => True

Please let me know if you’d like me to upload the log zip file(s), and remind me how to do that.

If you need a more recent timestamp, I’ll start the app right now…

7:03p CT on 05/13/2025
Took 9-10 seconds to get from clicking the icon to the Now Playing screen.

monty

Hi @Monty_Kosma,

Thanks for the above info!

From your admin, we’re seeing a second Roon Server, on a different local subnet, potentially, running Early Access - a few follow-up questions for you:

  1. Are you running multiple subnets within your local network?
  2. Do you see the same issues on this other server running Early Access?

We’re seeing some network realted failures that could be playing a role in the behavior you’re experiencing:

Warn: [discovery] got send failure: network is unreachable
Warn: [inetdiscovery] failed to register: Result[Status=NetworkError]
Trace: [RAATServer] network reachability changed, refreshing discovery

I’d look at simplifying your network topology overall, and see if you experience the same issues with a simple Ethernet connection from your Server directly to your primary router. Let me know if you run into the same behavior! :raised_hands:

I have no subnets. My topology could not be simpler.

I have the gateway, and one hardwired WAP, and one hardwired Mac Mini which is the Roon server

You may be right that there is some other ghost process on one of my computers. What can you tell me about the other? Version or anything? How to find and kill it?

Sometimes my Roon cannot find any music devices. Usually I have to kill and restart the server.

It does this on a fresh reboot sometimes so I bet there is a second process starting somehow.

Hi @Monty_Kosma,

I have unlisted this thread to keep all the information private between you and Roon staff :+1:

Your admin indicates you’re running Roon Server on a MacBook Pro 13-inch, 2020 running Mac OS X 14.5.0.

The second subnet this server is running on appears to be: 10.10.1.yyy

With an early access version of Roon running (build 1535) earlyaccess.

Meanwhile, your Mac Mini running Roon Server is tied to a 192.168.1.xx IP.

You can always see if Roon Server is running on a Mac via the taskbar in the upper right hand corner - you can typically click the Roon jellyfish and quit the application.

Okay - found that laptop, in a home where I used to live and had it set up. It was just on the network not being used. I’ve uninstalled Roon / Roon Server from that laptop and rebooted it.

I also restarted my local Mac Mini Roon server.

And … wow, much improved! Thank you!

I am puzzled how packets were getting from that remote LAN to my local LAN, or if the hangup was somehow occuring in the Roon cloud. But that’s just curiosity….

monty

1 Like

Hey @Monty_Kosma,

Odd indeed! None the less, I’m happy to hear things have improved for you - happy listening! :drum: :notes:

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