Setting up via Docker in Unraid: logs are never populated once Redis info is provided #35

New issue

Open

opened 2026-03-05 19:41:43 +00:00 by bgarnz · 1 comment

bgarnz commented

2026-03-05 19:41:43 +00:00

Now when I enter my Redis container name into the docker compose, spotizerr never populates anything in its logs. Just completely empty. The last log entry was earlier today before I set up Redis. After that, nothing.

Is there something I'm supposed to do with Redis to make it functional with spotizerr? I don't see any mention of it in the docs.

I set this up on my Unraid server via docker, and it seemed to work enough for me to do spotify-auth. However, I realized that I had completely missed the Redis step. I then had to learn what Redis is, get a container for it, and make sure that it's running in the logs. Now when I enter my Redis container name into the docker compose, spotizerr never populates anything in its logs. Just completely empty. The last log entry was earlier today before I set up Redis. After that, nothing. Is there something I'm supposed to do with Redis to make it functional with spotizerr? I don't see any mention of it in the docs.

Krunox commented

2026-03-09 23:41:36 +00:00

I'm not sure how container deployment works in Unraid, but you should at least post your docker-compose.yaml and .env files so we can see what might be wrong. Also, your Spotizerr logs.

In your .env, make sure REDIS_HOST matches the Redis service name in your compose file.

So, if the redis service in your compose file looks like:

services:
  redisname:
    image: redis:alpine
    container_name: spotizerr-redis
    restart: unless-stopped
    env_file:
    - .env
    volumes:
    - redis-data:/data
    command: sh -c 'redis-server --requirepass "$REDIS_PASSWORD" --appendonly yes'
volumes:
  redis-data:
    driver: local

The redis connection in your .env should look like:

REDIS_HOST=redisname
REDIS_PORT=6379
REDIS_DB=0
REDIS_PASSWORD=CHANGE_ME

However, I realized that I had completely missed the Redis step. I then had to learn what Redis is, get a container for it, and make sure that it's running in the logs.

You don't have to learn it if you don't know what it is. You should redo the process, delete your spotizerr, and prune redis-data.

Is there something I'm supposed to do with Redis to make it functional with spotizerr? I don't see any mention of it in the docs.

That's because you don't need to do anything with the Redis service. You're only expected to interact with the Spotizerr service. The Spotizerr app will set up the database automatically on the first run.

I'm not sure how container deployment works in Unraid, but you should at least post your `docker-compose.yaml` and `.env` files so we can see what might be wrong. Also, your Spotizerr logs. In your `.env`, make sure `REDIS_HOST` matches the Redis service name in your compose file. So, if the redis service in your compose file looks like: ```yaml services: redisname: image: redis:alpine container_name: spotizerr-redis restart: unless-stopped env_file: - .env volumes: - redis-data:/data command: sh -c 'redis-server --requirepass "$REDIS_PASSWORD" --appendonly yes' volumes: redis-data: driver: local ``` The redis connection in your `.env` should look like: ```env REDIS_HOST=redisname REDIS_PORT=6379 REDIS_DB=0 REDIS_PASSWORD=CHANGE_ME ``` > However, I realized that I had completely missed the Redis step. I then had to learn what Redis is, get a container for it, and make sure that it's running in the logs. You don't have to learn it if you don't know what it is. You should redo the process, delete your spotizerr, and prune redis-data. > Is there something I'm supposed to do with Redis to make it functional with spotizerr? I don't see any mention of it in the docs. That's because you don't need to do anything with the Redis service. You're only expected to interact with the Spotizerr service. The Spotizerr app will set up the database automatically on the first run.