Release Rejected: SoulseekDownloadProtocol is not enabled for this artist

[matterbyte]

I recently configured the plugin, but not seeing anywhere how to address this. what does this mean?

Also seeing "Unable to parse release" for a number as the release rejection reason.
what could be going on?

[TypNull]

That’s an unusual issue, it cant occur if you installed Tubifarry normally and didn’t disable the protocol. However, you can simply follow the instructions in the relevant section to resolve it: https://wiki.servarr.com/lidarr/plugins#delay-profile

[matterbyte]

@TypNull looks like i missed that last part of the steps, thank you! this fixed it. using interactive import, i no longer see release rejected.

however, once the download completes, lidarr reports "No files found are eligible for import"
I do have the queue cleaner enabled as well, with rename tracks, always, retry

i assume this isn't related to the download release rejected, but is there a way to address this?

[TypNull]

I’m still unclear on how you’ve set up your Compose files. I’m not sure if SLSKD respects user sets, it’s been a while since I last checked. For faster help, I’d recommend joining the Servarr Discord; there are more people there who can assist.
Also, make sure your paths in SLSKD and Lidarr match exactly. If they don’t, Lidarr won’t be able to locate the directory.

[matterbyte]

@TypNull i had more time to look into this recently, and i believe i might have a bit more info on the issue - it looks like when lidarr errors on import, it's due to expected album names in lidarr not matching actual downloaded album names from SLSKD.

For example, lidarr's error is "No files found are eligible for import in /data/completed/NAME (YEAR)" but the folder name in the directory is "(YEAR) NAME [16Bit-44.1kHz]"

However, i had understood the plugin was supposed to intercept the download and rename the files to avoid this issue during import. Have i configured something incorrectly perhaps?

For context, I don't believe my issue is with regards to permissions or access, as i've set this up identical to other containers where i haven't had file access/directory issues. The paths do match as they should as well between the different containers.

[TypNull]

The slskd client does not automatically rename files. To rename files for better compatibility with Lidarr, you can set up the queue cleaner with the 'rename tracks' option. It should improve the chance of import at least a little.

[matterbyte]

I enabled that setting when i initially installed Tubifarry - below is how i have it configured, is this not correct?

[TypNull]

While this is technically correct, if it still fails, the issue may be that the tracks did not have enough information to construct the filename. Without trace logs, it’s difficult to determine exactly what went wrong.