Roon ROCK NUC
Intel BXNUC10i7FNH Core i7-10710U 6-Core NUC Mini PC, 2.5" Drive Bay
Storage Drive: Crucial BX500 2TB 3D NAND SATA 2.5-Inch Internal SSD, up to 540MB/s - CT2000BX500SSD1
SSD OS Drive: Transcend 128GB Nvme PCIe Gen3 X4 MTE110S M.2 SSD Solid State Drive TS128GMTE110S
Version 1.0 (build 227) stable
Running 1 minute, 50 seconds.
Roon Server Software
Version 1.7 (build 667) stable
Running 0 minutes, 13 seconds.
Roon Database & Settings
94% of 114 GB available.
Internal Music Storage
2000GB, CT2000BX500SSD1 39% of 1848 GB available
Core Machine (Operating system/System info/Roon build number)
**Network Details Synology RT2600ac connected via ethernet
Macbook Pro 2012ish remote
Iphone 6s Plus
Allo DigiOne Signature connecting to Airport Express via ethernet (but the Airport Express is wirelessly connected to Synology router - extending network and airplay source).
The Allo DigiOne is running Ropieee XL and I have no problem connecting to it via the IP address listed in my router…
Schiit Modi 3 DAC takes optical output from DigiOne and outputs to vintage Yamaha receiver via RCA cables.
connection is flaky, doesn’t show on Roon software on MacBook - flips in and out of connection - eventually has fatal problem “There was an issue loading your database”
I can reboot/reset/restart the NUC/ROCK via http://192.168.1.20/, but the problem remains. I do not have any issues with accessing the ROCK/NUC’s files through Finder on the MacBook.
Synology Firewall is turned off (I think - I don’t have anything checked/enabled to run in the Security/Firewall gui.
I have reinstalled the OS a couple of times, and I can control the NUC for a little while via the MacBook but it eventually fails and I get the loading screen/lost connection and ultimately the “there was an issue loading your database”
I’m not super savvy with the Synology/networking settings and I am hoping someone can point me to some newbie setting I have which is causing the flaky behavior.
Previously this system was running fine on an Airport Time Capsule Router. I’m pretty confident it is something I have put in the Synology settings which is screwed up.