Roon Remote Constantly Shows "Waiting for Roon Server" Status (ref#439VUL)

Full form submission

What’s happening?

· Something else

How can we help?

· None of the above

Other options

·


Describe the issue

This is a new setup, new hardware, new Roon install in Windows 10 machine, fresh download, Roon Server and Roon Client (aka. Roon Remote) both runs on the "same" PC. Everything works fine, except this observation, in setting, About, Roon Remote keeps/constantly shows "Waiting for Roon Server...". Why is this? Roon Server is showing (on This PC), status of running. And shows the correct Roon Server version. And says "You have the latest version installed." The Roon Remote shows Roon version 2.0 (build 1401) production (64bit). And Roon Server version 2.0 (build 1401) production (does not say it's 64bit though, which is weird).

Did you add Roon and roonserver to the windows firewall exceptions?

What @ged_hickman1 said.

I would also turn on the “Launch at startup” option for your Roon Server by checking the option in the menu shown in your screenshot, otherwise the next time you reboot your PC, Roon Server will not start automatically.

The Firewall exceptions that you need are listed here:

Thanks.

I believe we can rule out the firewall as the culprit, since as a quick fix test (closed all Roon, disabled firewall and restarted Roon server/client), completely disabled Windows 10 firewall. Result is the same. What is happening here? Need to resort to Roon logs to dig deeper? I don’t see any negative consequence(s) from this though.

Also, since we are at the topic of the Windows firewall setting per the Roon KB mentioned above, this KB needs some update. Why? Because the process exceptions are outdated.

When i installed the Roon (rant: i much preferred the earlier Roon setup, where client and server was kept separate, i.e. Roon Core and the Roon client - now we have single download that “forces” you to install both client and server on a given PC), the setup prompted me “twice” to add the firewall exceptions. I did not pay attention to the processes. But looking at the processes that are added by the setup in this PC, which has both client and server installed, following is shown in the firewall exceptions table,

What Roon KB says about the exceptions:

image

Actual exceptions after the clean setup install of Roon (client and server) in Windows 10 PC,

image

image

image

image

In the Roon Server Application folder, there is BOTH the RAATserver.exe and the RoonServer.exe, but the Roon setup program only added the RAATserver.exe to the allowed list. But also interestingly there is TWO of raatserver.exe processes listed there.

What is this Roon KB actually saying as far as WHAT all the processes that OUGHT to be in the allowed list for Roon client and server installs? And the Roon Bridge install?

Also, in the Roon Bridge PC (separate PC), the exceptions created in firewall there is “not” what this KB says, i.e. there is no roonbridge.exe, but instead roonbridgehelper.exe process.

image

image

image

Roon needs to get this particular KB updated and make clear how these process exceptions ought to show in Windows 10/11 firewall’s allowed apps table. Because in current form this KB is “not” accurate.

More specifically, are ALL of the EXE’s in the Application folder supposed to be added into the allowed apps table? Because even the Roon install setup did NOT do that. And seem okay, operational wise. But i don’t know where the side effect can show up in, if i do NOT have ALL of the application EXE’s added to the allowed apps list.

Is that the only RoonServer active in your network?

Hi @George_Shin,

Thanks for taking the time to write in, and we appreciate the feedback on our firewall KB! Our team was able to take a closer look into your inquiry, and are curious, have you performed a full restart of your Windows machine since updating Roon?

Give it a try and let me know if you still see this in the About tab afterwards. :+1:

Just so that i’m clear about the ask above, are you asking if the PC was rebooted since the last Roon “update”, and not reboot after the “initial” setup install?

I did reboot after the “initial” setup install. But the PC did “not” reboot since the last “update”. I will do that shortly.

And just so that i know what the best practice is, should the Windows PC be rebooted after “each” Roon “updates” ?

No difference, refer to below A/B screenshots,

Before reboot:

After reboot:

Hi @George_Shin,

Correct!

No, not necessarily. If you’re experiencing some odd behavior, a full reboot of the system is always a good first step. :man_construction_worker:

To confirm, you aren’t experiencing any issues in playback or connectivity, you’re just seeing a consistent ‘waiting for Roon Server…’ when viewing the About page within Roon Settings?

Our development team will take a closer look and the above information will be helpful. Thanks!

Correct, no other noticeable side effect on this new PC setup with Roon.

There is this observation, i.e. without any change to my music sources (lives out in multiple NAS boxes), “sometimes” when i restart Roon server, i would get a message saying Roon needs to update the database.

What’s interesting about this is that NOTHING changed, no update, new change to music library. Only thing did is close Roon server. Start Roon server.

Reporting this as well, from this new PC setup.

Between the “Waiting for your Roon Server” and “Uh oh, something’s not right”, i did catch the Roon Server Status as showing “Error” of some sort. Unfortunately that quickly changed to “Running”, so couldn’t grab screenshot.

Note that this new PC is a “dedicated” Roon Server on Windows 10 Pro new PC. And the C: drive is SSD storage.

The backup do eventually complete.

It would have been “Roon Server Status: Not Responding” - that’s been reported elsewhere on the forum (on MacOS, I believe, but I suspect it is also happening on Windows installations).

Yes, it happens frequently on my setup Win11 server with iPhone 15 pro & iPad Pro clients. It’s a right PITA at times, especially when server & client reboots don’t immediately resolve it…

This topic was automatically closed after 9 days. New replies are no longer allowed.