Clean uninstall of Roon, RoonServer, and RAATServer Reinstalled from scratch (latest version) Chose “Use this PC” as Core Opened firewall ports manually Tested on a clean Windows install Verified DNS, time sync, IP binding Problem: After successful authentication, Roon returns to the “Connect to Core” screen and repeats the loop.
Reference Thread:
I’ve also attached the latest Roon_log.txt file for your analysis.
https://gofile.io/d/hfumcn
UPDATE #2:
In addition to the login loop issue, I’ve noticed that in the few rare cases when I do successfully log in, the Roon Core appears to launch but:
No Audio devices are detected (RAATServer doesn’t seem to start) The music library doesn’t scan — no albums or folders appear The Core seems unresponsive to remote connections Interestingly, in a few of those rare cases, I was able to connect to the Core using Roon Remote on my iPhone — but only briefly. Even then, the Core still showed no audio devices or library content.
These symptoms strongly suggest that the Core is not starting fully. I reviewed the logs and found there is no indication of RAATServer initialization or Watcher events for library scanning.
This aligns with previous log entries like:
ServerRestartNeeded, could not get RoonServer app lock connected to local broker? False
So the issue isn’t just login — it’s that Roon Core fails to start up completely, even after successful authentication.
All signs continue to point to an internal issue with session locking or background services not initializing, possibly due to a compatibility issue with Roon 2.50 build 1528 and Windows 11 24H2.
Kindly assist further — thank you so much!
Describe your network setup
Opened firewall ports manually Tested on a clean Windows install Verified DNS, time sync, IP binding
Thank you for reaching out to Roon Support and for providing the detailed report along with the uploaded logs.
Unfortunately, the logs you attached are from a remote Roon instance, which aren’t helpful for this specific case. I’ve enabled diagnostics on your account, but for some reason, your device is not successfully communicating with our servers—even after I re-enabled diagnostics on my end. I also ran a test from my own setup and was able to submit a similar report successfully, which suggests there may be another issue at play.
To help us move forward, please follow the instructions here to manually collect logs and upload them via our Logs Uploader Service. Once uploaded, let us know so we can take a look—thank you!
Additionally, could you please try copying the login link that opens in your browser (after being redirected from the Roon app) and paste it into a different browser, then manually enter your credentials there to see if you are able to log in?
I’ve just uploaded the latest Roon Core log (Roon_log.txt) via the uploader service as requested.
This log was taken after a clean reinstall and running the lock reset script. Login was successful, but Roon failed to stay connected to the Core (PONY-ROON-CORE), and it loops back to the “Connect to Core” screen.
Relevant log entries:
Connection dropped after login
connected to local broker? False
could not get RoonServer app lock
Please let me know if you need anything else.
Also, if there’s anything I should check or test further on my side, I’d be happy to help move this forward.
As per your official log submission guidelines, I’ve zipped and uploaded the full RoonServer/Logs folder, ensuring that Roon was fully closed before collecting the data.
The zip file is named after my email and has been uploaded via your Logs Uploader Service.
Please let me know if you need RAATServer logs or anything else.
Hi @SPATIPON,
Thanks for uploading those logs for us. I found a trace indicating that your Roon server wasn’t able to retrieve an account from our servers. Additionally, our diagnostics request is unable to reach your server, which suggests something on your network is interfering with Roon’s ability to connect externally.
Here are a couple of things you can try:
Try a different DNS provider. We’ve seen improved results using:
I’ve followed your suggestions regarding DNS and firewall:
DNS: I’ve tested multiple providers including Cloudflare (1.1.1.1), Google DNS (8.8.8.8), and Quad9, by setting them manually in Windows network settings.
Firewall: I’ve created both inbound and outbound rules to explicitly allow I’ve also double-checked Windows Defender settings to make sure no interference.
Despite these steps, the issue persists. Roon still fails to connect to the Core after login, resulting in a loop back to the “Connect to Core” screen.
To assist further, I’ve uploaded two log archives via your Logs Uploader:
Spation RoonServer_log.zip – contains full RoonServer logs
Spation Roon_log.zip – contains the Roon logs
Please let me know if these provide any clearer insight, or if there’s anything else I should test or adjust on my side.
Based on the traces, your Roon server appears to be restarting approximately every minute, and we’re not seeing any login attempts at all — this behavior is not expected.
Could you kindly confirm whether you’re using an existing database or if you’ve performed a restore recently?
Also, could you please let us know what regional settings are currently configured on your laptop? In some cases, switching to English (United States) may help with the stability of the application.
How to change regional settings to English in Windows:
Open Settings
Navigate to Time & Language > Language & Region
Under Windows display language, choose English (United States)
If it’s not listed, click Add a language, search for English (United States), and install it
Restart your system for the changes to take effect
Please let us know once you’ve made this change, and we can continue investigating from there.
I’ve followed your instructions and switched the system’s Regional Format to English (United States) while keeping the Windows Display Language in Thai. After restarting the system, Roon Core was able to launch and function properly.
I’ve confirmed the following:
Core now boots without looping or crashing.
I can see and enable my audio devices, including my Roon Ready device
It’s worth noting that:
Windows Display Language can remain Thai without issue, but Regional Format set to Thai causes silent failures