Roon app on PC and iPhone stuck on "Waiting for your Roon server" post-update (ref#64RX4I)

Hi! What’s not quite right with Roon?

· Can’t reach my Server, remotes or ARC

Can’t connect to my Server, remotes or ARC

· Other ARC issues

Tell us what's going on

· After the most recent software update the Roon app on my PC and on my iPhone say "Waiting for your Roon server" and never connect to the server. I have rebooted everything but no luck.

Tell us about your home network

· Server: SonicTransporter Audiophile (Intel i5 based PC)

Hi @Ben_Toby,

Try clicking on “select a different Roon Server”, it will force Roon to perform a fresh device discovery scan.

OK. Did that and I’m getting this message:

I found my SonicTransporter on my network. It’s connected and appears normal:

I also re-booted my end point which is a MicroRendu and it is connected as well:

Hi @Ben_Toby,

Thanks for writing in and for sharing your report! Based on your account info, it looks like your Roon remote devices took the update successfully, but your SonicTransport is still running an outdated version of Roon.

Let’s see if you can force an update within the machine itself:

  1. On any device on the same network, open a browser and go to [url=http://sonicorbiter.com]sonicorbiter.com[/url] (it finds your unit locally).
  2. Click Manage next to your sonicTransporter.
  3. Go to Apps → Software Manager and click Update. Let it finish, don't reboot or power off mid-update. This updates the SonicOrbiter OS and its Roon Server package.
  4. To act directly on Roon Server itself, go to Apps → Roon Server (or Settings → Roon Server), where you can restart or reinstall Roon Server. A reinstall pulls the current version and typically clears a stuck/failed update that was blocking remotes from connecting.
After it restarts, try connecting a remote again. If remotes still won't connect, confirm the sonicTransporter and remote are on the same network/subnet, and check that no firewall or VLAN is isolating them, that's the most common cause when the server is running but unreachable. 👍

I updated the software using steps 1 to 3, but I’m still getting this message:

I haven’t made any changes which would put the SonicTransporter and the remotes on different networks or introduced any firewalls that I am aware of. I’ve been running Roon with good stability for at least a year with this exact configuration - the only change was the software update. (I’ve been a Roon customer for 5+ years - the SonicTransporter has always been the core, and I’ve used a few different servers over the years.)

@benjamin

Any further ideas as to what might be causing my problem? Is there a chance that my SonicTransporter is not compatible with the new Roon software version update?

Hi @Ben_Toby,

It looks like your ST hasn’t been in touch with our servers in 5 or so days, and without being able to capture and review a fresh diagnostic report to analyse things further its tough to say what might be happening.

Your ST should be compatible, I don’t believe there are any issues there.

If you could, please use the directions found here and send over a set of logs to our File Uploader? Once logs have been uploaded, please let us know so that we can check the server for your files, thanks!

Good morning - I just uploaded the logs to the file uploader using the instructions you provided. Thank you for your help - fingers crossed that you can help me get this resolved and I can get my Roon system up and running again!

Hi @Ben_Toby,

Unfortuantly it looks like you’ve sent over a set of Roon remote logs from the windows machine, rather than Roon Server logs from the ST:

Info: Starting Roon v2.70 (build 1671) production on windows 

You should be able to get the logs by navigating to

-> Manage -> Apps -> Roon Server

Thank you!

Hi @Ben_Toby,

Just checking in on this. Were you able to grab the logs from the Roon Server on the ST by going into MySonicorbiter and then Manage, Apps, Roon Server, instead of sending the Windows Roon Remote logs again? If you can send those server logs over, we can take another look and see what is going on.

Please note, if we don’t hear back from you this thread may close automatically soon. If the thread auto-closes and you need further assistance, please submit a reopen support request via the technical support help form below and specify that the issue should be reopened. Thank you.