Hi - Just a quick update - I’m now running MacOS 15.7.4 (24G517) and I’m still seeing RoonAppliance MacOS error: -25294 . I haven’t had the problem with files not playing in a while, but I thought you should know. Perhaps you would have another suggestion for me to look into to resolve the errors. Thanks!
Hey @James_Moore,
Thanks for the update, I’m happy to hear playback has been stable! Since -25294 specifically points to a “missing” keychain, the system might be defaulting to the iCloud/Local Items sync scope when Roon expects the local login keychain (or vice versa).
- Check for Orphans: Open
Keychain Accessand look for any non-standard keychains listed in the sidebar. If there are any "ghost" entries from a previous migration or a corrupted volume, RoonAppliance might be trying to reach into one of those. - Reset Default: Right-click the login keychain and ensure it is set as the "Default Keychain." If it already is, sometimes toggling the lock (Lock then Unlock) can force the Security framework to re-register its availability to background processes like RoonAppliance.
- Go to System Settings > Privacy & Security > Local Network.
- Toggle the switch for Roon (and RoonServer/RoonAppliance if listed) to OFF, wait 10 seconds, and toggle it back ON.
- Do the same for Full Disk Access. This often clears the "Could not create required lock file" errors that often accompany keychain issues.
- Exit out of Roon/RoonServer (from the taskbar)
- Find and open your Roon database
- Navigate to
/Library/RoonServer/Cache - Move the contents of the
/Cachefolder elsewhere, like your desktop - Try restarting Roon and verify if the issue still occurs
Thank you!
Hi Benjamin - Thanks as always for the suggestions - I will take these in order they were suggested.
No Keychain orphans exist
When I right click on the Login Keychain , there is no option toggle to select or unselect the keychain to be default as you mention.
I toggled off an on the Local Network and Full Disk Access settings
I dragged out the Cache folder from my user/Library folder and restarted the server.
None of the above helped end the error messages.
At the same time, I’ve not had any failures to play since 2.61/2.62 updates. I assume these errors should not be occurring, but at the same time, how big a deal is it given it did not seem to be the cause of the failed playing? That said, I’d still love to resolve this if you have other ideas given I assume this should not be happening.
Hi, still seeing thousands of these errors. Hopping you have further advice to resolve. Nothing so far has influenced this issue. Thanks.
I have an update for you. I went out today and bought a brand new Mac mini with MacOS 26 on it. I set it up as a new Mac so as to not migrate over any issues, and then I installed a fresh copy of Roon, and then restored Roon from backup. I still see the same error - I’m not sure what to do at this point. Please advise. Thanks !
Hello @James_Moore
Thank you for that update. It is indeed very interesting (and a bit unexpected) that the -25294 error persists even on a brand-new machine with a clean OS install.
I want to be completely candid with you: earlier in our conversation, we pointed to these errors as the “smoking gun” because, on your 2012 Mac Mini (Catalina), they were directly tied to playback failures. Now that you are on a modern M4 Mac with the latest OS, the fact that the error remains while playback (presumably) works suggests that the impact of this error has changed, even if the code remains the same.
To help us pin this down, could you clarify a few things for our team:
- Playback Status: How is the actual playback performing now? Are you still experiencing any skips or hangs since moving to the new Mac mini?
- Clean Database Test: Did you happen to notice if these errors were appearing before you restored your Roon backup (i.e., when you had a completely fresh, empty Roon database)?
- Current Experience: Aside from seeing the messages in the Console, have you noticed any functional issues today?
Internal Update: I have officially opened a task with our R&D team to investigate why RoonAppliance continues to trigger this specific security framework error on Apple Silicon and macOS 15/26. We want to clean up these logs and ensure that Roon is communicating with the macOS Keychain as efficiently as possible, even if it isn’t currently breaking your music.
1 Like
Hello Vadim. Thank you for the reply.
To answer your questions:
- I have not experienced any playback issues since setting up the new Mac, however, to be fair, it’s only been a couple days, and that falls into the normal window of when things worked. At times it would take several days for any issues to occur.
- I’m sorry to say I failed to do any testing & looking at the console logs before performing the backup. That would totally make sense as a rational troubleshooting step, but at the time I didn’t think to do it.
- No functional issues. The new Mac does greatly improve the perceived performance of Roon, responsiveness wise, anyway.
Thank you for opening the R&D team case. I agree with you. Please let me know if I can assist further. Do you have a sense on how long it normally takes for someone on that team to provide you feedback?
Thanks!
So thinking through your comment about a “clean database test” I decided to give that a try, so I deleted Roon app and Roon files everywhere I could find them by searching and my general Mac knowledge, and then reinstalled the software fresh. I logged in but didn’t add any files or log into Qobuz. I was watching the logs and I got the error only about 15 times . Then it stopped and did not start again. After waiting for a while and not seeing the error I moved on with my testing.
So then I pointed Roon to my my external SSD that contains all my music and boom . After like 10 mins or so I have over qty 30,000 MacOS error - 25294 messages. And counting up fast. I haven’t even played a song - but roon is in the process of “Adding music to the library”
Next I disabled my local storage and the messages stopped and stayed stopped.
Then I Logged in to Qobuz and in like 2 mins in had over 50,000 -25294 messages, and the number of errors was climbing fast while it syncs.
So it’s clearly about general network access, both syncing a library from a streaming platform or IDing local files- I just can’t figure out what is going on. I hope your developers help us determine what’s happening. In the meantime I guess I restore from my backup and wait for your reply.
Hi @James_Moore,
Apologies if this has already been glazed over, but are you using any active VPNs within your local network setup?
The reason we ask is that based on the full Roon Server log, -25294 errors fire in bursts immediately after TCP connections to port 443 (HTTPS) are established via utun4, and utun4 is a VPN tunnel interface.
If you disable any VPNs, do you still run into the same issue?
No VPN’s in use. Roon is on this brand new Mac mini, and is the only app I’ve ever installed on this new Mac other than a hard drive search tool called EasyFind By Devon Tech ( DEVONtechnologies | Needful Things ) and Roon, of course.
The Mini is hardwired to my network and was assigned an IP by my router, which I just made a DHCP reservation for it in the router. There are no active VPN’s enabled anyplace on the network.
I did a netstat -rn in terminal and the routing table I think looks clean. Everything goes through en0 (the physical ethernet/wifi interface) with a normal gateway of 192.168.1.1 of my router. There is no utun4 interface anywhere in the routing table, so I’m thinking no VPN smoking gun there, so no vpn tunnel that I can tell with what I know. Maybe I’m misunderstanding that you are thinking or not looking at the correct relevant data. Thanks. I look forward to more follow up or any report from your R&D team that was mentioned earlier by Vadim.
Hello Vadim. Any updates from your R&D people regarding the case you opened with them regarding my issue? Thanks!
Hello. Just checking in. Been a bit since I’ve had an update. Thank you!
Hi @James_Moore,
Thank you for your gracious demonstration of patience and we’re sorry this has taken so long.
You mentioned that the errors accumulated during import. As a test, please try copying a few of these local files to a completely new folder stored directly on the Mac (like the desktop). Create a Watched Folder in Roon pointing to that location instead. Do you see the -25294 accumulate for each track import? We can scan the logs for you, we’ve requested diagnostics from the account automatically.
Did you use Time Machine to migrate from your old to your new Mac by chance? Or was this a completely fresh user setup on the new Mac?
Just so we understand correctly: you’re not currently experiencing dropouts or playback issues with this new RoonServer instance?
Hello Connor.
I did NOT migrate via Time Machine. I simply set up the new Mac, loaded Roon, and let it roll. Since then, I have also installed EasyFind and Carbon Copy Cloner, that those are the only apps besides the Apple ones..
I am NOT generally experiencing dropouts or failed plays this week since Qobuz got their CDN issues cleaned up and you guys released 2.62 and beyond.
IMO, my noticing the -25294 errors came at the same time as the Qobuz drama and the Lumin issues (I use a Lumin U2 Mini). I mistakenly assumed causation when it probably was just correlation. Once I spent time in the forums, I figured that out.
The -25294 errors came like crazy when I first connected the new/clean Roon to Qobuz AND also when I then next added my local files. I mean by the 10’s of thousands. Once those files (streaming and local) all got scanned by Roon, the errors died down - BUT, it still happens. They come like 14 at a time, or sometimes just one. I just checked and I see that happening right now.
So I did what you asked. I added a folder to my desktop that had about 10 albums worth of files in it and added it as you requested, and there was a small flurry of activity - but not sure how significant of what this shows. I took a screenshot movie of the process, but it looks like your system won’t allow the upload. Thanks -
Hey, @James_Moore.
Thanks for performing that test.
We were able to reproduce the same problem on our side, and it has already been passed to our developers since it is easily reproducible.
Could you please clarify whether you are still seeing any issues other than the -25294 error spamming in console ?
Thanks.
Hello @alex_h That’s a relief. Been working on this for a while 
Regarding your question about other issues. No. The other chatter in the console seems like normal log noise, from what little I know and can tell.
In terms of as a listener & user, Roon performance itself, since moving to the new M4 Mini (with MacOS 26), and you guys pushing our 2.62 and newer, AND, Qobuz fixing their CDN issues, it’s been good. Thanks for pushing this to the developers, Hopefully they can clean that up in their new builds. Cheers!