thx for your feedback

Deluge/Libtorrent version?
Have you tried to set the loggin to debug level? So far the msg doen't ring a bell but maybe with more details...

Hi,

try to install this plugin viewtopic.php?f=9&t=28915
I think It may fit your need

Under Ubuntu I think the process responsible for out of memory process kill is OOM killer. Maybe there are some rooms there to not kill specific process. However this approach will always leads to issue and I think better to substitute teamviewer with something else for example. Even at the OS level...

The name of the interface seems logical for me, either the name displayed in the network panel or the one displayed in the 1st line of "route print".
(Interface List). Test this last option first, seems more logical to me.

So here it seems you run Libtorrent 1.0.11/Deluge 1.3.15 and the daemon is well started. Is this daemon killed a short time after? The journal tells us the Deluge process was killed due to an out of memory issue on the RPI. In such constrain the Kernel kills application but Deluge didn't kill itself...

cool

Hi

GTKclient: have you enabled the remote access to Deluge and created a user with the sufficient rights?
Deluge-console: try on the server with your usual account "sudo -u deluge deluge-console"

Hi guys, to share my own "solution" about this: I'm using the PPA Deluge repository for the installion to stick with the couple Deluge 1.3.15/Libtorrent 1.0.11. Of course any system update will upgrade the libtorrent version so simply freeze it : #if not done yet add the PPA repo, Zesty wi...

Hi, No log-> have you set the log level debug? https://dev.deluge-torrent.org/wiki/Troubleshooting#Loggingtofile The libtorrent version may be useful too, (command available on the same page). So the RPI ran out of memory and the process was killed it seems. Check with "free -m" command. t...