Roon Mac OS X client cannot connect to Server after 1/15/2025 update (ref#UF5ORW)

What’s happening?

· I'm having trouble connecting to Roon

What type of connection issue?

· Something else

How can we help?

· None of the above

Other options

· Other

Describe the issue

Roon Mac OS X client cannot connect to Server after update around 1/15/2025

Describe your network setup

Cisco RV340/Cisco Business Switches/AC Access points and mesh extenders

Hello I think I kind of botched the support form - sorry I wasn’t paying enough attention. More details

  • Happened after latest Roon Server update.
  • No changes in anything from working condition - that is, basically, roon server update was the only thing changed in the setup, then it stopped working
  • Running on ubunt 24.04 server, Client on Mac OS X Sequoia 15.2, Mac Mini M1 2020. 16GB, Firewall inactive, tested both wired and wireless.
  • UPDATE AFTER CREATING TICKET - just occurred to me to check other devices - working fine from Samsung phone on the same network.
  • Roon Client
  • Restarting the server makes the client find the server but still unable to connect, as depicted in the screenshot
  • Endpoints connect to server no issue

Hey @vmartell,

Thanks for writing in and sharing your report! Odd you’re only seeing the issue/blockage from the Mac. Let’s see if refreshing your Roon instance on the Mac may help:

  • Exit out of Roon
  • Navigate to your Roon Database Location
  • Find the folder that says “Roon”
  • Rename the “Roon” folder to “Roon_old”
  • Reinstall the Roon App from our Downloads Page to generate a new Roon folder

Let me know if you’re still not able to connect after the above. :+1:

Might be the same issue. Is re-installing the only advice? Seems extreme and time consuming, so confirming

[EDIT: got - I misread the advice - thought it was to re-install the server, not the client - doing]

Performed the update today. Roon server didn’t “see” any Roon endpoints. Had to reboot my Mac. After doing so Roon suddenly detected all of my network endpoints once again.

Ok, just to try something before following instructions above, I let the client wait, just to see what happened. After 20 minutes, it actually connected to the Roon Server and the problem hasn’t happened again.

1.- Do you still recommend to follow the procedure (clear up and reinstall) anyway?

2.- What was the client doing all that time it couldn’t connect?
(I ask, because the Android client connected at the same time, no problem, no wait, so it was the Mac OS X client the one doing something, right?)

BUMP! Any recommendations? Answer to the question? After doing what I described above the issue did not reoccur. DO YOU STILL RECOMMEND TO CLEAR AND RE-INSTALL?

Hi @vmartell,

Thank you for your patience!

It wont hurt anything and you won’t lose any saved settings, but if you’re not experiencing any connection issues at this time you can skip the database refresh.

We see repeated failures in attempting to connect to your network, but we can’t pinpoint the specific timeline for additional details, unfortunately.

Are you still having issues at this time? If your connection is functioning properly, feel free to mark your response as a solution and we’ll close out the ticket.

Let us know, thank you! :+1:

Unfortunately, NO. It failed again, same symptoms. Proceeded to to the remove Library and re-install. Worked right exactly ONCE. Android app on the same network still works. Again ISSUE STILL VERY MUCH PRESENT.

Update after a shutdown of the Mac Mini, it is able to connect again. I won’t be marking this as a solution until I am sure it doesn’t re-occur. If you have other suggestions in the meantime, they will be appreciated

After reboot of the Mac problem reoccurs - I can safely say that removing the Library and re-installing did nothing. Any ideas? This is annoying.

BUMP
Any ideas? Having work on the phone is not an option - Need the Mac client functionality

Going from worse to worse - it just went from working sporadically to just NEVER working.
The client log is incredibly silent, so I have no way of even trying to find out what is wrong:

01/21 00:09:30 Warn: [1] [rnet/RnetJsonClient] failed to connect No route to host
01/21 00:09:30 Trace: [1] [client/roonbridges] [RoonBridge remote-endpoint @ 192.168.1.100:34457] connecting (attempt 5)
01/21 00:09:30 Warn: [1] [rnet/RnetJsonClient] failed to connect No route to host
01/21 00:09:30 Trace: [1] [client/roonbridges] [RoonBridge desktop-endpoint @ 192.168.1.199:33249] client connection failed. Giving up
01/21 00:09:30 Trace: [1] [client/roonbridges] [RoonBridge remote-endpoint @ 192.168.1.100:34457] client connection failed. Giving up
01/21 00:09:35 Warn: [1] frame took 20.10ms! 19.38ms preframe, 0.00ms safe queue, 0.00ms timers, 0.00ms frame calls, 3.73ms update, 20.10ms render
01/21 00:09:40 Info: [10] [stats] 405383mb Virtual, 334mb Physical, 157mb Managed

Help - I was not able to use my roon setup during the holiday weekend - that is just wrong; the phone display is too small for me, I HAVE TO USE THE MAC CLIENT.

pls help

BUMP - Same situation - would like to get some help before resorting to extreme measures like re-installing the server.

Well, while very upset that his matter was apparently dropped - the customer should not be the only person updating the thread. Will probably try to communicate with Roon (and or the new overlords) re: this.

THAT SAID, I think I found the cause of the issue. The Mac that I have is my ONLY Mac - so I use it both for development AND general computing purposes. And because of that I have both VirtualBox and VMWare Fusion installed on this machine. When trying to debug this (because, again, no help was forthcoming) I realized the number of tunnels and bridges those products create. The client was probably confused with those - at least that was my hypothesis.

Not wanting to continue living in debug hell with no support, I just uninstalled both products. It has been a day, and so far so good. If I hit a week with no issues, will declare this handled.

I won’t be marking it as a solution as nothing was solved. Destroying your setup is not a valid/acceptable “solution”

Hi @vmartell ,

Thank you for sharing your detailed findings. I understand how frustrating it can be when support feels lacking and configurations interfere with your workflow. As you discovered, having VirtualBox and VMware Fusion installed on your only Mac can create network tunnels and bridges that confuse Roon, and since VMs aren’t officially supported, this configuration can lead to issues like the ones you experienced.

I’m glad to hear that uninstalling those products appears to have stabilized your system so far. Please let us know if everything is still working smoothly since making those changes, or if you have encountered any further issues.

I appreciate the feedback. I will change tacks and mark it as a solution in the unlikely case someone else is crazy enough to run all that together. Thanks!

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