Issue description:
Hello.
I’m a new user.
I have just configured the application to play my music on my NAS via Webdav.
It works perfectly. But I can’t get the images and artist information.
I followed the wiki which talks about Kodi’s folder structure (which I also use at home) but nothing works.
Is this a limitation of the Webdav protocol or is there an option in the application that I’ve missed?
Logs:
Upload description: can"t get artist info with webdav
Additional information:
Reproduction steps:
I have an ArtistInfo folder at the root of my library. A folder with the artist’s name. An nfo file with information on the artist and images in jpg thumb and fanart.
Nothing is retrieved from Symphonium.
I’ve also tried putting the images in the artist’s folder containing the albums, but it doesn’t work.
Media provider:
WebDAV
Screenshots:
2025-05-05 18:41:14.995 Error WebDav Error getting server data 405-
The server returns error 405 when trying to access the folder.
Do you have an “ArtistInfo” folder with the proper case and proper permissions ?
Normally, permissions are configured. Kodi can retrieve images and information. But Symfonium can’t.
I tried locally on my phone, it retrieves the information from the nfo file (except the biography) but does not retrieve the thumb.jpg image.
I tried to create the nfo with MediaElch (which I use for movies) and I also tried copying and modifying the example given in the wiki.
Same result…
I can’t figure out what I’m doing wrong. 
Have you checked your WebDAV server log to see why it returns 405 when trying to access the folder ?
What WebDAV server are you using ?
It should work for the local device I’ll need log for that part too 
Good evening.
For the Webdav server, I use the one provided by my Synology NAS. It’s an old NAS (OS version 6.2).
In its log, there is nothing about the webdav connection, only the file transfer. I don’t see any error.
I’ve tried again locally and normally I’ve sent the logs.
The included scrapper seems to work (at worst I’d use it), but I like to control and do this kind of addition myself, especially for lesser-known artists.
Translated with DeepL.com (free version)
I tested with my Synology but it’s 7.2 and it works correctly, please show the actual folder hierarchy.
And provide a zip of your ArtistInfo folder to check why no biography.
I’ve just sent you the files.
I should point out that I’ve just noticed in the local source settings that you can choose the artist information folder. I’ve filled it in.
I have the same structure on my phone and on my NAS.
I tested with my Synology but it’s 7.2 and it works correctly, please show the actual folder hierarchy.
Maybe my NAS is too old for Webdav to work properly (I don’t know anything about it).
For local use SMB is a way better way to access the NAS.
I know. But Webdav was mainly for accessing music away from home.
At worst, I’d get an SD card to put on my phone.
Any idea why my NFO file and images don’t work locally?
Ok no problem 
have a nice day
Ok so the issue with some data not used will be fixed in next release.
I’ve turned on my old nas with 6.2 and it does work so I guess the logs where from some odd test and it will work too with next release.
May I ask, in the root directory, ArtistInfo, does this rule apply to all media source providers?
Not sure what you mean, the folder needs to have that name at the root for providers scanned by Symfonium.
Thank you so much for your time!
Sorry, I just used translation software, so there might be some parts that are not expressed clearly.
I found that in “Manage media providers”, only the “Local device” provider has the “Artist info folder” configuration, so I want to ask, for example, for the Dropbox provider, if I also put an ArtistInfo folder in the root directory, will Symfonium scan it?
I just tested it a bit. Synology 7.2 WebDav, alist WebDAV, Dropbox, in the case where the ArtistInfo folder exists in the root directory for all, all are unable to correctly display the artist’s information.
Yes it’s currently not working except for the moods, will be fixed in next release.
Thank you for your patient reply, looking forward to good news.
