Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
T-Mobile Cellspot Router
TL-SG2216 Switch
Ethernet and WiFi devices.
Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)
Ethernet Connected PC
Macbook
iOS Devices
Apple Homepods
DietPi Roon RP3 Endpoints
Description Of Issue
When attempting to identify an album I encounter a network error. Newly added music is recognized, and playable, but does not show Roon-applied album information (bio, etc.).
The WiFi Cellspot Router, a rebranded Asus RT-AC68U, shouldn’t be the culprit. I’ve used it since I purchased Roon a few years ago with no issue. I just noticed this Roon behavior in the last few weeks, and search/playback seems to be working as normal.
I’m currently getting DOWNLOAD Mbps 153.10 and UPLOAD Mbps 11.31 to my Ethernet-connected PC. My Synology Core is ethernet-connected, with link aggregation, to the same switch.
Regarding the DNS settings, is their a procedure I should be following? Happy to check detailed settings if you can provide me some direction.
As you say this used to work I’m assuming maybe there was some update to your core os perhaps?
Any update would have been to the Synology core OS. Perhaps @crieke is aware of a known issue or likely culprit?
What’s peculiar is if I de-authorize my Synology and switch to using my Windows 10 PC as the core, I don’t notice the same issue. That would suggest one of the following is causing the issue:
Can you confirm that you can access the internet from the Synology?
At least parts of the Synology are able to access the internet. The system can pull updates from the cloud.
Is there a particular setting to check?
Are you able to start Roon Radio or play Internet Radio stations?
I keep encountering a “Roon could not find a radio station at this URL” error. If I use the same URL on the Windows 10 core, I’m able to connect to the station and play it successfully.
Is there any change if you reboot the device?
Rebooting the Synology did not resolve the issue. Manually identifying an album isn’t working (timeout) and albums added in the last few days only show the basic tag metadata coded in the original files.
I have a four-cable aggregated link to my switch. The Windows 10 core is still playing the same files, stored on the NAS.
Based on that information, I don’t think the cables are causing the issue, because the LAN is working as intended. Sounds like connection to the web is a likely culprit.
Thanks for confirming. My guess is this is most likely limited to the Synology’s ability to connect to our servers, but I’d like to verify this by trying another Core. If you run the Core on Windows instead of the Synology, does this same behavior occur?
If you run the Core on Windows instead of the Synology, does this same behavior occur?
I just switched back to the Windows 10 core (connected to the same switch via Ethernet and reading the same files stored on the Synology) and am able to identify a newly added album. A few albums that are still unidentified on the Synology core are correctly identified on the Windows 10 core.
I updated the Synology to use Google DNS—that update resolved the issue.
I have my router configured to utilize 1.1.1.1 DNS at the network level. Is there any reason that setup would prevent Roon or Synology via Roon from working as intended?
