This article describes common Deluge issues and how to resolve them.
If your Deluge instance becomes unresponsive, you can restart it from the Client Area. The sections below also describe several common issues and how to fix them.
ERROR: The connection to the webserver has been lost
If you are running a large number of torrents and frequently receive this error, we recommend managing Deluge using the thin client instead of the WebUI.
ERROR: 404 Not Found
If you receive a 404 Not Found error when opening your Deluge URL, it usually means that Deluge is not running.
Restart your Deluge instance from the Client Area and try again.
Restore the Connection Manager Configuration
The Connection Manager is configured automatically during the Deluge installation. Normally, you should not modify this configuration.
If it has been modified or removed accidentally, follow the steps below to restore it.
Step 1 – Remove Existing Entries
Open the Connection Manager and remove all existing entries.
Click Add to create a new connection.
Step 2 – Configure the Connection
Only the following fields are required:
- Hostname: 127.0.0.1
- Port: your Deluge daemon port
Username and Password should be left empty.
You can display your Deluge daemon port via SSH using the following command:
echo -e "Your deluge-daemon port: \e[31m\
$(
grep '"daemon_port": [0-9]*' ~/.config/deluge/core.conf | awk -F ': ' '{print $2}' | awk -F ',' '{print $1}'
)\e[0m"
Example output:
Your deluge-daemon port: 21005
Use the returned value in the Port field.
Step 3 – Connect
Click Add.
Select the newly created entry.
If the daemon is not running, click Start Daemon.
Once the daemon is running, click Connect to access the Deluge WebUI.
Restart Deluge via SSH
If Deluge has frozen or crashed, you can restart it manually using SSH.
Step 1 – Check if Deluge Is Running
Run the following command:
ps --User $(whoami) | grep deluged
If the command returns a process, Deluge is running.
If there is no output, Deluge is already stopped.
Step 2 – Stop Deluge
If Deluge is running, stop it with:
kill -9 $(ps --User $(whoami) | grep deluged | awk -F ' ' '{print $1}')
Verify that it has stopped:
ps --User $(whoami) | grep deluged
If there is no output, Deluge has been stopped successfully.
Step 3 – Start Deluge
Start Deluge with the following command:
deluged
Notes
- The Connection Manager is configured automatically during installation and normally does not require any changes.
- When restoring the Connection Manager, only the hostname and daemon port are required.
- If Deluge frequently becomes unresponsive while managing many torrents, consider using the Deluge thin client instead of the WebUI.
