I was waiting to see if it would pop up somewhere else, so thanks! It shouldn't be too much to change the template around. I'll take a look ASAP. Might not be until the weekend though.

8 minutes ago, JPDVM2014 said:

I was waiting to see if it would pop up somewhere else, so thanks! It shouldn't be too much to change the template around. I'll take a look ASAP. Might not be until the weekend though.

Awesome, take your time. Thanks!

On 9/4/2025 at 1:51 PM, CopesaCola said:

@JPDVM2014 Spotizerr moved from github to lavaforge.org/spotizerr. How can we get this working in UnRaid?

I just updated the repo to lavaforge.org/spotizerr/spotizerr:latest and it seems to work

10 hours ago, mayberts said:

I just updated the repo to lavaforge.org/spotizerr/spotizerr:latest and it seems to work

Got the UI to come up but getting a can't connect to server error when trying to search for playlists.. anything wrong here?

@CopesaCola REDIS_DB should just be 0. And REDIS_BACKEND should match REDIS_URL. So redis://172.17.0.3:6379/0

I don't see REDIS_URL and REDIS_BACKEND in the sample env file, so you could try removing those if it still doesn't work after the above changes.

Edited September 8, 2025Sep 8 by JPDVM2014

I'm just getting error: RuntimeError: Missing 'version' in data/config/main.json. Please update your configuration to 3.3.0.

You have to make a config directory in your appdata folder. Then make a main.json that has

{

"version": "3.3.0"

}

That seems to get me up and running.

Source: https://lavaforge.org/spotizerr/spotizerr/issues/2

Edited November 13, 2025Nov 13 by JPDVM2014

Can anybody check on this fork and explain to me how to tweak the template to get the docker images from this new repo please?

LavaForge: Simple. Fast. LavaForge.

spotizerr-phoenix

Spotizerr, reborn

18 hours ago, Olivier12 said:

Can anybody check on this fork and explain to me how to tweak the template to get the docker images from this new repo please?

LavaForge: Simple. Fast. LavaForge.

spotizerr-phoenix

Spotizerr, reborn

I changed the spotizerr template to work with this fork instead. Should be in the Community App store in a couple hours.

If anybody had this problem, I ran into an issue: .cache was created as a directory instead of a file (don't know why), I had to upload an empty file and rename it .cache for it to work.

6 hours ago, Olivier12 said:

If anybody had this problem, I ran into an issue: .cache was created as a directory instead of a file (don't know why), I had to upload an empty file and rename it .cache for it to work.

Yea, I ran into that problem too. It should have popped up as an instruction when installing, but glad you figured it out.

Hey I'm having a problem with the server timing out when searching for playlists, but the logs aren't updating. Any idea whats wrong?

11 hours ago, CopesaCola said:

Hey I'm having a problem with the server timing out when searching for playlists, but the logs aren't updating. Any idea whats wrong?

Could you post a screenshot of your template?

Also, did you go through all the steps to add your Spotify account using the other docker container and Spotify connect?

6 minutes ago, JPDVM2014 said:

Could you post a screenshot of your template?

Also, did you go through all the steps to add your Spotify account using the other docker container and Spotify connect?

Yes I used the new auth tool

9 minutes ago, CopesaCola said:

Yes I used the new auth tool

For your REDIS_HOST, try removing the "redis://" and just leaving the IP address.

I've tried both ways, the server still times out

Hmm, I'm not sure then. Is there anything in your logs at all? Maybe there is something in the logs during startup that can help?

So I've finally managed to set it up with the provided extra "spotizerr-auth" container. At first I tried to run the auth container on unraid, but had to do it on my notebook instead (because I am in a different network)
When I now try to download a track, it get's queued, but receives an error in the end and disappears from history.

There is nothing in the logs that inidcate's an connection issue. I've only seen this message once:

2025-12-10 07:03:16 [WARNING] Couldn't decode JSON from cache at: .cache

edit:

so I've restarted the container and checked the logs (no warning or error)

Tried the same.. downloading a track, now I finally received some more info:

{
  "callback_type": "track",
  "parent": null,
  "current_track": null,
  "total_tracks": null,
  "album": {
    "type": "albumTrack",
    "album_type": "album",
    "title": "SONIC TRASH",
    "release_date": {
      "year": 2025,
      "month": 11,
      "day": 14
    },
    "total_tracks": 16,
    "total_discs": 1,
    "genres": [],
    "images": [
      {
        "url": "https://i.scdn.co/image/ab67616d00001e02de99fccc2376c6045b5ca098",
        "width": 300,
        "height": 300
      },
      {
        "url": "https://i.scdn.co/image/ab67616d00004851de99fccc2376c6045b5ca098",
        "width": 64,
        "height": 64
      },
      {
        "url": "https://i.scdn.co/image/ab67616d0000b273de99fccc2376c6045b5ca098",
        "width": 640,
        "height": 640
      }
    ],
    "ids": {
      "spotify": "65DiMasUEEVfLXwNgeoYok",
      "upc": "199538391466"
    },
    "artists": [
      {
        "type": "artistAlbumTrack",
        "name": "ROMES",
        "ids": {
          "spotify": "4b3MzzOReTrle64Pxc1r9g"
        }
      }
    ]
  },
  "status_info": {
    "ids": {
      "spotify": "4k7xlAymPBgxqJSdMgHfJX",
      "isrc": "QMDA72520349"
    },
    "status": "error",
    "error": "Download failed for 'BLACK HONEY' by 'ROMES' (URL: https://open.spotify.com/track/4k7xlAymPBgxqJSdMgHfJX). Original error: Maximum retry limit reached for 'BLACK HONEY' by 'ROMES' (local: 3, global: 100). Last error: Failed fetching audio key! gid: <redacted>, fileId: <redacted>"
  }
}

There is nothing shown in the container logs. Maybe it would be helpful to have a debugging option?

Edited December 10, 2025Dec 10 by W0nderW0lf

6 hours ago, W0nderW0lf said:

So I've finally managed to set it up with the provided extra "spotizerr-auth" container. At first I tried to run the auth container on unraid, but had to do it on my notebook instead (because I am in a different network)
When I now try to download a track, it get's queued, but receives an error in the end and disappears from history.

There is nothing in the logs that inidcate's an connection issue. I've only seen this message once:

2025-12-10 07:03:16 [WARNING] Couldn't decode JSON from cache at: .cache

edit:

so I've restarted the container and checked the logs (no warning or error)

Tried the same.. downloading a track, now I finally received some more info:

{
  "callback_type": "track",
  "parent": null,
  "current_track": null,
  "total_tracks": null,
  "album": {
    "type": "albumTrack",
    "album_type": "album",
    "title": "SONIC TRASH",
    "release_date": {
      "year": 2025,
      "month": 11,
      "day": 14
    },
    "total_tracks": 16,
    "total_discs": 1,
    "genres": [],
    "images": [
      {
        "url": "https://i.scdn.co/image/ab67616d00001e02de99fccc2376c6045b5ca098",
        "width": 300,
        "height": 300
      },
      {
        "url": "https://i.scdn.co/image/ab67616d00004851de99fccc2376c6045b5ca098",
        "width": 64,
        "height": 64
      },
      {
        "url": "https://i.scdn.co/image/ab67616d0000b273de99fccc2376c6045b5ca098",
        "width": 640,
        "height": 640
      }
    ],
    "ids": {
      "spotify": "65DiMasUEEVfLXwNgeoYok",
      "upc": "199538391466"
    },
    "artists": [
      {
        "type": "artistAlbumTrack",
        "name": "ROMES",
        "ids": {
          "spotify": "4b3MzzOReTrle64Pxc1r9g"
        }
      }
    ]
  },
  "status_info": {
    "ids": {
      "spotify": "4k7xlAymPBgxqJSdMgHfJX",
      "isrc": "QMDA72520349"
    },
    "status": "error",
    "error": "Download failed for 'BLACK HONEY' by 'ROMES' (URL: https://open.spotify.com/track/4k7xlAymPBgxqJSdMgHfJX). Original error: Maximum retry limit reached for 'BLACK HONEY' by 'ROMES' (local: 3, global: 100). Last error: Failed fetching audio key! gid: <redacted>, fileId: <redacted>"
  }
}

There is nothing shown in the container logs. Maybe it would be helpful to have a debugging option?

Only thing I can think of is maybe a permission issue. If you are comfortable in the command line, navigate to your spotizerr appdata folder and run "ls -la". Everything should show as "nobody users".

For the debugging, it might be worth asking at the creator's code repo. I can't add anything unfortunately since I don't have the skill. I just created the template.

https://lavaforge.org/spotizerrphoenix/spotizerr-phoenix

Pemissions are all fine.

It has nothing to do with the file permissions itself, but an incompatibility with the python code to the spotify endpoint api. See: https://lavaforge.org/spotizerr/spotizerr/issues/16

Seems that I have to adress that on lavaforge..

edit:

the issue has been already adressed here:

LavaForge: Simple. Fast. LavaForge.

Last error: Failed fetching audio key!

**Describe the bug** Tried downloading songs after following the setup procedure and it doesn't work. got hit with Last error: Failed fetching audio key! **To Reproduce** Just try to download someth

Edited December 10, 2025Dec 10 by W0nderW0lf

After reading the entire issue - I would suggest adding a information/warning to your template, mentioning that download with spotizerr-phoenix is only possible, if you have an premium account.

Under the bottom line: Dont waste your energy if you only have a free spotify account.

2 hours ago, W0nderW0lf said:

After reading the entire issue - I would suggest adding a information/warning to your template, mentioning that download with spotizerr-phoenix is only possible, if you have an premium account.

Under the bottom line: Dont waste your energy if you only have a free spotify account.

Got it. I'll add that into the description. Thanks!

FYI Version - 0.9.15.11

required me to change the PGID: from 100 to 1000

container was failing with

addgroup: gid '100' in use

adduser: unknown group cabernet

su-exec: getpwnam(cabernet): Invalid argument

addgroup: gid '100' in use

adduser: unknown group cabernet

su-exec: getpwnam(cabernet): Invalid argument

Starting with UID : 99

Starting with UID : 99

2 hours ago, kcossabo said:

FYI Version - 0.9.15.11

required me to change the PGID: from 100 to 1000

container was failing with

addgroup: gid '100' in use

adduser: unknown group cabernet

su-exec: getpwnam(cabernet): Invalid argument

addgroup: gid '100' in use

adduser: unknown group cabernet

su-exec: getpwnam(cabernet): Invalid argument

Starting with UID : 99

Starting with UID : 99

Ugh, I was hoping there would be a PUID/PGID option instead. I'll update the template. Thanks!

Edited December 14, 2025Dec 14 by JPDVM2014

Reference Shelfarr:
Missing a few variables for this container, specifically
ABS_BASE_URL: "http://audiobookshelf:13378"

ABS_TOKEN: "YOUR_ABS_API_TOKEN"

also, as posted currently (1/4/26) does not currently start correctly.

Log is as follows:
text error warn system array login

[2026-01-04 13:03:36 -0600] [1] [INFO] Starting gunicorn 22.0.0

[2026-01-04 13:03:36 -0600] [1] [INFO] Listening at: http://0.0.0.0:5060 (1)

[2026-01-04 13:03:36 -0600] [1] [INFO] Using worker: gthread

[2026-01-04 13:03:36 -0600] [11] [INFO] Booting worker with pid: 11

[runtime] Shelfarr container starting

[runtime] Shelfarr: Container user: uid=99 gid=100(users) groups=100(users)

[runtime] Shelfarr: Python version: Python 3.12.12

[runtime] Shelfarr: Working directory: /app

[runtime] Shelfarr: jemalloc preload: /usr/lib/x86_64-linux-gnu/libjemalloc.so.2

[runtime] Shelfarr: Listing /data:

total 32

drwxr-xr-x 1 99 users 45 Jan 4 12:34 .

drwxr-xr-x 1 root root 180 Jan 4 13:03 ..

-rw-r--r-- 1 99 users 32768 Jan 4 12:34 settings.db

-rw-r--r-- 1 99 users 0 Jan 4 12:34 shelfarr.log

[runtime] Shelfarr: Starting Gunicorn server on port 5060

_____ _ _ __

/ ____| | | |/ /

| (___ | |__ ___| ' / __ _ _ __ _ __

\___ \| '_ \ / \ < / ` | '__| '__|

____) | | | | __/ . \| (_| | | | |

|_____/|_| |_|\___|_|\_\\__,_|_| |_|

Shelfarr v0.69.6 starting…
____
End of Log.
Kept it running for hours thinking maybe it just too awhile to start the first time, but no joy. I see the main github is running V.7.0 as of posting.

I wish I had enough experience with docker to troubleshoot this stuff myself, but I've had bad luck trying to figure out what I've done wrong when trying to get non-unraid specific containers to work correctly in the past. Thanks in advance for your help.