Post-update issues connecting to NAS folders (ref#UT1YUJ)

Support
1

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· Updated to latest software today and the following happened:

1 - update hung and crashed Roon Server on QNAP NAS
2 - I removed and reinstalled the app in a container
3 - I reinstalled Roon Remote on my iMac running Sequoia and was able to see the NAS
4 - I was not able to reconnect to the folder on the NAS with my music library
5 - I also tried to connect to another folder on the same NAS with backups, but no success

I am confident the login credentials for the NAS are correct. I am getting an 'Unexpected Error' message.

Tell us about your home network

· Cisco switches, Bitdefender VPN on iMac, Spectrum branded router. No connectivity issues with other devices or apps, now or in the past.

2

Presuming you read through this…

Note the last step, in which you have to restore from a backup. I can’t quite tell from your post if you performed that procedure as documented.

3

Thank you - I didn’t get a prompt that asked me to restore from a backup. I tried doing that afterwards, but was thwarted by the access issue. I can report that I have no problem connecting to Tidal and Qobuz.

4

The link for restoring is not obvious. You can see it in some of the screenshots here:

5

Hello @Nicholas_Gee

Thank you for the update. Since you are running Roon in a Docker container, it’s important to note that the container operates in an isolated environment and can only see the folders that were explicitly “mounted” during the setup.

Regarding the restore process and the “Unexpected Error” you’ve encountered, could you please clarify a few details:

  1. Access Issues: Could you describe the access problem in more detail? Are you seeing this error when trying to browse for the backup folder within the Roon interface, or is it a permissions error from the QNAP OS?
  2. Backup Location: Is the folder containing your backups already mapped in your Docker configuration? For the “Restore from backup” option to work, the backup files must be located within the directory you assigned to the /backups mount point during the container setup. Please share the backup folder location on your QNAP host system and .yaml file used during the container creation.
  3. Internal vs. Network Paths: Are you trying to add the backup folder using a network path (e.g., SMB/IP address)? Since the files are on the same NAS, you should use the local mapped path defined in your Docker settings instead.

Once the backup files are correctly placed in the mapped directory, the Settings → Backups should be able to see the backups folder and restore your system.

Please let us know more about the specific error you’re seeing, and if possible, share your Docker Compose configuration so we can verify the folder mappings.

Standing by for your reply!

6

Hello @vadim, many thanks for your reply. I suspect some of this is beyond my technical knowledge, so you may need to make things more basic for me please.

1 - I get this error only when trying to connect to the NAS from within Roon. I can connect to it fine from my Mac. I get the same error when trying to connect to my music files as when trying to connect to the backup folder.

2 - simple answer is no (and the same for the music files). Unless I didn’t understand something, the instructions on setting up Roon in a container didn’t talk about adjusting file paths. I understand the point about files needing to be in the same location as the container, but I’m not sure how to go about doing that. Do I simply drag them into that location (if it’s even possible) now that the container is set up, or am I supposed to do this ahead of time? and then what about adjusting the YAML code to point to those folders? I literally used the exact same YAML code as specified in the instructions (I think that’s what you mean by Docker Compose config), which works fine with the streaming services, but obviously doesn’t with locally stored music files and backup.

3 - yes to SMB/IP. I am fine to adjust, but what to?

It did occur to me that I’m just supposed to go back to running Roon as an app alongside all the other apps on the NAS, but I only ended up in this situation bc doing that meant that Roon didn’t work at all (it just showed a status of ‘stopped’ even though it said the app was running). I deleted and reinstalled it a couple of times (no other changes) and still had that problem.

I also looked at the log files and saw a bunch of 504 errors, which I assume all relate to the container point you made above.

I’m sure this is more basic than I realise and that the gap in my technical knowledge is why we’re here.

Many thanks for your help.

7

Hello @Nicholas_Gee,

Please don’t worry at all! Transitioning to Docker is a steep learning curve, and the exact issue you are running into—mapping the file paths—is the number one hurdle everyone faces. Let’s break it down into much simpler steps.

First, to answer your biggest question: No, you do not need to move or drag your files anywhere. Your music and backups can stay exactly where they are on the NAS.

Here is what is happening: Think of the Docker container as a locked, windowless room inside your NAS. Right now, Roon is sitting in that room, but it can’t see the rest of the house. To fix this, we need to use the yaml file to build a “window” that looks directly at your music folder and your backup folder.

Here are the answers to your points:

1 & 3: Stop using SMB/Network Paths Because Roon is now running directly on the NAS itself, you don’t need to use network addresses (like SMB or IP addresses) to connect to it. That would be like calling your own home phone from inside the house. Once we get the “windows” set up in the yaml file, you will simply select a local folder from inside Roon.

2: How to adjust the YAML file The instructions provide generic placeholder paths in the yaml file that look like this: - /share/Music:/Music - /share/Container/roon-backups:/RoonBackups

The left side of the colon is the path on your QNAP. The right side is the folder inside the Roon container. We need to change the left side to match the actual, physical location of your files on your NAS hard drives (this is called the “absolute path”).

The Next Step: To give you the exact yaml code you need, I just need to know where your folders are located on the QNAP. The easiest way to do this without getting into technical menus is to take a screenshot.

Could you please open the File Station app on your QNAP, navigate to the folder where your Music is stored, and take a full-screen screenshot? (And do the same for your Backup folder if it is in a different place).

Once you post those screenshots here, I can write out the exact yaml text you need to copy and paste. We will get this sorted out together!

8

Hello @vadim,

As I’ve been able to get things working, here are some comments that might help others:

  • This is way less complicated than I thought, but really simple and basic instructions woud help the uninitiated (more basic than on the primers folks pointed me to would be great).
  • Syntax is critical - Linux is case sensitive for file paths. This is for the boxes on the left hand side of the RoonServer Docker Config Generator.
  • Given that the container setup seems only to allow the folders specified in the YAML, perhaps Roon could automatically choose them? It does it for Music, not sure why it can’t be backups too.
  • When choosing a backup folder, you get presented with a long list of files and folders. If selecting the backup folder automatically isn’t possible, then at least limiting the choice to the one defined in the YAML and suppressing everything else could be helpful.
  • I had to run the backup procedure twice before it would go into the regular Roon screen. Not sure how common this is, but folks might like to know that doing it more than once could be necessary.

Again, many thanks for your help.

9

Hey, @Nicholas_Gee.

We’re glad you were able to get things working, and we’ll go ahead and mark this thread for closure. Enjoy your music!