Skip to content

Troubleshooting

The bot replies "You are not authorized to use this bot"

Cause: your Telegram user id is not in TELEGRAM_ALLOWED_USERS. When the list is empty the bot denies everyone, and the log says TELEGRAM_ALLOWED_USERS is empty — bot will deny all commands until configured at startup.

Fix: the reply includes your id. Add it to TELEGRAM_ALLOWED_USERS (comma-separated for several people) and recreate the container with docker compose up -d.

The container stops right after it starts

Cause: a required variable is missing. The log names it: Required environment variable 'SLSKD_API_KEY' is not set. The required ones are TELEGRAM_BOT_TOKEN, SPOTIFY_CLIENT_ID, SPOTIFY_CLIENT_SECRET, SLSKD_HOST and SLSKD_API_KEY.

Fix: set it in .env (or the compose environment: block) and start again.

Permission denied on /downloads, /music or /data

Cause: the container runs as uid 1000 and cannot write a mounted folder. A folder Docker creates for a missing bind mount belongs to root.

Fix: give the folders to uid 1000 (sudo chown -R 1000:1000 data, and the same for your download and library folders), or mount folders that uid 1000 can already write.

Downloads finish in slskd but nothing reaches the library

Cause: /downloads in the container is not the folder slskd writes its completed downloads to, so the bot never sees the file.

Fix: set SLSKD_DOWNLOAD_PATH to slskd's own download folder on the host, the same one slskd mounts.

slskd writes downloads as root

Cause: slskd's container runs as root with umask 0022, so every finished download belongs to root and only root may change it. The bot runs as uid 1000: it can read the file and copy it into the library, but it cannot delete the download afterwards. The log shows Failed to cleanup: /downloads/... after a save or a chat send, and the orphan sweep logs Orphan sweep could not delete /downloads/...: [Errno 13] Permission denied. The downloads folder keeps growing.

Fix: let slskd write files its group can change, and put the bot in that group.

  1. On the slskd container, set SLSKD_UMASK=0002. New downloads are then group-writable (rw-rw-r--, folders rwxrwxr-x).
  2. Run the bot with the root group: user: "1000:0" under the slskd-importer service in docker-compose.yml. Running it with slskd's own uid works too.
  3. Fix the downloads that already exist, once, on the host: sudo chmod -R g+w /path/to/slskd/downloads.

Recreate both containers (docker compose up -d). The next save deletes its download, and the next sweep stops logging Permission denied.

Library files belong to the root group

Cause: with user: "1000:0" every file the bot writes gets group root. The bot gives new library files mode 664 (folders 775) and the library folder's group, but it can only hand a file to a group it belongs to.

Fix: add the library's group to the bot as a second group, keeping the root group for the downloads. With the library folder owned by group 100 (users):

    user: "1000:0"
    group_add:
      - "100"

Recreate the container. Files saved from then on get group users; older ones keep root until you change them, for example with sudo chgrp -R users /path/to/library.

Telegram says the bot is logged in elsewhere

Cause: the bot was switched to a local Bot API server without logging it out of Telegram's cloud server. A bot token is logged in to one server at a time, so the bot gets no updates, or errors that say it is logged in or logged out somewhere else.

Fix: log it out of the cloud server once, then recreate the containers:

curl https://api.telegram.org/bot<your-bot-token>/logOut
docker compose --profile bigfiles up -d

Going the other way, from the local server back to the cloud, needs logOut on the local server first, and Telegram can take up to 10 minutes before the cloud server accepts the token again. The steps are in Getting started.

Uploads time out

Cause: a big file takes longer to upload than the request timeout allows. The log shows Sending <file> to chat <id> failed with a TimedOut error, and the chat says "Could not send the file to Telegram: Timed out". With a local Bot API server the timeout is 600 s, which covers a 2 GB file on a LAN but not on a slow link.

Fix: raise TELEGRAM_UPLOAD_TIMEOUT_SECS in .env (for example 1800) and recreate the container with docker compose up -d. It sets the read and write timeouts of every request to Telegram except polling.

Reporting a bug

Open an issue with:

  • the image tag or version you run;
  • the log around the problem, with LOG_LEVEL=DEBUG if you can reproduce it (docker logs slskd_importer);
  • the song name or Spotify link you sent, and what the bot answered.

Leave out tokens, API keys and your Telegram user id.