Deluge
I'm a (happy) deluge user since years (and since yarss2 I can't do without deluge, I love love it) but one day, I did a clean install on my server, and since then, I can't seem to be able to remotely connect my deluged instance
* All computer are debian stable (bullseye).
* I did my attempts with both legacy ~/.config/deluge and new ones (adding a auth file following https://dev.deluge-torrent.org/wiki/Use ... entication) : in both cases, I couldn't remotely connect with the deluge's GUI (locally, it work fine with the custom user/passwd tho)deluged 2.0.3
libtorrent: 1.2.9.0
Python: 3.9.2
OS: GNU/linux Debian GNU/Linux 11 bullseye
I even tried wiith deluge-console which worked fine locally on 127.0.0.1 but spammed errors about "twisted" (which catched my intention) ; I had to redirect 2>/dev/null to be able to use it properly ; but it did weird things like complaining "ANYTHING I PUT" in port being ignored as "not being an integer" while I'm writing the default deluge's port (58846).
I don't know what's hapenning !
I think the problem should be reproductible on any fresh installed bullseye ? I firstly assumer it could be a "armhf" bug (my server's is an olinuxino), but seem like I have the same error wether I try to connect remotely to deluged on x86 or arm.
___
And then somehow, I edited with nano core.conf and put true to "allow_remote" and of course it worked.
I thought it wouldn't be necessary because it wasn't mentionned in https://dev.deluge-torrent.org/wiki/Use ... entication
...And because I did check the damn box using the local deluge-console gui and then "apply", but it didn't effectively worked so... There is that.
Okay solved ! Woukld be nice to add a little word in the Authentification page about this little silly thing I lost hours of sanity on !
Like I don't know "just make sure to check the core.conf, le param allow_remote before anything".
