· None of the above quite fits
· None of these quite match
· Artist overview and discography unavailable, artist search doesn't work
· Router: TP-link Archer AX6000, switch: Trendnet TRG-S50g, no VPN
Roon core/server is an M4 Mac mini with external SSD for locally stored music. Qobuz is used for streaming other music.
Hi @JeffS, welcome to the community.
Thanks for sending the screenshots and setup details. Since the artist overview, discography, and Roon search are all failing at once, this looks more like a connectivity or backend access problem than a local library issue.
Before we go further, a few things would help us narrow it down:
If possible, could you please attempt to update your Roon Server, and see if that helps?
Thank you! 
The images I sent were from the Roon remote, a MacBook, not the Mac mini. So the artist overview failure looks like it does in the image above with the Roon logo spinning. The discography failure looks like the image above with the message discography unavailable, and the search failure looks like the image above.
The M4 Mac mini is connected to network with Ethernet.
When I browse my local library in album view, the first few rows show the album cover while subsequent rows do not. Clicking on an album that shows the cover or one that does not takes me to that album and it plays.
I notice that my MacBook (Roon remote) has latest version, while Roon Server (Mac mini) does not as shown in first image below. Looking at a monitor attached to the Mac mini, that machine is not able to update to the latest version as shown in second image below. Web pages open instantly on the Mac mini except for Roon web pages. I was thinking of going to the Roon download page and re-installing Roon Sever on the Mac mini. Are there any precautions when doing that?
Hello @JeffS,
Thanks for the update and additional information.
From your account admin, it looks like your Roon Server instance hans’t reached out servers in about two weeks now.
With this, can you please use the directions found here and send over a set of Roon Server logs to our File Uploader? Once logs have been uploaded, please let us know so that we can check the server for your files, thanks!
Thank you benjamin. On my Roon Server Mac mini under Library there are Roon and a Roon Server folders and the log files in them have different dates. Should I send both folders?
Something really strange, on my Roon Server Mac mini, Roon web pages don’t work. On that machine all other sites I’ve tried open immediately and function as they should.
I sent over the logs. I sent the Logs folder from the Roon Server folder (instead of the Roon folder) because it had more recent RoonServer_log files including one from this morning.
I shut down my Roon server on the Mac mini before doing this. I don’t know how to re-start it can you please help with that. I see the Roon app in applications and opening that brings up the message “Waiting for Roon server.”
I was able to start Roon server by re-booting the Mac mini.
Hey @JeffS,
Thanks for getting the logs over, and for the extra detail on your setup.
Good news first: this isn’t a problem with your library or with Roon itself. Your Roon Server is starting up fine, your account is logged in and licensed, and your local music plays normally. The logs point to a network issue on the Mac mini, specifically, it can’t reliably reach the Roon cloud servers that power artist overviews, discography, search, artwork, and updates.
Here’s what we’re seeing. When Roon Server tries to connect to our backend, the connections repeatedly time out before they can even complete, thousands of these over the past two weeks, all to the same couple of destination addresses. Your metadata last updated successfully on July 6th, which lines up with when things started going sideways. Because those same servers also host our web pages and the software updater, this explains everything you’ve reported: the spinning artist overview, “discography unavailable,” search not connecting, artwork that loads for some albums but not others, Roon web pages not opening on the mini, and the failed update.
Importantly, other traffic (like Qobuz and general websites) gets through fine, it’s specifically the path to our servers that’s being blocked or dropped, and only from the Mac mini. That pattern usually points to something on the network filtering or interfering with those connections.
A few things to try, roughly in order:
1.1.1.1 and 8.8.8.8, then reboot the mini. This can route Roon to a healthier set of servers.
roonlabs.com / roonlabs.net.
Give these a try and let us know how it goes. Thank you! 
Thanks for your help! So far I did the following in the order listed.
On the TP-Link app I didn’t see HomeShield so I moved on.
Changed the DNS on Mac mini, added 1.1.1.1 and 8.8.8.8, when done those were the only ones listed, I thought they would be added to the original list of one to make a list of three.
Rebooted the mini and problems not solved.
Went back to the TP-link app and under security found found three features turned on: malicious content filter, intrusion prevention, infected devices quarantine. Are these what you want me to turn off? Is that safe? The TP-link app shows multiple instances of “blocked access to a malicious content website” for our phones, MacBook and iMac but none for the Mac mini. I only use the mini for Roon server and HQPlayer. The TP-link app also shows two instances of "defended against an attack from 192.168.0.211 and .210 classification DDOS. These were today and yesterday.
Leaving for a short vacation this morning and would like to put this on hold until after 7/28
Hey @JeffS,
Enjoy your vacation, no rush here at all. We’ll pick this right back up when you’re back after the 28th, and everything below will be waiting for you.
You actually found the culprit in step 4. Those three TP-Link security features, malicious content filter, intrusion prevention, and infected devices quarantine, are exactly what I’d want to test against, and the “defended against an attack from 192.168.0.211 and .210, classification DDoS” entries are the key clue. Those are internal (LAN) addresses, so they’re your own devices, and one of them is very likely the Mac mini. Roon Server holds many persistent, chatty connections open to our cloud, which is exactly the kind of traffic pattern these intrusion/DDoS systems tend to misread as an attack and start dropping. That lines up perfectly with what your logs showed: repeated timeouts to our servers from the mini specifically, while everything else on your network works fine.
So yes, when you’re back, those are the features to try turning off, and doing so is safe as a temporary diagnostic. A couple of notes so you’re comfortable:
First, before changing anything, jot down which IP the mini is using (System Settings → Network → Ethernet → Details will show it) so we can confirm whether .210 or .211 is in fact the mini. If it is, that essentially confirms the router is blocking Roon.
Second, the plan when you’re back would be, roughly in order: temporarily disable intrusion prevention first and restart Roon Server, then test artist overview and search. If that alone fixes it, we’ve found it and you can leave the other filters on. If not, also switch off the malicious content filter and the infected-devices quarantine, then test again. These are all reversible from the same TP-Link app screen, and turning them off briefly for a test doesn’t leave you exposed, your Macs each still have their own protections, and you can flip them back on the moment we confirm the cause.
If disabling all three restores things, the long-term fix is usually to add the Mac mini (or the Roon Server ports) to an allow-list / trusted-device exception in the TP-Link app so you can keep the security features enabled everywhere else.
One more reassurance: your DNS change looked correct. TP-Link/macOS replaced the single entry rather than appending to it, which is normal, 1.1.1.1 and 8.8.8.8 are both fine on their own.
Safe travels, and just reply here whenever you’re ready to continue.
Thank you Benjamin for the well written and clear instructions. The IP address the mini is using is one of the two in question which is 192.168.0.211
In the router I disabled intrusion prevention and restarted Roon server. When I started Roon on my Roon remote the update available window opened so I suspected problem solved. The mini now has version 2.70 and I tested artist overview, search etc. and they work.
Is there a long term fix you can walk me through where only the mini has intrusion prevention disabled?
Hey @JeffS,
That’s exactly the result we were hoping for, nice work confirming .211 is the mini, and glad to see it jump to 2.70 with artist overview and search all working again. That pins the cause squarely on the router’s intrusion prevention misreading Roon Server’s normal cloud traffic.
For the long-term fix, you don’t have to leave intrusion prevention off for the whole network. The TP-Link app lets you exempt a single device while keeping the protection on for everything else. Here’s the plan:
1. Give the mini a fixed IP first (so the exception never drifts).
In the Tether app: tap the mini in your device list → look for IP settings / Address Reservation and reserve its current address (192.168.0.211). This keeps it from changing later and breaking the exception. (You can also do this from the router web page under Advanced → Network → DHCP Server → Address Reservation.)
2. Add the mini to the Intrusion Prevention exceptions list.
In the Tether app: HomeShield → Security / Network Protection → Intrusion Prevention. Turn the feature back on, then open its Exceptions (sometimes shown as “opt out” or an allow-list), and add the Mac mini. That excludes only the mini from intrusion prevention while every other device stays protected.
3. Re-enable the other two, then restart and test.
Since disabling intrusion prevention alone fixed it, you can turn the malicious content filter and infected-devices quarantine back on. Restart Roon Server, then check artist overview and search once more to confirm everything still works with the mini excepted.
A couple of notes: the Exceptions option lives inside each protection feature separately, so adding the mini under Intrusion Prevention won’t affect the other two. If your firmware doesn’t show an Exceptions/allow-list under Intrusion Prevention, let me know your app and firmware version and we’ll find the equivalent, worst case you can leave just intrusion prevention off, which is a safe trade-off since each of your Macs still has its own protection.
I was able to complete step 1 but not step 2. Could not find Exceptions or opt out or allow list in the Tether app. An internet search brought up this AI summary:
The TP-Link Archer AX6000’s built-in HomeCare Intrusion Prevention System (IPS) does not feature a granular per-device exception or whitelist menu to bypass scanning for a single local device. The security engine operates globally across the entire network, meaning you can only toggle the entire Intrusion Prevention feature on or off rather than creating individual device exemptions.
My Tether app version is 4.15.19 (build 1859)
Hey @JeffS,
Great work finding the fixed-IP reservation, and thanks for the version details, you’re absolutely right, and it saves us chasing a menu that doesn’t exist on your router.
Here’s the situation: your Archer AX6000 runs TP-Link’s older HomeCare security engine (Trend Micro), not the newer HomeShield. On HomeCare, the three antivirus features, Malicious Content Filter, Intrusion Prevention, and Infected Device Quarantine, are network-wide on/off switches only. There’s genuinely no per-device Exceptions or allow-list for them, so my earlier “add the mini to an exception” step doesn’t apply to your hardware. My mistake there, the exception list is a HomeShield feature on newer models.
The reassuring part: your mini isn’t infected. Those “attack from 192.168.0.211 … DDoS” entries are Intrusion Prevention misreading Roon Server’s normal, persistent connections to our cloud (metadata, search, artwork) as an attack. That one feature is the whole problem, the Malicious Content Filter blocks in your logs were all against your other devices, never the mini.
Since there’s no way to exempt just the mini, here’s what I’d recommend:
Keep the address reservation you set up (192.168.0.211) that’s good hygiene and costs nothing.
If you’d rather not give up Intrusion Prevention long-term, one thing worth trying: check Tether (or
) for an AX6000 firmware update. Some models have been migrated to the newer HomeShield engine, which does offer a per-device opt-out, and with your reserved IP, exempting the mini would then be trivial. If no update is available, you can also report the false positive to TP-Link support so they’re aware Roon Server is being flagged.
Once you’ve settled on a configuration, let me know and I can confirm on our end that your server is checking in cleanly again.
Thanks benjamin that all sounds fine. I’ll let you know. Right now I have intrusion prevention on, malicious content filter on, and infected device quarantine on. Roon search etc. works fine. It may stop working again and that case I will turn intrusion prevention back to off.