Deluge ignoring tracker proxy

[marco_silva85]

Ressurecting this old thread, because I can still reproduce the problem.
Deluge in classic and also daemon mode.
Using a tracker proxy: HTTP, 127.0.0.1.
No connection is made and connection follows directly, can see the "bypass" in wireshark.

archlinux w/KDE. Maybe deluge tries to follow kde proxy settings / system settings (I have none btw, they are the defaults).

[Cas]

That post was for a very old version of Deluge and certainly not worth resurrecting.

http://dev.deluge-torrent.org/wiki/Cont ... nformation

[marco_silva85]

Non-related: Trac (bug reporting system) is blocking me from registering, assumes I'm a spam-bot - then it shows captcha and it always fails with "CAPTCHA failed to handle original request". I'm registering with name same as this account and followed http://forum.deluge-torrent.org/viewtop ... =7&t=51737 so:

I'm not already registered
Valid username
Matching passwords
Valid email
...

[marco_silva85]

It happens with current deluge.
Did some debugging: tracker proxy starts working if you enable DHT proxy.
Another bug: w/tracker proxy, deluge or libtorrent modifies the header "Location". If the tracker proxy is on localhost, "Location" is modified to 127.0.0.1 instead of tracker url, breaking it.
Deluge 1.3.12 libtorrent 1.0.6.0 linux.

[Cas]

From libtorrent 0.16 onwards there is only one proxy for everything so you should just put details into one in Deluge.

[marco_silva85]

From libtorrent 0.16 onwards there is only one proxy for everything so you should just put details into one in Deluge.

ok, doesn't make sense removing the individual proxie, but I guess I have to report it on libtorrent then.
What about the second bug?
(w/tracker proxy, deluge or libtorrent modifies the header "Location". If the tracker proxy is on localhost, "Location" is modified to 127.0.0.1 instead of tracker url, breaking it.)

[chuckecheeseli]

I can also make Deluge bypass the proxy, using multiple different versions of the Windows installation. I set all my proxies to my phone on my LAN (192.168.1.5), even specifying Socks5 w/Auth and blank user/passes knowing that it should fail to connect (see attached).

Deluge will eventually find peers from which to download. The two peers in the attached screenshot also show up as active connections in CurrPorts port monitoring utility (highlighted in red in attached screenshot). Currports also show simultaneous connection attempts to my bogus proxy (highlighted in blue).

Has anyone figured out why this is still happening, and how to fix it?

Deluge v: 1.3.6 (but this happens from 1.3.4 to 1.3.12)
libtorrent v: 0.15.10.0
OS: Windows 10 Home x64

proxy settings.png (93.33 KiB) Viewed 4382 times

active peers.png (154.75 KiB) Viewed 4382 times

active ports.png (153.98 KiB) Viewed 4382 times

[marco_silva85]

The text you wrote is a bit confusing, "different versions of the Windows installation", "all my proxies to my phone on LAN", what does this mean?
I didn't understand the problem you are having either.

And is your problem related to the one in this topic? If not, please open a new topic.

[chuckecheeseli]

Thanks for the reply.

"different versions of the Windows installation": I installed multiple different deluge Windows installation packages (one after another, not simultaneously) including 1.3.4, 1.3.6, and 1.3.12. I noticed this behavior with at least these three versions of Deluge.

"all my proxies to my phone on LAN": Please see screenshot 1, again included below. I set my phone as 192.168.1.5 on my LAN (and my computer as 192.168.1.3). I then set Deluge proxies to 192.168.1.5, effectively telling it to try and use my phone as a proxy server, which shouldn't work.

Perhaps the behavior I'm noticing is not quite the same as that described in your original post, but the issue I'm having is definitely proxy-related. Deluge appears to be circumventing my proxy settings. I assume this because it should be failing to make any connection when trying to use my phone as a proxy server, but insteads it still finds peers and downloads from then, via apparently direct peer-to-peer connections as far as I can tell.

Other posts seem to describe this problem, without any solutions posted (see below):
http://forum.deluge-torrent.org/viewtop ... 1&p=222599
http://forum.deluge-torrent.org/viewtop ... 1&p=211091
http://forum.deluge-torrent.org/viewtop ... 3&p=205733
http://forum.deluge-torrent.org/viewtop ... 3&p=205067
http://forum.deluge-torrent.org/viewtop ... 5&p=198881
http://forum.deluge-torrent.org/viewtop ... 5&p=197135
http://dev.deluge-torrent.org/ticket/2149