When attempting to start roon on my core machine (windows 10 laptop), I'm prompted to "Choose your roon server". The option is "This PC-Windows 10/127.0.0.1 Version2.0 (Build 1442) production with a blue dot next to "Ready". I hit connect and get a white screen with pulsing roon logo, but it never connects. Prior to this, playback stopped mid-song and none of my roon-ready devices showed up on roon core machine or any of my remotes. I shut down roon on core machine, rebooted core machine, and now have problem described above. I have tried shutting down firewall on private network on core machine temporarily but same problem.
Describe your network setup
ASUS RT-AC86U router, Arris Surfboard SB8200 modem
To confirm, you are referring to your windows firewall specifically, correct? Do you have any additional third party antivirus software or VPNs active on the machine?
Do you have a recently saved backup available? If so, lets see if refreshing your Roon Server database may help. Steps to follow below:
I do not have any additional antivirus or vpns active. I followed your steps, then started roon on the core machine, entered my roon and qobuz credentials, it found my roon ready devices and was loading my music from my database but then went into screen saver mode which seemed to stop the database load after I activated the screen again. So I followed your steps again, and after this reinstall, when I run roon I get screen “Waiting for your Roon Server - Your device doesn’t seem to be running”. I’ve selected “Start Roon Server” multiple times and have also tried “Select a different Roon Server”, but it keeps coming back to this same screen. I have also tried starting the roon server using the RoonServer shortcut that was created.
This is expected behaviour - if you are running Roon Server on a windows or mac computer, letting the computer go to sleep will cut off connection to Roon Server.
Are you able to restore Roon from a saved backup and connect?
Can you confirm Roon Server is running via the taskbar on your windows machine? Share a screenshot if possible.
After several failed attempts, Roon finally loaded all of my music from the database and I could see all of my roon ready devices. However, when I attempted to play a song, the time elapsed bar for the song pulsed back and forth and I get an occasional pop-up that says Waiting on Roon Server and music does not play. Then, after a while, the roon interface no longer finds any of my roon ready devices. Attached is a screen capture showing that roonserver is running. Everything on the laptop is running very slow. This is an old laptop with less than the recommended specs for running roon. Is it possible that the latest updates to roon have exceeded the specs of this laptop? It just seems strange that it was working fine and then just stopped playback suddenly. Wasn’t sure if I should still try restoring roon from a backup? I have a screenshot confirming that roonserver is running but not sure how to upload/attach? Thanks.
Attached is screenshot of roonserver running. After leaving laptop alone for several hours, I received message that windows defender firewall was blocking RAATserver. I checked allow access on private network, but still the same problems
Update - I am able to play music for the first time since problem started. I simply started roon and after a couple of “waiting for roon server” messages, it worked. However, in the middle of every 2nd or 3rd song, playback stops and none of my roon ready devices are available except my AVR. I get message “You don’t have any zones, go to your interface to set up zones”. After about 30 seconds, all of my roon ready devices, including my DAC, show up as selectable again, and once I select my DAC, music plays.
Hi @Scott_Tweddale,
I think the next step here is to enable some diagnostics on your account so our technical staff can get some more insight into what’s going on here.
However, before I enable this feature, I’d like to ask for your help ensuring we gather the right information.
First, can you please reproduce the issue once more and note the time at which the error occurs. Then respond here with that time, and I’ll make sure we review the diagnostics related to that timestamp.
I encountered the error at 4:02pm central today (8/27). Listened to 2 songs and then playback stopped in middle of 3rd song. Saw several pop-ups of “Waiting for Roon Server” on the core/server machine over the next several minutes, followed by a message that no Audio Devices were set up. The roon endpoint that I was streaming music to was “basement: Mytek Manhattan II”. When I tried to re-select this endpoint, it did not show up initially, but then at 4:08 it showed up again and I was able to select it and resume playback to it. This pattern repeats itself. As I mentioned earlier, my core/server machine is an old laptop that is well below the minimum specs you recommend for running roon, so I may be up against hardware performance issues. Perhaps time for a new core/server. thanks
Thanks for the update and timestamp! We do see dropouts in relation to a lack of bandwidth around the time you shared.
I see you also have a Windows 11 machine, are you able to temporarily move your Roon Server over to this machine and test to see if the same issues occur? Let me know.
I attempted to migrate roon server to my windows 11 machine but it did not work. Followed instructions from here: https://help.roonlabs.com/portal/en/kb/articles/migration#Preparation. I was able to restore roon from a backup and then logged into roon when prompted and selected the new server. I get white screen with logo pulsing for about 30 minutes, then “Uh Oh, something’s not right. Make sure your roon server is turned on and that you’re connected to the same network”. Then pattern repeats.
On the windows 11, did you allow Roon as a proper exception in the windows firewall? Here’s more info:
Another easy way to test this is to temporarily disable the windows firewall and see if you’re able to connect properly. We’ll be on standby for the results.
No success. I tried turning off firewalls temporarily. I also tried adding all of the roon associated .exe’s as firewall exceptions. I did notice that our network was public by default, so I tried changing it to private with no success. The fact that it was public by default means that it was set to public when I did the restore from backup. Not sure if that’s relevant? Should I try to re-do the restore from backup with it set to private?
This shouldn’t matter, setting it to private now will do the trick!
I’d be curious to see if you run into the same issue when attempting to start Roon from a completely fresh install, not restoring from a backup. Let’s see if that makes a difference in connecting. I’ll list similar steps from above, but this time, don’t immediately restore a backup - see if you can connect and login and access a ‘Brand New’ Roon account from the windows 11:
If you’re able to access the Roon homepage, we may be looking at a database-related issue. Let us know the results!
Success! Roon is running and seems stable after a fresh install on windows11 machine. When I logged in, it told me I was already signed in and I had to disable the old server. Could this have been the problem all along, or is it a database issue? I ask because using the windows11 machine for roonserver is only temporary. I intend to move to a dedicated sonictransporter for roonserver. Also, I don’t have recent activity-added or roon playlists since I didn’t restore from backup, but all of my qobuz albums are restored in my library as well as qobuz playlists. Is it possible to try restoring from a different older backup? Do you suspect that the most recent backup that I used was corrupt due to problems on windows10 machine? thank you.
This is a normal result of the database refresh process you performed. Nothing out of the ordinary there!
You can certainly test out restoring from a backup - that will give you all the prior library settings and playlists. We didn’t see any diagnostic traces pointing at corruption, so I think you’re safe there. Worse comes to worse if you run into the issue again after restoring the backup, you can perform the same refresh steps again.
