-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Closed
Labels
bugSomething isn't workingSomething isn't workinginvestigationWe are looking into itWe are looking into it
Description
β Have you read and understood the above guidelines?
yes
π What is the name of the script you are using?
slskd
π What was the exact command used to execute the script?
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/slskd.sh)"
βοΈ What settings are you using?
- Default Settings
- Advanced Settings
π₯οΈ Which Linux distribution are you using?
Debian 12
π Provide a clear and concise description of the issue.
Hello,
I read everything here https://community-scripts.github.io/ProxmoxVE/scripts?id=slskd
But the web gui is not working? Maybe I miss something?
My /opt/soularr/config.ini :
[Lidarr]
api_key = MY API KEY
host_url = http://192.168.1.119:8686
download_dir = /data/slskd_downloads
disable_sync = False
[Slskd]
api_key = MY API KEY
host_url = http://192.168.1.118:5030
url_base = /
download_dir = /downloads
delete_searches = False
stalled_timeout = 3600
π Steps to reproduce the issue.
- Install the slskd script
- Install the lidarr script (which is working)
- Edit the /opt/soularr/config.ini
- Go to slskd host_url
β Paste the full error output (if available).
journalctl -u slskd
Γ slskd.service - slskd Service
Loaded: loaded (/etc/systemd/system/slskd.service; enabled; preset: enabled)
Active: failed (Result: start-limit-hit) since Fri 2025-05-30 09:57:55 EDT; 11min ago
Duration: 300ms
Process: 330 ExecStart=/opt/slskd/slskd --config /opt/slskd/config/slskd.yml (code=exited, status=0/SUCCESS)
Main PID: 330 (code=exited, status=0/SUCCESS)
CPU: 258ms
May 30 09:57:55 slskd systemd[1]: slskd.service: Scheduled restart job, restart counter is at 5.
May 30 09:57:55 slskd systemd[1]: Stopped slskd.service - slskd Service.
May 30 09:57:55 slskd systemd[1]: slskd.service: Start request repeated too quickly.
May 30 09:57:55 slskd systemd[1]: slskd.service: Failed with result 'start-limit-hit'.
May 30 09:57:55 slskd systemd[1]: Failed to start slskd.service - slskd Service.
May 30 09:36:05 slskd systemd[1]: Started slskd.service - slskd Service.
May 30 09:36:06 slskd slskd[7170]: Invalid configuration:
May 30 09:36:06 slskd slskd[7170]: Soulseek:
May 30 09:36:06 slskd slskd[7170]: The Picture field specifies a non-existent file '/opt/slskd/path/to/slsk-profile-picture.jpg'.
May 30 09:36:06 slskd systemd[1]: slskd.service: Deactivated successfully.
May 30 09:36:06 slskd systemd[1]: slskd.service: Scheduled restart job, restart counter is at 1.
May 30 09:36:06 slskd systemd[1]: Stopped slskd.service - slskd Service.
May 30 09:36:06 slskd systemd[1]: Started slskd.service - slskd Service.
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workinginvestigationWe are looking into itWe are looking into it