Feature Request
When the Roon server receives an unauthorized response from roonlab’s account service API, display the login screen to the user so they can reauthorize their account and service.
Current System Behavior
Roon stops playing music and the Roon remote doesn’t show why things are not working. Restarting just the remote won’t re-connect it to the Roon server. It takes restarting the Roon Appliance for the remote to display a login screen. Once logged in, everything functions as expected.
Cause of Behavior
I was reviewing my upcoming Roon subscription renewal and noticed old login sessions.
I removed weeks and months old sessions and carried on. Some time later, Roon stopped playing music. Had to look in the logs to see what might have gone wrong and saw this in the Roon server log (unrelated log lines removed):
Debug: [easyhttp] [10577] POST to https://api.roonlabs.net/accounts5/accounts/3/login returned after 217 ms, status code: 200, request body size: 42 B
Trace: [fiveaccountserver] GOT {“status”:“Unauthorized”}
Trace: [fiveaccountserver] logging out due to Unauthorized response
Info: [broker] is not licensed
Trace: [broker/accounts] Data updated. AccountStatus=Unauthorized MachineStatus=Unauthorized UserId=
Trace: [transport] disabling transport
Warn: [auth] EnsureAuthReady failed: Result[Status=Unauthorized]
Warn: [broker/accounts] failed to refresh account info: Result[Status=Unauthorized]
Info: [music/storage] disabling library
Debug: [UpdateRemoteLocalTime] iso = 2026-04-16T15:58:19.0770300-05:00
Error: Atomic File Move: /Users/me/Library/RoonServer/Database/Registry/Core/local_time_offset_from_utc.tmp → /Users/me/Library/RoonServer/Database/Registry/Core/local_time_offset_from_utc failed on linux: -1 errno=2
Error: could not write key: local_time_offset_from_utc = -1.6666666666666668E-07 – System.Exception: atomic file move failed: -1 errno=2
The Error level message,System.Exception: atomic file move failed caught my eye. Took me a minute to put one and one together why Roon was unauthorized and disabled several important functions.
A graceful recovery with the Roon remote would make it clear what the next step is after an event like this.