· The Nucleus boots up and I can connect to it in the Roon app without issue, but I have a question about configuration/storage/attached devices
Describe the issue
Roon won't mount network attached drive for backups. It connects to one of my network servers but not the other which it was connected and doing backups until today. When I tried to add again thenetwork share I got the message "unexpected error". Nothing was changed in the original network configuration. The share can be accessed from my Mac from menu Go to server...
Hi @Alberto_Arebalos,
Thanks for writing in to ask us about this issue. I activated diagnostics on your account and found traces of network issues. Additionally when you tried to add the drive we saw a trace saying invalid operation. Are you able to mount the drive outside of Roon? If you can please copy that network path and try adding it that way.
I reinstalled Roon server, moved the Nucleus One to my main switch and was able to add the shared folder. Although from time to time it shows problems reaching metadata servers and now can’t access it from ARC. I am using Tailscale. ARC sees the server, then ask who is listening today? I choose my profile and the it says “There is an issue with your roon server.”
Based on the information you’ve shared so far, it sounds like there could be some network blockages at play, we can’t yet fully point at your Nucleus as the point of error quite yet.
If you could, please move your server back to your Nucleus, and attempt to access Arc again. You mention using Tailscale - could you please share a screenshot of the webUI of your Nucleus? Here’s more info:
Did you follow the directions on installing Tailscale on your Nucleus? Here’s a step by step on this as well:
Well, looking my Nucleueone page I saw that DNS was 0.0.0.0 which is weird. I went to my Tailscale page and discvered that “Magic DNS” was allowed. I unchecked Magic DNS, and now DNS at NucleusOne is back at 192.168.1.1 and seems working.
Glad to hear that toggling Magic DNS off helped! I haven’t heard of this setting to cause such behavior in the past, but we’ll definitely keep an eye out for similar reports!
