Deluge turning force_proxy off on its own

[onetwothree]

I'm having a strange issue. When I set force_proxy or anonymous_mode to true, the daemon sets them back to false when it starts up. If I set them via the web interface, the change is also reverted. My Deluge version is:

Code: Select all

deluged 2.0.3
libtorrent: 1.1.13.0
Python: 3.8.5
OS: Linux Ubuntu 20.04 focal

There are no errors in the log, nor any indication why Deluge would be acting like this. Could anyone possibly shed some light on why this is occuring?

[mhertz]

Do you have 'apply settings on startup' enabled in ltconfig? If yes, then is this something new and has worked before or always been like this?

Edit: Completely forgot, that with regards to these two options, then you can also enable them under deluge's own options under proxy, as added in deluge2. Or is it these you refer to here and not ltconfig?

[onetwothree]

I'm not using ltconfig, but instead the "force_proxy" option under "proxy" in core.conf.

I could try using ltconfig instead. It's something I hadn't tried yet because Deluge theoretically supports the option now.

Also, am I right in thinking that "force_proxy" ensures the proxy is always used, and if the proxy is down, Deluge will wait until it's up again?

Edit: ltconfig seems to have worked - there doesn't appear to be a force proxy option, but there is an option for an "anonymous mode" that looks like it does the same thing, according to the docs on libtorrent.

[mhertz]

Strange that ltconfig works but not main deluge settings, as set same options. Sorry, don't know why resets, and not at my computer now to test.

Force_proxy indeed does that, or I'm not 100% sure if it reconnects after the failure, but atleast breaks connection when occuring, bar any bugs in implementation, though Arvid added low-level checks in place to catch such hopefully.

The option was deprecated in libtorrent 1.2.x and it's functionality instead became default, so it sounds like you have libtorrent 1.2.x and not 1.1.13(force_proxy functionality was also incorporated into anonymous_mode at one point though in much older times, so I'm pretty sure you're not on that old version).

Anonymous_mode makes sure you never leak your IP and several other identifying info, as metadata over the connection(extended handshakes and special announce flags), being proxy, vpn or regular(I.e force_proxy forces connection to only go over proxy, but then doesn't help if sending real IP as metadata over said proxy connection, hence two options), but the docs could be outdated from older times where force_proxy functionality included, cannot remember.

[onetwothree]

deluge -v and apt search both report libtorrent as being 1.1.13, so the version should be correct. The reason I'm investigating this is that I believe my IP address was leaked, despite using a proxy, so my guess is that the proxy temporarily went down. If I was using a later version of libtorrent where it was the default not to bypass the proxy, then I wouldn't expect my IP address to leak.

[mhertz]

Strange indeed, sorry I cannot reproduce here unfortunetly.

On my setup(linux), then editing core.conf, as I always also do myself, doesn't forget force_proxy or anonymous_mode. When checking the setting afterwards from 'deluge-console config force_proxy', then it shows just blank, neither true or false, and same with anonymous_mode, but the option is there in core.conf as defined before and checking ipmagnet website shows anonymous_mode is enabled by not showing the agent string and just showing blank there. That is though with deluge 2.0.4.dev38 and libtorrent 1.2.11.

I then checked a VM i have laying around of win10 for some stuff I do at times, and there I checked deluge 2.0,3 with libtorrent 1.1.14, as didn't have 1.1.13 available there anymore and there I had the full GTK client installed so checked that and there was a force_proxy in the ltconfig settings, and the main deluge setting also wasen't reset upon restart. Are you using latest ltconfig 2.0?

You can try run with debug logging enabled and see if there is some clues or attach it here for us to see, as else i'm pretty much out of ideas i'm affraid.

[onetwothree]

If this ltconfig doesn't work I'll try running it in debugging mode for more information, otherwise we can perhaps chalk this down as the fault of something unusual in my setup.