Cannot connect to QNAP TS464 for adding music folder (ref#YHMXIH)

Support
1

Hi! What’s not quite right with Roon?

· Music won’t play or issues with my library

Music won’t play or issues with my library

· Local files won't import or appear

Tell us what's going on

· I cant connect to my local Network ie add a folder.
I have a QNAP TS464 which has the pathway smb://192.168.1.50/Public/Music. No matter what i do i keep getting the same error message "there was an unexpected error. Unexpected error".

Tell us about your home network

· I use Deco Mesh (Be65Pro) and it is connected to my NAS via Ethernet

2

And where is your Roon Server running? What OS? How installed?
Some more details might greatly help helpers to help you.

3

Hello @edward_thompson

Thanks for the screenshot. There is no need to go over the network here at all.

Your Roon Server is running on the QNAP at 192.168.68.52, and your music is on that same QNAP. You are asking the NAS to connect to itself over the network to reach folders it already has locally.

One question decides how you add the folder, and it is the only thing we need right now. How is Roon installed on the QNAP: through Container Station, or as an app from the App Center? Please open Container Station and tell us whether a Roon container is listed there.

If Roon runs in a container, it can only see folders that were mapped into it when it was created, so the music folder has to be mapped there first and then added in Roon by the name it has inside the container. If it is the App Center version, you browse to the folder directly. The two routes are different enough that we do not want to send you down the wrong one.

Two other things worth knowing. Your Roon Server currently has no music folder configured and one album in its library. An earlier record of the same server shows /Public/Music added with around 9,500 albums, so the settings have been lost rather than never set. Do you have a Roon backup, and if so where is it? Restoring it would save you re-importing everything.

5

Great. Thanks so much for the response. I reinstalled Roon via Container Station and added the folders as per below but still no luck with Roon reading those folders?

Docker path
Docker path1276×992 67.1 KB

6

Please use something that makes sense, like /share/Public/Music:/Music2 for example. There is no point in giving IP-Addresses in simple path mappings - this will never work (unless you’ve created a folder named after an IP-Address) and there is also no need to access a local path from the same NAS as a network share.

7

Hello @edward_thompson

Thanks for posting the file, that shows the problem clearly. Lines 13 and 14 need to be deleted, and line 11 probably needs correcting.

How a volume line works. Each line has two halves separated by a colon:

/share/Container/roon : /Roon
        ↑                  ↑
   real folder on      the name Roon
   your QNAP           sees inside the container

The left half is an actual path on the NAS. The right half is just a folder name that exists inside the container. Neither half is ever a network address, and no part of this goes over the network. The container runs on the QNAP, so it reaches your music as ordinary local folders.

What lines 13 and 14 are currently doing.

- /share/:/192.168.68.52/Public/Music/Albums
- /share/:/192.168.68.52/Public/Music/

You have put your NAS’s own IP address on the container side. That makes a folder literally named 192.168.68.52 inside the container, which Roon has no reason to look in. And on the host side both lines say /share/, so they mount the whole of your storage into the container twice over.

Please remove both lines entirely.

Your first three lines are correct in shape.

- /share/Container/roon:/Roon
- /share/Music:/Music
- /share/Container/roon-backups:/RoonBackups

/Roon, /Music and /RoonBackups are the three names the container expects, so please leave those exactly as they are.

One thing to check on line 11. Earlier diagnostics showed your music living at /Public/Music, which suggests the real path on the NAS is /share/Public/Music rather than /share/Music. Please confirm in File Station which it is.

This matters more than it looks. If the host path on the left does not exist, Docker does not report an error. It quietly creates an empty folder with that name and mounts that instead. Roon then sees a valid but empty /Music and finds nothing, with no error anywhere to tell you why. That would match what you have been seeing.

So: delete lines 13 and 14, correct line 11 to the real path, recreate the application, and in Roon add /Music as your storage folder. Inside Roon you use the container name /Music, not the QNAP path.

8

Hello @edward_thompson,

Circling back on this, have you had a chance to update the Docker volume mappings we went over, especially removing those two bad lines and correcting the music path on line 11? If it helps, the QNAP Docker setup guide is the same reference for the container-side paths we were talking about. Please reply with what you see in File Station or any changes you made, and we can take it from there.

Please note, if we don’t hear back from you this thread may close automatically soon. If the thread auto-closes and you need further assistance, please submit a reopen support request via the technical support help form below and specify that the issue should be reopened. Thank you.