-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Description
β Have you read and understood the above guidelines?
yes
π What is the name of the script you are using?
Deluge
π What was the exact command used to execute the script?
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/deluge.sh)"
βοΈ What settings are you using?
- Default Settings
- Advanced Settings
π₯οΈ Which Linux distribution are you using?
Debian 12
π Which Proxmox version are you on?
pve-manager/9.0.3/025864202ebb6109 (running kernel: 6.14.8-2-pve)
π Provide a clear and concise description of the issue.
After a clean installation the website is not accassible.
when going to 192.168.100.25:8112 you get:
192.168.100.25 refused to connect.

π Steps to reproduce the issue.
Step1: install via: https://community-scripts.github.io/ProxmoxVE/scripts?id=deluge&category=Files+%26+Downloads
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/deluge.sh)"
Step2: Connect to {IP}:8112
β Paste the full error output (if available).
root@deluge:~# sudo systemctl status deluge-web deluged
Γ deluge-web.service - Deluge Bittorrent Client Web Interface
Loaded: loaded (/etc/systemd/system/deluge-web.service; enabled; preset: enabled)
Active: failed (Result: signal) since Thu 2025-09-18 00:00:22 CEST; 5min ago
Duration: 1.102s
Docs: man:deluge-web
Process: 307 ExecStart=/usr/local/bin/deluge-web -d (code=killed, signal=ILL)
Main PID: 307 (code=killed, signal=ILL)
CPU: 1.096s
Sep 18 00:00:22 deluge systemd[1]: deluge-web.service: Main process exited, code=killed, status=4/ILL
Sep 18 00:00:22 deluge systemd[1]: deluge-web.service: Failed with result 'signal'.
Sep 18 00:00:22 deluge systemd[1]: deluge-web.service: Consumed 1.096s CPU time.
Sep 18 00:00:22 deluge systemd[1]: deluge-web.service: Scheduled restart job, restart counter is at 5.
Sep 18 00:00:22 deluge systemd[1]: Stopped deluge-web.service - Deluge Bittorrent Client Web Interface.
Sep 18 00:00:22 deluge systemd[1]: deluge-web.service: Consumed 1.096s CPU time.
Sep 18 00:00:22 deluge systemd[1]: deluge-web.service: Start request repeated too quickly.
Sep 18 00:00:22 deluge systemd[1]: deluge-web.service: Failed with result 'signal'.
Sep 18 00:00:22 deluge systemd[1]: Failed to start deluge-web.service - Deluge Bittorrent Client Web Interface.
Γ deluged.service - Deluge Bittorrent Client Daemon
Loaded: loaded (/etc/systemd/system/deluged.service; enabled; preset: enabled)
Active: failed (Result: signal) since Thu 2025-09-18 00:00:19 CEST; 6min ago
Duration: 1.142s
Docs: man:deluged
Process: 301 ExecStart=/usr/local/bin/deluged -d (code=killed, signal=ILL)
Main PID: 301 (code=killed, signal=ILL)
CPU: 1.117s
Sep 18 00:00:19 deluge systemd[1]: deluged.service: Consumed 1.117s CPU time.
Sep 18 00:00:19 deluge systemd[1]: deluged.service: Start request repeated too quickly.
Sep 18 00:00:19 deluge systemd[1]: deluged.service: Failed with result 'signal'.
Sep 18 00:00:19 deluge systemd[1]: Failed to start deluged.service - Deluge Bittorrent Client Daemon.
Sep 18 00:00:20 deluge systemd[1]: deluged.service: Start request repeated too quickly.
Sep 18 00:00:20 deluge systemd[1]: deluged.service: Failed with result 'signal'.
Sep 18 00:00:20 deluge systemd[1]: Failed to start deluged.service - Deluge Bittorrent Client Daemon.
Sep 18 00:00:22 deluge systemd[1]: deluged.service: Start request repeated too quickly.
Sep 18 00:00:22 deluge systemd[1]: deluged.service: Failed with result 'signal'.
Sep 18 00:00:22 deluge systemd[1]: Failed to start deluged.service - Deluge Bittorrent Client Daemon.
πΌοΈ Additional context (optional).
No response