What is the operating system of your Roon Server host machine?
· Roon Optimized Core Kit (ROCK)
What kind of device are you using to perform the login?
· Windows
Where are you trying to login?
· I can't log into Roon
Have you been redirected to [https://account.roon.app](https://account.roon.app) (the Roon login page) in your browser?
· Yes
Please try clearing the browser cache and cookies for the [l](https://account.roon.app/)ogin page where you have been redirected
· No, the issue remains the same
Content / Popup Blockers
· No, the issue remains the same
Temporarily try to use a different browser
· No, the issue remains the same
Please try to restart your Roon Server by closing the Roon Server app in the taskbar (MacOS), task manager (Windows) or rebooting your Roon Server machine.
· No, the issue remains the same
Different device
· I am able to switch to the diffrent device
Are you still facing the issue on the different device
· No, the issue remains the same
Record the timestamp
· I attempted to log in on June 2, 2026, at approximately 10:34 JST (UTC+9).
Describe the issue
I am currently trying to log in to my Roon ROCK system.
I have two ROCK servers and switch between them depending on my needs.
Two days ago, I powered up the other ROCK server, but I encountered some issues and shut it down before completing the login process.
Since the following day, I have been unable to log in to the Roon server from the other ROCK system, and I am having trouble figuring out what is wrong.
Could you please help me determine whether the failed login attempt or the abrupt shutdown of the other ROCK server might have caused this issue?
The system was working normally before I powered up the second ROCK server, so I suspect the issue may be related to that event.
Welcome to the forum! Could you please clarify the motherboard and RAM amount on the affected ROCK that is having the login issue? Are you still able to access that ROCK’s Web UI?
The affected ROCK is running on an ASUS TUF GAMING Z790-PLUS WIFI motherboard with 32GB of RAM.
I can access the ROCK Web UI without any issues.
I have successfully collected the logs and uploaded the ZIP file to the provided upload location.
As additional context, I operate two ROCK servers and switch between them. The issue started after I powered on the second ROCK server, encountered a problem, and shut it down before completing the login process. Since then, I have been unable to log in and use Roon on my primary ROCK server.
I also received an email notification from Roon indicating that a device from Osaka, Japan successfully signed in to my Roon account, suggesting that account authentication may be working correctly.
Please let me know if any additional information is needed.
I understand the reasoning behind resetting the Windows Roon folder, but I would like to point out that the same login issue occurs on both my Windows PC and my iPAD.
I can also log in to my Roon account successfully through a web browser, and I receive a “New sign in detected” email when attempting to log in through the Roon app.
Because the issue affects multiple Remote devices, I am wondering whether there could be an account, cloud, or server-side issue involved.
Could you please review the uploaded logs and check if there is anything unusual on the cloud/account side?
Yes, the logs you’ve sent over have already been reviewed. Your ROCK cannot reach the internet at all. Every single outbound HTTPS connection fails with:
socketerr (NetworkUnreachable): Network is unreachable
This is hitting both api.roonlabs.net and go.roonlabs.com. Without being able to reach Roon’s servers, the SSO login token exchange simply cannot complete, the login page works in your browser (which uses your PC’s network stack), but when Roon tries to retrieve the auth token on the ROCK side, it fails every time.
The evidence:
Your second ROCK successfully logged in on May 29 and ran fine.
Your primary ROCK then shows the same network-unreachable failure pattern starting from the very first log captured (June 1).
Crucially, both ROCKs report the same IP address: 192.168.88.200. If they were ever powered on simultaneously, even briefly, this would cause an ARP/IP conflict on your network. Your router or switch may have become confused about which MAC address owns .200, causing routing for that IP to break until it naturally resolves (or doesn't).
Some next troubleshooting steps for you to try:
From your router’s admin interface or another device on the network, check whether 192.168.88.200 is resolving to the correct MAC address (the ASUS TUF board’s NIC). If your router shows a stale MAC from the second ROCK, flush/clear the ARP entry or restart the router.
Confirm only one ROCK is running at a time. Make absolutely sure the second ROCK is fully powered off before booting the primary. Even if they’re on different networks, having both on .200 simultaneously will cause conflict.
Check the default gateway from the ROCK Web UI. From the ROCK Web UI, navigate to the network settings and confirm:
IP address: 192.168.88.200
Default gateway is set (e.g., 192.168.88.1 or similar)
DNS servers are populated
The NetworkUnreachable error (as opposed to Connection Refused or a timeout) specifically means no route exists; the ROCK doesn't even know how to reach the internet. A missing or wrong default gateway is the most likely cause.
Restart the router/switch, then reboot the ROCK. Power-cycle your router and/or managed switch to flush all ARP tables, then reboot the ROCK fresh. This alone often resolves IP conflict aftermath.
The latest Windows Roon log does not appear to show any NetworkUnreachable errors. The Remote can connect to the ROCK at 192.168.88.200, and communication with api.roonlabs.net appears successful (HTTP status 200).
However, I am still unable to complete the login process.
I also noticed the following error in the log:
“error processing internet discovery device: Sequence contains no elements”
Could you please review the newly uploaded logs and let me know if you see anything that might explain why the login process is still failing?