Deluge 2.1.1 not working, cant connect to daemon

[greg811]

I can't install Deluge 2.1.1 on dedicated server with ubuntu server 22.04.
Deluged, deluge-web and deluge-console packages installed, services created, both deluged and deluge-web work, but there is no connection.
Web ui does not connect to the deluged daemon, is offline Core.conf has not been created.
When I go to deluge-console, I'm not connected either, and connection is refused.
I thought maybe firewalld, but no, because after disabling it is the same.
Virtualmin and qbittorrent are also installed on the system.

[shinger]

Hi,

So to be sure if i understand the situation right.

- Dedicated server (Ubuntu 22.04) (Here is DelugeD installed on)
- Your computer that you visit the webinterface.

Can you at least ssh to that dedicated server where deluged is installed on and do a

Code: Select all

sudo systemctl status deluged.service

You must see something like this. You said "both deluged and deluge-web work", but i just want to be sure of it.

Code: Select all

<USER>@<SERVER>:~$ sudo systemctl status deluged.service 
_ deluged.service - Deluge Bittorrent Client Daemon
     Loaded: loaded (/etc/systemd/system/deluged.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2023-08-27 11:06:50 CEST; 1 weeks 4 days ago
       Docs: man:deluged
   Main PID: 1028327 (deluged)
      Tasks: 11 (limit: 18540)
     Memory: 14.0G
     CGroup: /system.slice/deluged.service
             __1028327 /usr/bin/python3 /usr/bin/deluged -d -L info -l /var/log/deluge/deluged.log

Aug 27 11:06:50 <SER>VER systemd[1]: deluged.service: Succeeded.
Aug 27 11:06:50 <SER>VER systemd[1]: Stopped Deluge Bittorrent Client Daemon.
Aug 27 11:06:50 <SER>VER systemd[1]: Started Deluge Bittorrent Client Daemon.

If the deamon is indeed is working execute the next command to see if deluged is indeed listening on port 58846

Code: Select all

sudo ss -tulpn | grep 58846

It will look something like this.

Code: Select all

<USER>@<SERVER>:~$ sudo ss -tulpn | grep 58846
tcp    LISTEN  0        50                                       0.0.0.0:58846                                       0.0.0.0:*                                   users:(("deluged",pid=1028327,fd=22))

Then on your core.conf do a

Code: Select all

sudo cat core.conf | grep daemon_port

It will look something like this.

Code: Select all

<USER>@<SERVER>:/var/lib/deluge/.config/deluge$ sudo cat core.conf | grep daemon_port
    "daemon_port": 58846,

[greg811]

There was conflict with qbittorrent.
When I remove qbittorrent, Deluge was installed corectly and start working. Then I install qbittorrent and now works both.

[mhertz]

Regardless, kudos @shinger for top-notch helpfull post, putting e.g me to shame, so great to have people like you around Thanks!

@greg811, thanks for posting solution back, and sorry for butting in needlessly.

[shinger]

There was conflict with qbittorrent.
When I remove qbittorrent, Deluge was installed corectly and start working. Then I install qbittorrent and now works both.

Good to hear .

Regardless, kudos @shinger for top-notch helpfull post, putting e.g me to shame, so great to have people like you around Thanks!

I am a Linux engineer in my professional life (so i have to deal with such cases almost every week), but the real credits and thanks are to you guys for maintaining Deluge and stuff.