slskd media management

[gbosky]

I keep getting an error when using slskd to download that says "Failed to import Track. Permissions Error" . Is there a way to fix that? Is there a setting in slskd that is blocking lidarr from editing the file?

[TypNull]

Hey there!

this is a pretty common headache, especially when dealing with Docker or Linux file permissions. Let’s walk through some steps to get this sorted out.

---

1. Check File and Folder Permissions

First, let’s make sure the folders where slskd is saving downloads and where Lidarr is trying to import files have the right permissions. You can check the permissions by running:

ls -ld /path/to/downloads
ls -ld /path/to/lidarr/library

If the folders aren’t writable by the user or group running Lidarr and slskd, you can fix that by adjusting the permissions:

sudo chmod -R 775 /path/to/downloads
sudo chmod -R 775 /path/to/lidarr/library

Or, if you prefer, you can change the ownership of the folders to the user running Lidarr and slskd:

sudo chown -R user:group /path/to/downloads
sudo chown -R user:group /path/to/lidarr/library

---

2. Make Sure Docker UID/GID Match

If you’re using Docker, it’s super important that the User ID (UID) and Group ID (GID) for the user running Lidarr and slskd match across your containers and the host system. You can check your user’s UID and GID on the host system with:

id username

Then, make sure your Docker setup uses the same UID and GID. If you’re using Docker Compose, it might look something like this:

environment:
  - PUID=1000
  - PGID=1000

If you’re running the containers manually, you can pass these values like this:

docker run -e PUID=1000 -e PGID=1000 ...

---

3. Double-Check Docker Volume Mounts

Make sure the folders you’re using in Docker are mapped correctly. For example, if slskd is saving files to /data/downloads and Lidarr is importing from /data/music, your Docker setup should look something like this:

volumes:
  - /host/path/to/downloads:/data/downloads
  - /host/path/to/music:/data/music

This ensures both containers are pointing to the same directories on your host system.

---

4. Check slskd Settings

Take a quick look at slskd’s settings to make sure the download directory is set correctly and accessible by Lidarr. Also, if slskd is running as a service, check the service file (usually at /etc/systemd/system/slskd.service) to ensure it’s running with the right user and group:

[Service]
User=yourusername
Group=yourgroupname

---

5. Use ACLs for More Control

If you don’t want to change ownership or permissions globally, you can use Access Control Lists (ACLs) to give specific permissions to the user or group running Lidarr and slskd:

sudo setfacl -R -m u:username:rwx /path/to/directory
sudo setfacl -R -m g:groupname:rwx /path/to/directory

---

Hopefully, one of these steps will get you back on track! Let me know if you’re still having trouble, and we can dig deeper.